You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by David Jencks <da...@gmail.com> on 2021/10/04 16:46:34 UTC
[Website] Updating after a release
I believe the Antora build has not yet been updated to include the just released camel-3.12.x and related releases. However, camel-quarkus is trying to use it, which breaks the camel-quarkus build.
I’d like to do this and write up what to do when there’s a release, and hopefully simplify the process a bit.
Is there already such a document?
I actually think it might be best to have a section explaining the structure and interdependencies of the Antora site in the site, along with instructions on what to do when there’s a new release. Alternatively perhaps this could be an AsciiDoc file in camel-website.
Is anyone else working on this? I don’t want to create conflicts or duplicate work.
David Jencks
Re: [Website] Updating after a release
Posted by David Jencks <da...@gmail.com>.
I’ve written a draft of instructions on how to update the docs/website after a camel/camel-karaf/camel-spring-boot release: https://github.com/apache/camel/pull/6215
I’ve also applied these instructions (retroactively in some cases) to all the active camel-karaf and camel-spring-boot branches: PRs listed in the doc PR above.
Although in some cases this results in no link changes, I’d prefer to apply all the PRs so that the link generation code is as consistent as possible.
I have a couple of questions as a TODO in the doc PR:
NOTE: TODO: Is there a step of setting up CI or the regen bot?
Should maven snapshots be deployed?
I had to build (with maven) quite a few projects completely because there were no snapshots deployed.
David Jencks
> On Oct 4, 2021, at 10:47 PM, David Jencks <da...@gmail.com> wrote:
>
> Thanks Gregor, it is really useful to me to know that these are actually the steps you are following, and that the branch instructions really are missing…. I’m very good at misinterpreting docs!
>
> David Jencks
>
>> On Oct 4, 2021, at 10:39 PM, Gregor Zurowski <gr...@list.zurowski.org> wrote:
>>
>> I just wanted to confirm that the release guide
>> (https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc)
>> is not outdated and describes the steps we are following when creating
>> new releases. The step to branch off into a new camel-MAJOR.MINOR.x
>> branch is missing though, I'll add it in.
>>
>> I'd be definitely interested in the missing steps that are needed
>> preparing the branch for dependent projects.
>>
>> Thanks,
>> Gregor
>>
>> On Mon, Oct 4, 2021 at 11:47 PM David Jencks <da...@gmail.com> wrote:
>>>
>>> 1. I got the camel-quarkus build to work with these PRs:
>>> https://github.com/apache/camel/pull/6210
>>> https://github.com/apache/camel-spring-boot/pull/376
>>> both include changes that eventually need to go on other branches, so I don’t want to squash the commits.
>>> They also include very substantial changes from simply running the maven build with the new version.
>>>
>>> (a) Evidently instructions to generate these changes is missing from the existing release instructions, or they weren’t followed or I didn’t wait long enough. I think it should be a step in the release process so that it’s safe to use the branch as a dependency.
>>> (b) I don’t see any harm in applying these manually generated changes, but if there is an automated process that will eventually create them and that is preferable please advise when it will occur.
>>>
>>> In any case the camel-quarkus build is currently broken due to the lack of at least the non-generated changes in these PRs.
>>>
>>>
>>> 2. Writing instructions about updating the website will take quite a while, so we can discuss where they should go. For my convenience I’m going to start with a separate page, and it’s easy enough to move the content if that seems appropriate.
>>>
>>> David Jencks
>>>
>>>
>>>> On Oct 4, 2021, at 1:59 PM, Andrea Cosentino <an...@gmail.com> wrote:
>>>>
>>>> If you want to work on one for the website it's fine, but you'll fragment
>>>> the release docs more than the current situation. Fragmentation is bad now.
>>>> We should try to reduce pages and focus on content.
>>>>
>>>> Il lun 4 ott 2021, 22:55 Andrea Cosentino <an...@gmail.com> ha scritto:
>>>>
>>>>> The release guide there it's not outdated. It's related only to camel
>>>>> camel-karaf and camel-sb. All the other subprojects have their own release
>>>>> guide. -1 to start from a new page. I would start from what we have, which
>>>>> is exactly the release steps to release plain camel.
>>>>>
>>>>> Il lun 4 ott 2021, 22:47 David Jencks <da...@gmail.com> ha
>>>>> scritto:
>>>>>
>>>>>> On a quick glance, that looks outdated (vintage camel 2), unaware of most
>>>>>> sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before
>>>>>> releasing camel-3.12.0 from it). I don’t think I should try to complete and
>>>>>> update those instructions.
>>>>>>
>>>>>> I think a new page on how to deal with the website would be appropriate,
>>>>>> since that’s generally going to happen after the release explained on the
>>>>>> existing page.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> David Jencks
>>>>>>
>>>>>>> On Oct 4, 2021, at 11:00 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi David
>>>>>>>
>>>>>>> Yes there is the release guide docs at
>>>>>>>
>>>>>> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
>>>>>>>
>>>>>>> On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>> I believe the Antora build has not yet been updated to include the
>>>>>> just released camel-3.12.x and related releases. However, camel-quarkus is
>>>>>> trying to use it, which breaks the camel-quarkus build.
>>>>>>>>
>>>>>>>> I’d like to do this and write up what to do when there’s a release,
>>>>>> and hopefully simplify the process a bit.
>>>>>>>>
>>>>>>>> Is there already such a document?
>>>>>>>>
>>>>>>>> I actually think it might be best to have a section explaining the
>>>>>> structure and interdependencies of the Antora site in the site, along with
>>>>>> instructions on what to do when there’s a new release. Alternatively
>>>>>> perhaps this could be an AsciiDoc file in camel-website.
>>>>>>>>
>>>>>>>> Is anyone else working on this? I don’t want to create conflicts or
>>>>>> duplicate work.
>>>>>>>>
>>>>>>>> David Jencks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> http://davsclaus.com @davsclaus
>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>>
>>>>>>
>>>
>
Re: [Website] Updating after a release
Posted by David Jencks <da...@gmail.com>.
Thanks Gregor, it is really useful to me to know that these are actually the steps you are following, and that the branch instructions really are missing…. I’m very good at misinterpreting docs!
David Jencks
> On Oct 4, 2021, at 10:39 PM, Gregor Zurowski <gr...@list.zurowski.org> wrote:
>
> I just wanted to confirm that the release guide
> (https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc)
> is not outdated and describes the steps we are following when creating
> new releases. The step to branch off into a new camel-MAJOR.MINOR.x
> branch is missing though, I'll add it in.
>
> I'd be definitely interested in the missing steps that are needed
> preparing the branch for dependent projects.
>
> Thanks,
> Gregor
>
> On Mon, Oct 4, 2021 at 11:47 PM David Jencks <da...@gmail.com> wrote:
>>
>> 1. I got the camel-quarkus build to work with these PRs:
>> https://github.com/apache/camel/pull/6210
>> https://github.com/apache/camel-spring-boot/pull/376
>> both include changes that eventually need to go on other branches, so I don’t want to squash the commits.
>> They also include very substantial changes from simply running the maven build with the new version.
>>
>> (a) Evidently instructions to generate these changes is missing from the existing release instructions, or they weren’t followed or I didn’t wait long enough. I think it should be a step in the release process so that it’s safe to use the branch as a dependency.
>> (b) I don’t see any harm in applying these manually generated changes, but if there is an automated process that will eventually create them and that is preferable please advise when it will occur.
>>
>> In any case the camel-quarkus build is currently broken due to the lack of at least the non-generated changes in these PRs.
>>
>>
>> 2. Writing instructions about updating the website will take quite a while, so we can discuss where they should go. For my convenience I’m going to start with a separate page, and it’s easy enough to move the content if that seems appropriate.
>>
>> David Jencks
>>
>>
>>> On Oct 4, 2021, at 1:59 PM, Andrea Cosentino <an...@gmail.com> wrote:
>>>
>>> If you want to work on one for the website it's fine, but you'll fragment
>>> the release docs more than the current situation. Fragmentation is bad now.
>>> We should try to reduce pages and focus on content.
>>>
>>> Il lun 4 ott 2021, 22:55 Andrea Cosentino <an...@gmail.com> ha scritto:
>>>
>>>> The release guide there it's not outdated. It's related only to camel
>>>> camel-karaf and camel-sb. All the other subprojects have their own release
>>>> guide. -1 to start from a new page. I would start from what we have, which
>>>> is exactly the release steps to release plain camel.
>>>>
>>>> Il lun 4 ott 2021, 22:47 David Jencks <da...@gmail.com> ha
>>>> scritto:
>>>>
>>>>> On a quick glance, that looks outdated (vintage camel 2), unaware of most
>>>>> sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before
>>>>> releasing camel-3.12.0 from it). I don’t think I should try to complete and
>>>>> update those instructions.
>>>>>
>>>>> I think a new page on how to deal with the website would be appropriate,
>>>>> since that’s generally going to happen after the release explained on the
>>>>> existing page.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> David Jencks
>>>>>
>>>>>> On Oct 4, 2021, at 11:00 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>>>
>>>>>> Hi David
>>>>>>
>>>>>> Yes there is the release guide docs at
>>>>>>
>>>>> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
>>>>>>
>>>>>> On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com>
>>>>> wrote:
>>>>>>>
>>>>>>> I believe the Antora build has not yet been updated to include the
>>>>> just released camel-3.12.x and related releases. However, camel-quarkus is
>>>>> trying to use it, which breaks the camel-quarkus build.
>>>>>>>
>>>>>>> I’d like to do this and write up what to do when there’s a release,
>>>>> and hopefully simplify the process a bit.
>>>>>>>
>>>>>>> Is there already such a document?
>>>>>>>
>>>>>>> I actually think it might be best to have a section explaining the
>>>>> structure and interdependencies of the Antora site in the site, along with
>>>>> instructions on what to do when there’s a new release. Alternatively
>>>>> perhaps this could be an AsciiDoc file in camel-website.
>>>>>>>
>>>>>>> Is anyone else working on this? I don’t want to create conflicts or
>>>>> duplicate work.
>>>>>>>
>>>>>>> David Jencks
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>
>>>>>
>>
Re: [Website] Updating after a release
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
I just wanted to confirm that the release guide
(https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc)
is not outdated and describes the steps we are following when creating
new releases. The step to branch off into a new camel-MAJOR.MINOR.x
branch is missing though, I'll add it in.
I'd be definitely interested in the missing steps that are needed
preparing the branch for dependent projects.
Thanks,
Gregor
On Mon, Oct 4, 2021 at 11:47 PM David Jencks <da...@gmail.com> wrote:
>
> 1. I got the camel-quarkus build to work with these PRs:
> https://github.com/apache/camel/pull/6210
> https://github.com/apache/camel-spring-boot/pull/376
> both include changes that eventually need to go on other branches, so I don’t want to squash the commits.
> They also include very substantial changes from simply running the maven build with the new version.
>
> (a) Evidently instructions to generate these changes is missing from the existing release instructions, or they weren’t followed or I didn’t wait long enough. I think it should be a step in the release process so that it’s safe to use the branch as a dependency.
> (b) I don’t see any harm in applying these manually generated changes, but if there is an automated process that will eventually create them and that is preferable please advise when it will occur.
>
> In any case the camel-quarkus build is currently broken due to the lack of at least the non-generated changes in these PRs.
>
>
> 2. Writing instructions about updating the website will take quite a while, so we can discuss where they should go. For my convenience I’m going to start with a separate page, and it’s easy enough to move the content if that seems appropriate.
>
> David Jencks
>
>
> > On Oct 4, 2021, at 1:59 PM, Andrea Cosentino <an...@gmail.com> wrote:
> >
> > If you want to work on one for the website it's fine, but you'll fragment
> > the release docs more than the current situation. Fragmentation is bad now.
> > We should try to reduce pages and focus on content.
> >
> > Il lun 4 ott 2021, 22:55 Andrea Cosentino <an...@gmail.com> ha scritto:
> >
> >> The release guide there it's not outdated. It's related only to camel
> >> camel-karaf and camel-sb. All the other subprojects have their own release
> >> guide. -1 to start from a new page. I would start from what we have, which
> >> is exactly the release steps to release plain camel.
> >>
> >> Il lun 4 ott 2021, 22:47 David Jencks <da...@gmail.com> ha
> >> scritto:
> >>
> >>> On a quick glance, that looks outdated (vintage camel 2), unaware of most
> >>> sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before
> >>> releasing camel-3.12.0 from it). I don’t think I should try to complete and
> >>> update those instructions.
> >>>
> >>> I think a new page on how to deal with the website would be appropriate,
> >>> since that’s generally going to happen after the release explained on the
> >>> existing page.
> >>>
> >>> Thoughts?
> >>>
> >>> David Jencks
> >>>
> >>>> On Oct 4, 2021, at 11:00 AM, Claus Ibsen <cl...@gmail.com> wrote:
> >>>>
> >>>> Hi David
> >>>>
> >>>> Yes there is the release guide docs at
> >>>>
> >>> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
> >>>>
> >>>> On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com>
> >>> wrote:
> >>>>>
> >>>>> I believe the Antora build has not yet been updated to include the
> >>> just released camel-3.12.x and related releases. However, camel-quarkus is
> >>> trying to use it, which breaks the camel-quarkus build.
> >>>>>
> >>>>> I’d like to do this and write up what to do when there’s a release,
> >>> and hopefully simplify the process a bit.
> >>>>>
> >>>>> Is there already such a document?
> >>>>>
> >>>>> I actually think it might be best to have a section explaining the
> >>> structure and interdependencies of the Antora site in the site, along with
> >>> instructions on what to do when there’s a new release. Alternatively
> >>> perhaps this could be an AsciiDoc file in camel-website.
> >>>>>
> >>>>> Is anyone else working on this? I don’t want to create conflicts or
> >>> duplicate work.
> >>>>>
> >>>>> David Jencks
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Claus Ibsen
> >>>> -----------------
> >>>> http://davsclaus.com @davsclaus
> >>>> Camel in Action 2: https://www.manning.com/ibsen2
> >>>
> >>>
>
Re: [Website] Updating after a release
Posted by David Jencks <da...@gmail.com>.
1. I got the camel-quarkus build to work with these PRs:
https://github.com/apache/camel/pull/6210
https://github.com/apache/camel-spring-boot/pull/376
both include changes that eventually need to go on other branches, so I don’t want to squash the commits.
They also include very substantial changes from simply running the maven build with the new version.
(a) Evidently instructions to generate these changes is missing from the existing release instructions, or they weren’t followed or I didn’t wait long enough. I think it should be a step in the release process so that it’s safe to use the branch as a dependency.
(b) I don’t see any harm in applying these manually generated changes, but if there is an automated process that will eventually create them and that is preferable please advise when it will occur.
In any case the camel-quarkus build is currently broken due to the lack of at least the non-generated changes in these PRs.
2. Writing instructions about updating the website will take quite a while, so we can discuss where they should go. For my convenience I’m going to start with a separate page, and it’s easy enough to move the content if that seems appropriate.
David Jencks
> On Oct 4, 2021, at 1:59 PM, Andrea Cosentino <an...@gmail.com> wrote:
>
> If you want to work on one for the website it's fine, but you'll fragment
> the release docs more than the current situation. Fragmentation is bad now.
> We should try to reduce pages and focus on content.
>
> Il lun 4 ott 2021, 22:55 Andrea Cosentino <an...@gmail.com> ha scritto:
>
>> The release guide there it's not outdated. It's related only to camel
>> camel-karaf and camel-sb. All the other subprojects have their own release
>> guide. -1 to start from a new page. I would start from what we have, which
>> is exactly the release steps to release plain camel.
>>
>> Il lun 4 ott 2021, 22:47 David Jencks <da...@gmail.com> ha
>> scritto:
>>
>>> On a quick glance, that looks outdated (vintage camel 2), unaware of most
>>> sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before
>>> releasing camel-3.12.0 from it). I don’t think I should try to complete and
>>> update those instructions.
>>>
>>> I think a new page on how to deal with the website would be appropriate,
>>> since that’s generally going to happen after the release explained on the
>>> existing page.
>>>
>>> Thoughts?
>>>
>>> David Jencks
>>>
>>>> On Oct 4, 2021, at 11:00 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>>>
>>>> Hi David
>>>>
>>>> Yes there is the release guide docs at
>>>>
>>> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
>>>>
>>>> On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com>
>>> wrote:
>>>>>
>>>>> I believe the Antora build has not yet been updated to include the
>>> just released camel-3.12.x and related releases. However, camel-quarkus is
>>> trying to use it, which breaks the camel-quarkus build.
>>>>>
>>>>> I’d like to do this and write up what to do when there’s a release,
>>> and hopefully simplify the process a bit.
>>>>>
>>>>> Is there already such a document?
>>>>>
>>>>> I actually think it might be best to have a section explaining the
>>> structure and interdependencies of the Antora site in the site, along with
>>> instructions on what to do when there’s a new release. Alternatively
>>> perhaps this could be an AsciiDoc file in camel-website.
>>>>>
>>>>> Is anyone else working on this? I don’t want to create conflicts or
>>> duplicate work.
>>>>>
>>>>> David Jencks
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
Re: [Website] Updating after a release
Posted by Andrea Cosentino <an...@gmail.com>.
If you want to work on one for the website it's fine, but you'll fragment
the release docs more than the current situation. Fragmentation is bad now.
We should try to reduce pages and focus on content.
Il lun 4 ott 2021, 22:55 Andrea Cosentino <an...@gmail.com> ha scritto:
> The release guide there it's not outdated. It's related only to camel
> camel-karaf and camel-sb. All the other subprojects have their own release
> guide. -1 to start from a new page. I would start from what we have, which
> is exactly the release steps to release plain camel.
>
> Il lun 4 ott 2021, 22:47 David Jencks <da...@gmail.com> ha
> scritto:
>
>> On a quick glance, that looks outdated (vintage camel 2), unaware of most
>> sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before
>> releasing camel-3.12.0 from it). I don’t think I should try to complete and
>> update those instructions.
>>
>> I think a new page on how to deal with the website would be appropriate,
>> since that’s generally going to happen after the release explained on the
>> existing page.
>>
>> Thoughts?
>>
>> David Jencks
>>
>> > On Oct 4, 2021, at 11:00 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> >
>> > Hi David
>> >
>> > Yes there is the release guide docs at
>> >
>> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
>> >
>> > On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com>
>> wrote:
>> >>
>> >> I believe the Antora build has not yet been updated to include the
>> just released camel-3.12.x and related releases. However, camel-quarkus is
>> trying to use it, which breaks the camel-quarkus build.
>> >>
>> >> I’d like to do this and write up what to do when there’s a release,
>> and hopefully simplify the process a bit.
>> >>
>> >> Is there already such a document?
>> >>
>> >> I actually think it might be best to have a section explaining the
>> structure and interdependencies of the Antora site in the site, along with
>> instructions on what to do when there’s a new release. Alternatively
>> perhaps this could be an AsciiDoc file in camel-website.
>> >>
>> >> Is anyone else working on this? I don’t want to create conflicts or
>> duplicate work.
>> >>
>> >> David Jencks
>> >
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -----------------
>> > http://davsclaus.com @davsclaus
>> > Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
Re: [Website] Updating after a release
Posted by Andrea Cosentino <an...@gmail.com>.
The release guide there it's not outdated. It's related only to camel
camel-karaf and camel-sb. All the other subprojects have their own release
guide. -1 to start from a new page. I would start from what we have, which
is exactly the release steps to release plain camel.
Il lun 4 ott 2021, 22:47 David Jencks <da...@gmail.com> ha scritto:
> On a quick glance, that looks outdated (vintage camel 2), unaware of most
> sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before
> releasing camel-3.12.0 from it). I don’t think I should try to complete and
> update those instructions.
>
> I think a new page on how to deal with the website would be appropriate,
> since that’s generally going to happen after the release explained on the
> existing page.
>
> Thoughts?
>
> David Jencks
>
> > On Oct 4, 2021, at 11:00 AM, Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi David
> >
> > Yes there is the release guide docs at
> >
> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
> >
> > On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com>
> wrote:
> >>
> >> I believe the Antora build has not yet been updated to include the just
> released camel-3.12.x and related releases. However, camel-quarkus is
> trying to use it, which breaks the camel-quarkus build.
> >>
> >> I’d like to do this and write up what to do when there’s a release, and
> hopefully simplify the process a bit.
> >>
> >> Is there already such a document?
> >>
> >> I actually think it might be best to have a section explaining the
> structure and interdependencies of the Antora site in the site, along with
> instructions on what to do when there’s a new release. Alternatively
> perhaps this could be an AsciiDoc file in camel-website.
> >>
> >> Is anyone else working on this? I don’t want to create conflicts or
> duplicate work.
> >>
> >> David Jencks
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
Re: [Website] Updating after a release
Posted by David Jencks <da...@gmail.com>.
On a quick glance, that looks outdated (vintage camel 2), unaware of most sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before releasing camel-3.12.0 from it). I don’t think I should try to complete and update those instructions.
I think a new page on how to deal with the website would be appropriate, since that’s generally going to happen after the release explained on the existing page.
Thoughts?
David Jencks
> On Oct 4, 2021, at 11:00 AM, Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi David
>
> Yes there is the release guide docs at
> https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
>
> On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com> wrote:
>>
>> I believe the Antora build has not yet been updated to include the just released camel-3.12.x and related releases. However, camel-quarkus is trying to use it, which breaks the camel-quarkus build.
>>
>> I’d like to do this and write up what to do when there’s a release, and hopefully simplify the process a bit.
>>
>> Is there already such a document?
>>
>> I actually think it might be best to have a section explaining the structure and interdependencies of the Antora site in the site, along with instructions on what to do when there’s a new release. Alternatively perhaps this could be an AsciiDoc file in camel-website.
>>
>> Is anyone else working on this? I don’t want to create conflicts or duplicate work.
>>
>> David Jencks
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: [Website] Updating after a release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi David
Yes there is the release guide docs at
https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc
On Mon, Oct 4, 2021 at 6:46 PM David Jencks <da...@gmail.com> wrote:
>
> I believe the Antora build has not yet been updated to include the just released camel-3.12.x and related releases. However, camel-quarkus is trying to use it, which breaks the camel-quarkus build.
>
> I’d like to do this and write up what to do when there’s a release, and hopefully simplify the process a bit.
>
> Is there already such a document?
>
> I actually think it might be best to have a section explaining the structure and interdependencies of the Antora site in the site, along with instructions on what to do when there’s a new release. Alternatively perhaps this could be an AsciiDoc file in camel-website.
>
> Is anyone else working on this? I don’t want to create conflicts or duplicate work.
>
> David Jencks
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2