Hi Claus, Yes, not a problem, you usually run the release-website.sh script post-release, i.e. after deploying the artifacts to Maven Central. I can add more details about the expected output when I cut the next release (do we already have plans for such?).
I am not sure about step 11 though. I have asked around about the actual procedure on how the Javadoc upload should be performed, but never received a definite answer. Thanks, Gregor On Sat, Aug 20, 2016 at 10:41 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi Gregor > > I want to bring you into this talk as you have done the last number of > releases with success. > > I wonder if in step 10 on this guide > http://camel.apache.org/release-guide.html > > where you run the script release-website > can this script be run post a release? From looking at the script it seems so. > > The guide says "Check the console output and finish this step (run svn > ci) manually after checking the artifacts." > Can this be more elaborated what the output is and what to do? Or > would anyone know what to do after running the script? > > > Step 11 talks about updating javadoc, but it seems the content on that > SVN repo is out-dated > https://svn.apache.org/repos/infra/websites/production/camel/content/maven/ > > If you look there its Camel 2.15 as the last. > > I wonder if we can get the guide updated so we can update the javadoc > on the camel website? > > btw you can always find javadoc from a central website like: > http://www.javadoc.io/doc/org.apache.camel/camel-core/2.17.3 > > > > On Mon, Aug 15, 2016 at 5:23 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> On Thu, Aug 11, 2016 at 6:21 PM, Daniel Kulp <dk...@apache.org> wrote: >>> >>> Claus, >>> >>> Thanks… >>> >>> I think there are other steps I haven’t had time to finish (updating >>> schemas and such). Did you handle those as well or do I need to circle >>> back on it? >>> >> >> No I didn't upload any schemas etc. as that likely needs to be done >> from the build that was done for the release. However we could likely >> find the XSD scheams from the 2.17.3 binaries and upload them manually >> if they are no longer on your laptop. >> >> I wonder if there isn't something we can do to make the release >> producer smarter and more automated. Can we have some scripts that can >> download from the JARs a release and then upload the needed schemas >> and javadoc etc. >> >> Then we can do that as a post install procedure after the artifacts >> has been promoted to maven central. >> And then we could use a CI server to do the regular release. >> >> >> The steps I did was 14, 15, 16 and 17 from this page: >> http://camel.apache.org/release-guide.html >> And I did 18 last weekend ;) >> >> >> >> >> >>> Dan >>> >>> >>>> On Aug 11, 2016, at 11:02 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>>> >>>> Hi >>>> >>>> Just to close this I did the announcement. >>>> >>>> Thanks Dan for cutting the release. >>>> >>>> >>>> >>>> On Wed, Aug 10, 2016 at 8:25 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>>>> Hi >>>>> >>>>> I dont think we have announced this released yet. Can we have that done. >>>>> >>>>> >>>>> >>>>> On Mon, Aug 8, 2016 at 3:33 PM, Daniel Kulp <dk...@apache.org> wrote: >>>>>> We have 9 +1 votes and no other votes. This vote passes.. >>>>>> >>>>>> Dan >>>>>> >>>>>> >>>>>> >>>>>>> On Aug 4, 2016, at 4:20 PM, Daniel Kulp <dk...@apache.org> wrote: >>>>>>> >>>>>>> >>>>>>> This is a vote to release Camel 2.17.3 >>>>>>> >>>>>>> Staging repository: >>>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1052/ >>>>>>> <https://repository.apache.org/content/repositories/orgapachecamel-1052/> >>>>>>> >>>>>>> Tag: >>>>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ad245911cc8db1a8c57ec7825f7fd630f2a4ec58 >>>>>>> >>>>>>> <https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ad245911cc8db1a8c57ec7825f7fd630f2a4ec58> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Here is my +1 >>>>>>> >>>>>>> -- >>>>>>> Daniel Kulp >>>>>>> dk...@apache.org <mailto:dk...@apache.org> - http://dankulp.com/blog >>>>>>> <http://dankulp.com/blog> >>>>>>> Talend Community Coder - http://coders.talend.com >>>>>>> <http://coders.talend.com/> >>>>>> >>>>>> -- >>>>>> Daniel Kulp >>>>>> dk...@apache.org <mailto:dk...@apache.org> - http://dankulp.com/blog >>>>>> <http://dankulp.com/blog> >>>>>> Talend Community Coder - http://coders.talend.com >>>>>> <http://coders.talend.com/> >>>>> >>>>> >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> ----------------- >>>>> http://davsclaus.com @davsclaus >>>>> Camel in Action 2: https://www.manning.com/ibsen2 >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> ----------------- >>>> http://davsclaus.com @davsclaus >>>> Camel in Action 2: https://www.manning.com/ibsen2 >>> >>> -- >>> Daniel Kulp >>> dk...@apache.org <mailto:dk...@apache.org> - http://dankulp.com/blog >>> <http://dankulp.com/blog> >>> Talend Community Coder - http://coders.talend.com >>> <http://coders.talend.com/> >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
