Re: ReleaseWizard tool
Hi again, The "default" reference guide location still redirects to the 8_2 guide. The 8.2 release is still in our mirrors: http://www.apache.org/dist/lucene/solr/ <http://www.apache.org/dist/lucene/solr/> You said you would come back to completing the post-release steps Ishan, there may be more steps than these two you missed. You are the 8.3.0 RM so only you would know what is completed and not? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 13. nov. 2019 kl. 22:01 skrev Jan Høydahl : > > Ishan, do you have some feedback on the ReleaseWizard? > > Also I notice that the redirect to the latest refGuide is not changed on the > website, so e.g > https://lucene.apache.org/solr/guide/distributed-requests.html > <https://lucene.apache.org/solr/guide/distributed-requests.html> redirects to > 8_2 guide instead of 8_3 guide. > The reeleaseWizard has a step for that so I wonder if you skipped it or if it > was not clear or perhaps buggy? > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com <http://www.cominvent.com/> > >> 8. nov. 2019 kl. 10:19 skrev Jan Høydahl > <mailto:jan@cominvent.com>>: >> >> Hi, >> >> Looking forward to feedback on the tool Ishan! >> >> One concrete question: >> I see that v8.2.0 is still in the release repo >> http://www.apache.org/dist/lucene/solr/ >> <http://www.apache.org/dist/lucene/solr/> >> The Wizard step "9.10. Stop mirroring old releases" should have told you to >> remove v8.2.0 form the repo. >> Did you not yet complete all steps in the Wizard or was there a bug so that >> step did not display for you? >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >> >>> 6. nov. 2019 kl. 21:46 skrev Ishan Chattopadhyaya >>> mailto:ichattopadhy...@gmail.com>>: >>> >>> Jan, I owe you the list of issues and filing of jiras regarding issues i >>> faced with the tool during 8.3.0. I'll try to do so this weekend. >>> >>> On Thu, 7 Nov, 2019, 2:03 AM Cassandra Targett, >> <mailto:casstarg...@gmail.com>> wrote: >>> I was far too swamped back in July to be able to take a look at this new >>> tool, but I’ve had a few minutes now and while I’ve never done a release, >>> it really looks very helpful. >>> >>> Jan, I note in your initial description in this thread and in LUCENE-8852 >>> you mention the release wizard tool allows you to "generate a full Asciidoc >>> guide for the release” - what is it generating? I’m not a python expert, >>> but I did notice it requires & uses the asciidoctor gem. That’s not how we >>> make the Ref Guide so it must be for another purpose, but I’m not able to >>> fully figure it out. >>> >>> Sorry for the late thread resurrection, as I said I only now have a bit of >>> time to catch up here. >>> >>> Thanks, >>> Cassandra >>> On Jul 5, 2019, 3:11 PM -0500, Jan Høydahl >> <mailto:jan@cominvent.com>>, wrote: >>>> Go for it. For me it was a very interesting experience, and I will likely >>>> do it again at some point! >>>> >>>> Jan Høydahl >>>> >>>> 5. jul. 2019 kl. 21:00 skrev David Smiley >>> <mailto:david.w.smi...@gmail.com>>: >>>> >>>>> Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to >>>>> help :-) >>>>> >>>>> ~ David Smiley >>>>> Apache Lucene/Solr Search Developer >>>>> http://www.linkedin.com/in/davidwsmiley >>>>> <http://www.linkedin.com/in/davidwsmiley> >>>>> >>>>> On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl >>>> <mailto:jan@cominvent.com>> wrote: >>>>> I wrote an article at LinkedIN pulse about the release process and the >>>>> tool: >>>>> https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ >>>>> >>>>> <https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-h%C3%B8ydahl/> >>>>> >>>>> -- >>>>> Jan Høydahl, search solution architect >>>>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>>>> >>>>>> 11. jun. 2019 kl. 10:46 skrev Jan Høydahl >>>>> <mailto:jan@cominve
Re: ReleaseWizard tool
Ishan, do you have some feedback on the ReleaseWizard? Also I notice that the redirect to the latest refGuide is not changed on the website, so e.g https://lucene.apache.org/solr/guide/distributed-requests.html <https://lucene.apache.org/solr/guide/distributed-requests.html> redirects to 8_2 guide instead of 8_3 guide. The reeleaseWizard has a step for that so I wonder if you skipped it or if it was not clear or perhaps buggy? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 8. nov. 2019 kl. 10:19 skrev Jan Høydahl : > > Hi, > > Looking forward to feedback on the tool Ishan! > > One concrete question: > I see that v8.2.0 is still in the release repo > http://www.apache.org/dist/lucene/solr/ > <http://www.apache.org/dist/lucene/solr/> > The Wizard step "9.10. Stop mirroring old releases" should have told you to > remove v8.2.0 form the repo. > Did you not yet complete all steps in the Wizard or was there a bug so that > step did not display for you? > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com <http://www.cominvent.com/> > >> 6. nov. 2019 kl. 21:46 skrev Ishan Chattopadhyaya > <mailto:ichattopadhy...@gmail.com>>: >> >> Jan, I owe you the list of issues and filing of jiras regarding issues i >> faced with the tool during 8.3.0. I'll try to do so this weekend. >> >> On Thu, 7 Nov, 2019, 2:03 AM Cassandra Targett, > <mailto:casstarg...@gmail.com>> wrote: >> I was far too swamped back in July to be able to take a look at this new >> tool, but I’ve had a few minutes now and while I’ve never done a release, it >> really looks very helpful. >> >> Jan, I note in your initial description in this thread and in LUCENE-8852 >> you mention the release wizard tool allows you to "generate a full Asciidoc >> guide for the release” - what is it generating? I’m not a python expert, but >> I did notice it requires & uses the asciidoctor gem. That’s not how we make >> the Ref Guide so it must be for another purpose, but I’m not able to fully >> figure it out. >> >> Sorry for the late thread resurrection, as I said I only now have a bit of >> time to catch up here. >> >> Thanks, >> Cassandra >> On Jul 5, 2019, 3:11 PM -0500, Jan Høydahl > <mailto:jan@cominvent.com>>, wrote: >>> Go for it. For me it was a very interesting experience, and I will likely >>> do it again at some point! >>> >>> Jan Høydahl >>> >>> 5. jul. 2019 kl. 21:00 skrev David Smiley >> <mailto:david.w.smi...@gmail.com>>: >>> >>>> Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to >>>> help :-) >>>> >>>> ~ David Smiley >>>> Apache Lucene/Solr Search Developer >>>> http://www.linkedin.com/in/davidwsmiley >>>> <http://www.linkedin.com/in/davidwsmiley> >>>> >>>> On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl >>> <mailto:jan@cominvent.com>> wrote: >>>> I wrote an article at LinkedIN pulse about the release process and the >>>> tool: >>>> https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ >>>> <https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-h%C3%B8ydahl/> >>>> >>>> -- >>>> Jan Høydahl, search solution architect >>>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>>> >>>>> 11. jun. 2019 kl. 10:46 skrev Jan Høydahl >>>> <mailto:jan@cominvent.com>>: >>>>> >>>>> I have now pushed the ReleaseWizard tool in >>>>> https://issues.apache.org/jira/browse/LUCENE-8852 >>>>> <https://issues.apache.org/jira/browse/LUCENE-8852> >>>>> Appreciate all kind of feedback! >>>>> >>>>> -- >>>>> Jan Høydahl, search solution architect >>>>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>>>> >>>>>> 1. jun. 2019 kl. 20:26 skrev Jan Høydahl >>>>> <mailto:jan@cominvent.com>>: >>>>>> >>>>>> As I said, I’ll start a thread about this, please reply to that instead >>>>>> of continuing discussion in this thread which is about releaseWizard :) >>>>>> >>>>>> Jan Høydahl >>>>>> >>>>>> 1. jun. 2019 kl. 15:53 skrev Michael Sokolov >
Re: ReleaseWizard tool
Hi, Looking forward to feedback on the tool Ishan! One concrete question: I see that v8.2.0 is still in the release repo http://www.apache.org/dist/lucene/solr/ <http://www.apache.org/dist/lucene/solr/> The Wizard step "9.10. Stop mirroring old releases" should have told you to remove v8.2.0 form the repo. Did you not yet complete all steps in the Wizard or was there a bug so that step did not display for you? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 6. nov. 2019 kl. 21:46 skrev Ishan Chattopadhyaya : > > Jan, I owe you the list of issues and filing of jiras regarding issues i > faced with the tool during 8.3.0. I'll try to do so this weekend. > > On Thu, 7 Nov, 2019, 2:03 AM Cassandra Targett, <mailto:casstarg...@gmail.com>> wrote: > I was far too swamped back in July to be able to take a look at this new > tool, but I’ve had a few minutes now and while I’ve never done a release, it > really looks very helpful. > > Jan, I note in your initial description in this thread and in LUCENE-8852 you > mention the release wizard tool allows you to "generate a full Asciidoc guide > for the release” - what is it generating? I’m not a python expert, but I did > notice it requires & uses the asciidoctor gem. That’s not how we make the Ref > Guide so it must be for another purpose, but I’m not able to fully figure it > out. > > Sorry for the late thread resurrection, as I said I only now have a bit of > time to catch up here. > > Thanks, > Cassandra > On Jul 5, 2019, 3:11 PM -0500, Jan Høydahl <mailto:jan@cominvent.com>>, wrote: >> Go for it. For me it was a very interesting experience, and I will likely do >> it again at some point! >> >> Jan Høydahl >> >> 5. jul. 2019 kl. 21:00 skrev David Smiley > <mailto:david.w.smi...@gmail.com>>: >> >>> Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to >>> help :-) >>> >>> ~ David Smiley >>> Apache Lucene/Solr Search Developer >>> http://www.linkedin.com/in/davidwsmiley >>> <http://www.linkedin.com/in/davidwsmiley> >>> >>> On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl >> <mailto:jan@cominvent.com>> wrote: >>> I wrote an article at LinkedIN pulse about the release process and the tool: >>> https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ >>> <https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-h%C3%B8ydahl/> >>> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>> >>>> 11. jun. 2019 kl. 10:46 skrev Jan Høydahl >>> <mailto:jan@cominvent.com>>: >>>> >>>> I have now pushed the ReleaseWizard tool in >>>> https://issues.apache.org/jira/browse/LUCENE-8852 >>>> <https://issues.apache.org/jira/browse/LUCENE-8852> >>>> Appreciate all kind of feedback! >>>> >>>> -- >>>> Jan Høydahl, search solution architect >>>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>>> >>>>> 1. jun. 2019 kl. 20:26 skrev Jan Høydahl >>>> <mailto:jan@cominvent.com>>: >>>>> >>>>> As I said, I’ll start a thread about this, please reply to that instead >>>>> of continuing discussion in this thread which is about releaseWizard :) >>>>> >>>>> Jan Høydahl >>>>> >>>>> 1. jun. 2019 kl. 15:53 skrev Michael Sokolov >>>> <mailto:msoko...@gmail.com>>: >>>>> >>>>>> I'm not sure what the proper way to use fix version is. Suppose you back >>>>>> port a fix to multiple branches? Should fixVersion list all of them? >>>>>> Just pick one? >>>>>> >>>>>> On Wed, May 29, 2019, 6:00 PM Jan Høydahl >>>>> <mailto:jan@cominvent.com>> wrote: >>>>>> My releaseWizard tool is getting more complete as the 7.7.2 release >>>>>> progresses. Will share the code just after I complete all steps. >>>>>> >>>>>> I tested relasedocmaker and it digs up all the JIRA issues marked as >>>>>> RESOLVED for the version and creates two files. >>>>>> CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG >>>>>> FIXES etc >>>>>> One problem I found with how the CHANGELOG wo
Re: ReleaseWizard tool
That explains it - I suspected it didn’t have anything to do with the Ref Guide, but wanted to be sure. Very nice, thanks for working on it! Cassandra On Nov 6, 2019, 2:48 PM -0600, Jan Høydahl , wrote: > It has nothing to do with the RefGuide :) > It will generate a "release TODO" document in adoc format for this specific > release, which details all the phases, all the steps in each phase, and all > the exact cmdline commands, with correct paths and version numbers, to run > for each step. > You don't really need it, because the interactive CLI menus in the tool keeps > you up to date on what steps remain and what to do, but it is nice for a full > overview of the process for preparation or whatever. > The guide will be different if you are doing a major, minor or bugfix > release, as there are different steps needed for each. > Then we generate a HTML page with embedded CSS from the adoc, see > https://www.dropbox.com/s/ug9yckvbwqwetvs/Lucene%3ASolr%20Release%208.3.0.html?dl=0 > for an example HTML, and > https://www.dropbox.com/s/wulog2ipweth4mp/lucene_solr_release_8.3.0.adoc?dl=0 > for the corresponding adoc. Try it :) > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > > 6. nov. 2019 kl. 21:32 skrev Cassandra Targett : > > > > I was far too swamped back in July to be able to take a look at this new > > tool, but I’ve had a few minutes now and while I’ve never done a release, > > it really looks very helpful. > > > > Jan, I note in your initial description in this thread and in LUCENE-8852 > > you mention the release wizard tool allows you to "generate a full Asciidoc > > guide for the release” - what is it generating? I’m not a python expert, > > but I did notice it requires & uses the asciidoctor gem. That’s not how we > > make the Ref Guide so it must be for another purpose, but I’m not able to > > fully figure it out. > > > > Sorry for the late thread resurrection, as I said I only now have a bit of > > time to catch up here. > > > > Thanks, > > Cassandra > > On Jul 5, 2019, 3:11 PM -0500, Jan Høydahl , wrote: > > > Go for it. For me it was a very interesting experience, and I will likely > > > do it again at some point! > > > > > > Jan Høydahl > > > > > > 5. jul. 2019 kl. 21:00 skrev David Smiley : > > > > > > > Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to > > > > help :-) > > > > > > > > ~ David Smiley > > > > Apache Lucene/Solr Search Developer > > > > http://www.linkedin.com/in/davidwsmiley > > > > > > > > > > > > > On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl > > > > > wrote: > > > > > > I wrote an article at LinkedIN pulse about the release process and > > > > > > the tool: > > > > > > https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ > > > > > > > > > > > > -- > > > > > > Jan Høydahl, search solution architect > > > > > > Cominvent AS - www.cominvent.com > > > > > > > > > > > > > 11. jun. 2019 kl. 10:46 skrev Jan Høydahl : > > > > > > > > > > > > > > I have now pushed the ReleaseWizard tool in > > > > > > > https://issues.apache.org/jira/browse/LUCENE-8852 > > > > > > > Appreciate all kind of feedback! > > > > > > > > > > > > > > -- > > > > > > > Jan Høydahl, search solution architect > > > > > > > Cominvent AS - www.cominvent.com > > > > > > > > > > > > > > > 1. jun. 2019 kl. 20:26 skrev Jan Høydahl > > > > > > > > : > > > > > > > > > > > > > > > > As I said, I’ll start a thread about this, please reply to that > > > > > > > > instead of continuing discussion in this thread which is about > > > > > > > > releaseWizard :) > > > > > > > > > > > > > > > > Jan Høydahl > > > > > > > > > > > > > > > > 1. jun. 2019 kl. 15:53 skrev Michael Sokolov > > > > > > > > : > > > > > > > > > > > > > > > > > I'm not sure what the proper way to use fix version is. > > > > > > > > > Suppose you back port a fix to mu
Re: ReleaseWizard tool
It has nothing to do with the RefGuide :) It will generate a "release TODO" document in adoc format for this specific release, which details all the phases, all the steps in each phase, and all the exact cmdline commands, with correct paths and version numbers, to run for each step. You don't really need it, because the interactive CLI menus in the tool keeps you up to date on what steps remain and what to do, but it is nice for a full overview of the process for preparation or whatever. The guide will be different if you are doing a major, minor or bugfix release, as there are different steps needed for each. Then we generate a HTML page with embedded CSS from the adoc, see https://www.dropbox.com/s/ug9yckvbwqwetvs/Lucene%3ASolr%20Release%208.3.0.html?dl=0 <https://www.dropbox.com/s/ug9yckvbwqwetvs/Lucene:Solr%20Release%208.3.0.html?dl=0> for an example HTML, and https://www.dropbox.com/s/wulog2ipweth4mp/lucene_solr_release_8.3.0.adoc?dl=0 <https://www.dropbox.com/s/wulog2ipweth4mp/lucene_solr_release_8.3.0.adoc?dl=0> for the corresponding adoc. Try it :) -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 6. nov. 2019 kl. 21:32 skrev Cassandra Targett : > > I was far too swamped back in July to be able to take a look at this new > tool, but I’ve had a few minutes now and while I’ve never done a release, it > really looks very helpful. > > Jan, I note in your initial description in this thread and in LUCENE-8852 you > mention the release wizard tool allows you to "generate a full Asciidoc guide > for the release” - what is it generating? I’m not a python expert, but I did > notice it requires & uses the asciidoctor gem. That’s not how we make the Ref > Guide so it must be for another purpose, but I’m not able to fully figure it > out. > > Sorry for the late thread resurrection, as I said I only now have a bit of > time to catch up here. > > Thanks, > Cassandra > On Jul 5, 2019, 3:11 PM -0500, Jan Høydahl , wrote: >> Go for it. For me it was a very interesting experience, and I will likely do >> it again at some point! >> >> Jan Høydahl >> >> 5. jul. 2019 kl. 21:00 skrev David Smiley > <mailto:david.w.smi...@gmail.com>>: >> >>> Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to >>> help :-) >>> >>> ~ David Smiley >>> Apache Lucene/Solr Search Developer >>> http://www.linkedin.com/in/davidwsmiley >>> <http://www.linkedin.com/in/davidwsmiley> >>> >>> On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl >> <mailto:jan@cominvent.com>> wrote: >>> I wrote an article at LinkedIN pulse about the release process and the tool: >>> https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ >>> <https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-h%C3%B8ydahl/> >>> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>> >>>> 11. jun. 2019 kl. 10:46 skrev Jan Høydahl >>> <mailto:jan@cominvent.com>>: >>>> >>>> I have now pushed the ReleaseWizard tool in >>>> https://issues.apache.org/jira/browse/LUCENE-8852 >>>> <https://issues.apache.org/jira/browse/LUCENE-8852> >>>> Appreciate all kind of feedback! >>>> >>>> -- >>>> Jan Høydahl, search solution architect >>>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>>> >>>>> 1. jun. 2019 kl. 20:26 skrev Jan Høydahl >>>> <mailto:jan@cominvent.com>>: >>>>> >>>>> As I said, I’ll start a thread about this, please reply to that instead >>>>> of continuing discussion in this thread which is about releaseWizard :) >>>>> >>>>> Jan Høydahl >>>>> >>>>> 1. jun. 2019 kl. 15:53 skrev Michael Sokolov >>>> <mailto:msoko...@gmail.com>>: >>>>> >>>>>> I'm not sure what the proper way to use fix version is. Suppose you back >>>>>> port a fix to multiple branches? Should fixVersion list all of them? >>>>>> Just pick one? >>>>>> >>>>>> On Wed, May 29, 2019, 6:00 PM Jan Høydahl >>>>> <mailto:jan@cominvent.com>> wrote: >>>>>> My releaseWizard tool is getting more complete as the 7.7.2 release >>>>>> progresses. Will share the code just after I complete all steps.
Re: ReleaseWizard tool
Jan, I owe you the list of issues and filing of jiras regarding issues i faced with the tool during 8.3.0. I'll try to do so this weekend. On Thu, 7 Nov, 2019, 2:03 AM Cassandra Targett, wrote: > I was far too swamped back in July to be able to take a look at this new > tool, but I’ve had a few minutes now and while I’ve never done a release, > it really looks very helpful. > > Jan, I note in your initial description in this thread and in LUCENE-8852 > you mention the release wizard tool allows you to "generate a full > Asciidoc guide for the release” - what is it generating? I’m not a python > expert, but I did notice it requires & uses the asciidoctor gem. That’s not > how we make the Ref Guide so it must be for another purpose, but I’m not > able to fully figure it out. > > Sorry for the late thread resurrection, as I said I only now have a bit of > time to catch up here. > > Thanks, > Cassandra > On Jul 5, 2019, 3:11 PM -0500, Jan Høydahl , wrote: > > Go for it. For me it was a very interesting experience, and I will likely > do it again at some point! > > Jan Høydahl > > 5. jul. 2019 kl. 21:00 skrev David Smiley : > > Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to > help :-) > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl wrote: > >> I wrote an article at LinkedIN pulse about the release process and the >> tool: >> https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> 11. jun. 2019 kl. 10:46 skrev Jan Høydahl : >> >> I have now pushed the ReleaseWizard tool in >> https://issues.apache.org/jira/browse/LUCENE-8852 >> Appreciate all kind of feedback! >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> 1. jun. 2019 kl. 20:26 skrev Jan Høydahl : >> >> As I said, I’ll start a thread about this, please reply to that instead >> of continuing discussion in this thread which is about releaseWizard :) >> >> Jan Høydahl >> >> 1. jun. 2019 kl. 15:53 skrev Michael Sokolov : >> >> I'm not sure what the proper way to use fix version is. Suppose you back >> port a fix to multiple branches? Should fixVersion list all of them? Just >> pick one? >> >> On Wed, May 29, 2019, 6:00 PM Jan Høydahl wrote: >> >>> My releaseWizard tool is getting more complete as the 7.7.2 release >>> progresses. Will share the code just after I complete all steps. >>> >>> I tested relasedocmaker and it digs up all the JIRA issues marked as >>> RESOLVED for the version and creates two files. >>> CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG >>> FIXES etc >>> One problem I found with how the CHANGELOG works is that it adds all >>> issues having the version in fixVersion, even if the feature >>> was already released in an earlier version. That is because of the way >>> we use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" >>> at the same time, even if we know that 8.2 is the version the feature >>> will be released. If we stop always adding "master" to fixVersion >>> but strive to keep it a list of version the feature/bugfix is FIRST >>> introduced, then this tool will do the correct job. >>> >>> RELEASENOTES.md lists "...new developer and user-facing >>> incompatibilities, important issues, features, and major improvements.". >>> And if we enable the JIRA field "Release Notes" (we don't have it now), >>> the content of that field will be used in the release notes instead of the >>> JIRA description. >>> You can select any issue to surface in RELEASENOTES by adding a certain >>> label, by default "backward-incompatible". >>> >>> I think it could be a welcome addition to our flow. We cant' expect the >>> output from the tool to be used as-is, sometimes a major feature spans >>> multiple >>> JIRAs etc, but it could be a good starting point, and would shift the >>> burden of documenting important and breaking changes from release-time to >>> commit-time, >>> if we as committers manage to adjust our routines. We could even have a >>> weekly job that runs the releasedocmaker and sends the output to dev@ >>> list for active branches, to keep focus. >>> >>> --
Re: ReleaseWizard tool
I was far too swamped back in July to be able to take a look at this new tool, but I’ve had a few minutes now and while I’ve never done a release, it really looks very helpful. Jan, I note in your initial description in this thread and in LUCENE-8852 you mention the release wizard tool allows you to "generate a full Asciidoc guide for the release” - what is it generating? I’m not a python expert, but I did notice it requires & uses the asciidoctor gem. That’s not how we make the Ref Guide so it must be for another purpose, but I’m not able to fully figure it out. Sorry for the late thread resurrection, as I said I only now have a bit of time to catch up here. Thanks, Cassandra On Jul 5, 2019, 3:11 PM -0500, Jan Høydahl , wrote: > Go for it. For me it was a very interesting experience, and I will likely do > it again at some point! > > Jan Høydahl > > 5. jul. 2019 kl. 21:00 skrev David Smiley : > > > Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to > > help :-) > > > > ~ David Smiley > > Apache Lucene/Solr Search Developer > > http://www.linkedin.com/in/davidwsmiley > > > > > > > On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl wrote: > > > > I wrote an article at LinkedIN pulse about the release process and the > > > > tool: > > > > https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ > > > > > > > > -- > > > > Jan Høydahl, search solution architect > > > > Cominvent AS - www.cominvent.com > > > > > > > > > 11. jun. 2019 kl. 10:46 skrev Jan Høydahl : > > > > > > > > > > I have now pushed the ReleaseWizard tool in > > > > > https://issues.apache.org/jira/browse/LUCENE-8852 > > > > > Appreciate all kind of feedback! > > > > > > > > > > -- > > > > > Jan Høydahl, search solution architect > > > > > Cominvent AS - www.cominvent.com > > > > > > > > > > > 1. jun. 2019 kl. 20:26 skrev Jan Høydahl : > > > > > > > > > > > > As I said, I’ll start a thread about this, please reply to that > > > > > > instead of continuing discussion in this thread which is about > > > > > > releaseWizard :) > > > > > > > > > > > > Jan Høydahl > > > > > > > > > > > > 1. jun. 2019 kl. 15:53 skrev Michael Sokolov : > > > > > > > > > > > > > I'm not sure what the proper way to use fix version is. Suppose > > > > > > > you back port a fix to multiple branches? Should fixVersion list > > > > > > > all of them? Just pick one? > > > > > > > > > > > > > > > On Wed, May 29, 2019, 6:00 PM Jan Høydahl > > > > > > > > wrote: > > > > > > > > > My releaseWizard tool is getting more complete as the 7.7.2 > > > > > > > > > release progresses. Will share the code just after I complete > > > > > > > > > all steps. > > > > > > > > > > > > > > > > > > I tested relasedocmaker and it digs up all the JIRA issues > > > > > > > > > marked as RESOLVED for the version and creates two files. > > > > > > > > > CHANGELOG.md simply lists all issues under headings > > > > > > > > > IMPROVEMENTS, BUG FIXES etc > > > > > > > > > One problem I found with how the CHANGELOG works is that it > > > > > > > > > adds all issues having the version in fixVersion, even if the > > > > > > > > > feature > > > > > > > > > was already released in an earlier version. That is because > > > > > > > > > of the way we use JIRA fixVersion, adding both e.g. "master > > > > > > > > > (9.0)" and "8.2" > > > > > > > > > at the same time, even if we know that 8.2 is the version the > > > > > > > > > feature will be released. If we stop always adding "master" > > > > > > > > > to fixVersion > > > > > > > > > but strive to keep it a list of version the feature/bugfix is > > > > > > > > > FIRST introduced, then this tool will do the correct job. > > > > > > > > > > > > > > > > >
Re: ReleaseWizard tool
Go for it. For me it was a very interesting experience, and I will likely do it again at some point! Jan Høydahl > 5. jul. 2019 kl. 21:00 skrev David Smiley : > > Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to help > :-) > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > >> On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl wrote: >> I wrote an article at LinkedIN pulse about the release process and the tool: >> https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >>> 11. jun. 2019 kl. 10:46 skrev Jan Høydahl : >>> >>> I have now pushed the ReleaseWizard tool in >>> https://issues.apache.org/jira/browse/LUCENE-8852 >>> Appreciate all kind of feedback! >>> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com >>> >>>> 1. jun. 2019 kl. 20:26 skrev Jan Høydahl : >>>> >>>> As I said, I’ll start a thread about this, please reply to that instead of >>>> continuing discussion in this thread which is about releaseWizard :) >>>> >>>> Jan Høydahl >>>> >>>>> 1. jun. 2019 kl. 15:53 skrev Michael Sokolov : >>>>> >>>>> I'm not sure what the proper way to use fix version is. Suppose you back >>>>> port a fix to multiple branches? Should fixVersion list all of them? Just >>>>> pick one? >>>>> >>>>>> On Wed, May 29, 2019, 6:00 PM Jan Høydahl wrote: >>>>>> My releaseWizard tool is getting more complete as the 7.7.2 release >>>>>> progresses. Will share the code just after I complete all steps. >>>>>> >>>>>> I tested relasedocmaker and it digs up all the JIRA issues marked as >>>>>> RESOLVED for the version and creates two files. >>>>>> CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG >>>>>> FIXES etc >>>>>> One problem I found with how the CHANGELOG works is that it adds all >>>>>> issues having the version in fixVersion, even if the feature >>>>>> was already released in an earlier version. That is because of the way >>>>>> we use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" >>>>>> at the same time, even if we know that 8.2 is the version the feature >>>>>> will be released. If we stop always adding "master" to fixVersion >>>>>> but strive to keep it a list of version the feature/bugfix is FIRST >>>>>> introduced, then this tool will do the correct job. >>>>>> >>>>>> RELEASENOTES.md lists "...new developer and user-facing >>>>>> incompatibilities, important issues, features, and major improvements.". >>>>>> And if we enable the JIRA field "Release Notes" (we don't have it now), >>>>>> the content of that field will be used in the release notes instead of >>>>>> the JIRA description. >>>>>> You can select any issue to surface in RELEASENOTES by adding a certain >>>>>> label, by default "backward-incompatible". >>>>>> >>>>>> I think it could be a welcome addition to our flow. We cant' expect the >>>>>> output from the tool to be used as-is, sometimes a major feature spans >>>>>> multiple >>>>>> JIRAs etc, but it could be a good starting point, and would shift the >>>>>> burden of documenting important and breaking changes from release-time >>>>>> to commit-time, >>>>>> if we as committers manage to adjust our routines. We could even have a >>>>>> weekly job that runs the releasedocmaker and sends the output to dev@ >>>>>> list for active branches, to keep focus. >>>>>> >>>>>> -- >>>>>> Jan Høydahl, search solution architect >>>>>> Cominvent AS - www.cominvent.com >>>>>> >>>>>>> 17. mai 2019 kl. 13:45 skrev Jan Høydahl : >>>>>>> >>>>>>> Yes, I thought we could use >>>>>>> https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ to >>>>>>>
Re: ReleaseWizard tool
Nice Jan! Maybe I'll be an RM one day, now that there's a nice tool to help :-) ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Thu, Jul 4, 2019 at 2:53 PM Jan Høydahl wrote: > I wrote an article at LinkedIN pulse about the release process and the > tool: > https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > 11. jun. 2019 kl. 10:46 skrev Jan Høydahl : > > I have now pushed the ReleaseWizard tool in > https://issues.apache.org/jira/browse/LUCENE-8852 > Appreciate all kind of feedback! > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > 1. jun. 2019 kl. 20:26 skrev Jan Høydahl : > > As I said, I’ll start a thread about this, please reply to that instead of > continuing discussion in this thread which is about releaseWizard :) > > Jan Høydahl > > 1. jun. 2019 kl. 15:53 skrev Michael Sokolov : > > I'm not sure what the proper way to use fix version is. Suppose you back > port a fix to multiple branches? Should fixVersion list all of them? Just > pick one? > > On Wed, May 29, 2019, 6:00 PM Jan Høydahl wrote: > >> My releaseWizard tool is getting more complete as the 7.7.2 release >> progresses. Will share the code just after I complete all steps. >> >> I tested relasedocmaker and it digs up all the JIRA issues marked as >> RESOLVED for the version and creates two files. >> CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG >> FIXES etc >> One problem I found with how the CHANGELOG works is that it adds all >> issues having the version in fixVersion, even if the feature >> was already released in an earlier version. That is because of the way we >> use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" >> at the same time, even if we know that 8.2 is the version the feature >> will be released. If we stop always adding "master" to fixVersion >> but strive to keep it a list of version the feature/bugfix is FIRST >> introduced, then this tool will do the correct job. >> >> RELEASENOTES.md lists "...new developer and user-facing >> incompatibilities, important issues, features, and major improvements.". >> And if we enable the JIRA field "Release Notes" (we don't have it now), >> the content of that field will be used in the release notes instead of the >> JIRA description. >> You can select any issue to surface in RELEASENOTES by adding a certain >> label, by default "backward-incompatible". >> >> I think it could be a welcome addition to our flow. We cant' expect the >> output from the tool to be used as-is, sometimes a major feature spans >> multiple >> JIRAs etc, but it could be a good starting point, and would shift the >> burden of documenting important and breaking changes from release-time to >> commit-time, >> if we as committers manage to adjust our routines. We could even have a >> weekly job that runs the releasedocmaker and sends the output to dev@ >> list for active branches, to keep focus. >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> 17. mai 2019 kl. 13:45 skrev Jan Høydahl : >> >> Yes, I thought we could use >> https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ to >> generate the draft, and this could be wired into the releaseWizard tool. >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> 17. mai 2019 kl. 06:40 skrev Ishan Chattopadhyaya < >> ichattopadhy...@gmail.com>: >> >> Much needed. Thanks for working on it. >> >> Here's an idea I was thinking about yesterday: the most tedious step is >> to generate release highlights. We should have a JIRA field "release >> highlight" which, when populated, will have the text that will be featured >> in the announce mail and on the website in news. That way, generating those >> mails can be semi/fully automated. >> >> Alternatively, this field can just be a Boolean check box and title of >> the Jira can be used as highlight. This will force the committer to keep >> meaningful titles. >> >> On Thu, 16 May, 2019, 10:58 PM Jan Høydahl, >> wrote: >> >>> Just a heads-up that as part of my releasing 7.7.2 effort I'm also >>> hacking on >>> a releaseWizard script to replace the ReleaseTodo wiki page. It will act >>> as a >>> checkl
Re: ReleaseWizard tool
I wrote an article at LinkedIN pulse about the release process and the tool: https://www.linkedin.com/pulse/releasing-lucene-just-61-steps-jan-høydahl/ -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 11. jun. 2019 kl. 10:46 skrev Jan Høydahl : > > I have now pushed the ReleaseWizard tool in > https://issues.apache.org/jira/browse/LUCENE-8852 > <https://issues.apache.org/jira/browse/LUCENE-8852> > Appreciate all kind of feedback! > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com <http://www.cominvent.com/> > >> 1. jun. 2019 kl. 20:26 skrev Jan Høydahl > <mailto:jan@cominvent.com>>: >> >> As I said, I’ll start a thread about this, please reply to that instead of >> continuing discussion in this thread which is about releaseWizard :) >> >> Jan Høydahl >> >> 1. jun. 2019 kl. 15:53 skrev Michael Sokolov > <mailto:msoko...@gmail.com>>: >> >>> I'm not sure what the proper way to use fix version is. Suppose you back >>> port a fix to multiple branches? Should fixVersion list all of them? Just >>> pick one? >>> >>> On Wed, May 29, 2019, 6:00 PM Jan Høydahl >> <mailto:jan@cominvent.com>> wrote: >>> My releaseWizard tool is getting more complete as the 7.7.2 release >>> progresses. Will share the code just after I complete all steps. >>> >>> I tested relasedocmaker and it digs up all the JIRA issues marked as >>> RESOLVED for the version and creates two files. >>> CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG FIXES >>> etc >>> One problem I found with how the CHANGELOG works is that it adds all issues >>> having the version in fixVersion, even if the feature >>> was already released in an earlier version. That is because of the way we >>> use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" >>> at the same time, even if we know that 8.2 is the version the feature will >>> be released. If we stop always adding "master" to fixVersion >>> but strive to keep it a list of version the feature/bugfix is FIRST >>> introduced, then this tool will do the correct job. >>> >>> RELEASENOTES.md lists "...new developer and user-facing incompatibilities, >>> important issues, features, and major improvements.". >>> And if we enable the JIRA field "Release Notes" (we don't have it now), the >>> content of that field will be used in the release notes instead of the JIRA >>> description. >>> You can select any issue to surface in RELEASENOTES by adding a certain >>> label, by default "backward-incompatible". >>> >>> I think it could be a welcome addition to our flow. We cant' expect the >>> output from the tool to be used as-is, sometimes a major feature spans >>> multiple >>> JIRAs etc, but it could be a good starting point, and would shift the >>> burden of documenting important and breaking changes from release-time to >>> commit-time, >>> if we as committers manage to adjust our routines. We could even have a >>> weekly job that runs the releasedocmaker and sends the output to dev@ list >>> for active branches, to keep focus. >>> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>> >>>> 17. mai 2019 kl. 13:45 skrev Jan Høydahl >>> <mailto:jan@cominvent.com>>: >>>> >>>> Yes, I thought we could use >>>> https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ >>>> <https://yetus.apache.org/documentation/0.10.0/releasedocmaker/> to >>>> generate the draft, and this could be wired into the releaseWizard tool. >>>> >>>> -- >>>> Jan Høydahl, search solution architect >>>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>>> >>>>> 17. mai 2019 kl. 06:40 skrev Ishan Chattopadhyaya >>>>> mailto:ichattopadhy...@gmail.com>>: >>>>> >>>>> Much needed. Thanks for working on it. >>>>> >>>>> Here's an idea I was thinking about yesterday: the most tedious step is >>>>> to generate release highlights. We should have a JIRA field "release >>>>> highlight" which, when populated, will have the text that will be >>>>>
[jira] [Commented] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878820#comment-16878820 ] ASF subversion and git services commented on LUCENE-8852: - Commit 07cb7cf5932e96a423a72e7b40ae55879e1db4cc in lucene-solr's branch refs/heads/branch_8x from Jan Høydahl [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=07cb7cf ] LUCENE-8852: Fix wording and git commit msg (cherry picked from commit 36af839eb110bcf9174dbd2f6de5f20a9705318e) > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Fix For: 8.2 > > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 20m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878819#comment-16878819 ] ASF subversion and git services commented on LUCENE-8852: - Commit 36af839eb110bcf9174dbd2f6de5f20a9705318e in lucene-solr's branch refs/heads/master from Jan Høydahl [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=36af839 ] LUCENE-8852: Fix wording and git commit msg > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Fix For: 8.2 > > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 20m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868529#comment-16868529 ] Jan Høydahl commented on LUCENE-8852: - Usage: https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Fix For: 8.2 > > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 20m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Resolved] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl resolved LUCENE-8852. - Resolution: Fixed Merged to master and branch_8x This is not product changes but dev script changes anyway, so better to get it out there in the hands of the devs for easier testing and feedback. > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Fix For: 8.2 > > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 20m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868498#comment-16868498 ] ASF subversion and git services commented on LUCENE-8852: - Commit 0d7a652974c1a9eee6bccd834862ff11048d71bf in lucene-solr's branch refs/heads/branch_8x from Jan Høydahl [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=0d7a652 ] LUCENE-8852 ReleaseWizard tool (#710) (cherry picked from commit 87c131baa739f591f2585ba1666b7d98768a5450) > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 20m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Fix Version/s: 8.2 > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Fix For: 8.2 > > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 20m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868495#comment-16868495 ] ASF subversion and git services commented on LUCENE-8852: - Commit 87c131baa739f591f2585ba1666b7d98768a5450 in lucene-solr's branch refs/heads/master from Jan Høydahl [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=87c131b ] LUCENE-8852 ReleaseWizard tool (#710) > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 20m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[GitHub] [lucene-solr] janhoy merged pull request #710: LUCENE-8852 ReleaseWizard tool
janhoy merged pull request #710: LUCENE-8852 ReleaseWizard tool URL: https://github.com/apache/lucene-solr/pull/710 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Description: The Release Wizard guides the Release Manager through the release process step by step, helping you to to run the right commands in the right order, generating e-mail templates with the correct texts, versions, paths etc, obeying the voting rules and much more. It also serves as a documentation of all the steps, with timestamps, preserving log files from each command etc, showing only the steps and commands required for a major/minor/bugfix release. It also lets you generate a full Asciidoc guide for the release. !ReleaseWizard.png|width=800! was: The Release Wizard guides the Release Manager through the release process step by step, helping you to to run the right commands in the right order, generating e-mail templates with the correct texts, versions, paths etc, obeying the voting rules and much more. It also serves as a documentation of all the steps, with timestamps, preserving log files from each command etc, showing only the steps and commands required for a major/minor/bugfix release. It also lets you generate a full Asciidoc guide for the release. !ReleaseWizard.png|width=600! > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=800! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Attachment: ReleaseWizard.png > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png, ReleaseWizard.png > > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=600! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (LUCENE-8852) ReleaseWizard tool
[
https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861114#comment-16861114
]
Jan Høydahl edited comment on LUCENE-8852 at 6/11/19 4:42 PM:
--
Commands to test the PR, from an existing lucene-solr git clone:
{code:java}
git checkout -b cominvent-releaseWizard master
git pull https://github.com/cominvent/lucene-solr.git releaseWizard
cd dev-tools/scripts
pip3 install -r requirements.txt
python3 releaseWizard.py
{code}
was (Author: janhoy):
Commands to test the PR, from an existing lucene-solr git clone:
{code:java}
git checkout -b cominvent-releaseWizard master
git pull https://github.com/cominvent/lucene-solr.git releaseWizard
cd dev-tools/scripts
pip3 install -r requirements.txt
python3 releaseWizard.py --dry-run{code}
> ReleaseWizard tool
> --
>
> Key: LUCENE-8852
> URL: https://issues.apache.org/jira/browse/LUCENE-8852
> Project: Lucene - Core
> Issue Type: New Feature
> Components: general/tools
> Environment: Python3
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Attachments: ReleaseWizard.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Release Wizard guides the Release Manager through the release process
> step by step, helping you to to run the right commands in the right order,
> generating e-mail templates with the correct texts, versions, paths etc,
> obeying the voting rules and much more. It also serves as a documentation of
> all the steps, with timestamps, preserving log files from each command etc,
> showing only the steps and commands required for a major/minor/bugfix
> release. It also lets you generate a full Asciidoc guide for the release.
> !ReleaseWizard.png|width=600!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-8852) ReleaseWizard tool
[
https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861114#comment-16861114
]
Jan Høydahl commented on LUCENE-8852:
-
Commands to test the PR, from an existing lucene-solr git clone:
{code:java}
git checkout -b cominvent-releaseWizard master
git pull https://github.com/cominvent/lucene-solr.git releaseWizard
cd dev-tools/scripts
pip3 install -r requirements.txt
python3 releaseWizard.py --dry-run{code}
> ReleaseWizard tool
> --
>
> Key: LUCENE-8852
> URL: https://issues.apache.org/jira/browse/LUCENE-8852
> Project: Lucene - Core
> Issue Type: New Feature
> Components: general/tools
> Environment: Python3
>Reporter: Jan Høydahl
>Assignee: Jan Høydahl
>Priority: Major
> Attachments: ReleaseWizard.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Release Wizard guides the Release Manager through the release process
> step by step, helping you to to run the right commands in the right order,
> generating e-mail templates with the correct texts, versions, paths etc,
> obeying the voting rules and much more. It also serves as a documentation of
> all the steps, with timestamps, preserving log files from each command etc,
> showing only the steps and commands required for a major/minor/bugfix
> release. It also lets you generate a full Asciidoc guide for the release.
> !ReleaseWizard.png|width=600!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Attachment: (was: image.png) > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png > > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=600! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Attachment: image.png > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png > > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=600! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Description: The Release Wizard guides the Release Manager through the release process step by step, helping you to to run the right commands in the right order, generating e-mail templates with the correct texts, versions, paths etc, obeying the voting rules and much more. It also serves as a documentation of all the steps, with timestamps, preserving log files from each command etc, showing only the steps and commands required for a major/minor/bugfix release. It also lets you generate a full Asciidoc guide for the release. !ReleaseWizard.png|width=600! was: The Release Wizard guides the Release Manager through the release process step by step, helping you to to run the right commands in the right order, generating e-mail templates with the correct texts, versions, paths etc, obeying the voting rules and much more. It also serves as a documentation of all the steps, with timestamps, preserving log files from each command etc, showing only the steps and commands required for a major/minor/bugfix release. It also lets you generate a full Asciidoc guide for the release. !ReleaseWizard.png|thumbnail! > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png > > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|width=600! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Description: The Release Wizard guides the Release Manager through the release process step by step, helping you to to run the right commands in the right order, generating e-mail templates with the correct texts, versions, paths etc, obeying the voting rules and much more. It also serves as a documentation of all the steps, with timestamps, preserving log files from each command etc, showing only the steps and commands required for a major/minor/bugfix release. It also lets you generate a full Asciidoc guide for the release. !ReleaseWizard.png|thumbnail! was: The Release Wizard guides the Release Manager through the release process step by step, helping you to to run the right commands in the right order, generating e-mail templates with the correct texts, versions, paths etc, obeying the voting rules and much more. It also serves as a documentation of all the steps, with timestamps, preserving log files from each command etc, showing only the steps and commands required for a major/minor/bugfix release. It also lets you generate a full Asciidoc guide for the release. > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png > > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step by step, helping you to to run the right commands in the right order, > generating e-mail templates with the correct texts, versions, paths etc, > obeying the voting rules and much more. It also serves as a documentation of > all the steps, with timestamps, preserving log files from each command etc, > showing only the steps and commands required for a major/minor/bugfix > release. It also lets you generate a full Asciidoc guide for the release. > !ReleaseWizard.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated LUCENE-8852: Attachment: ReleaseWizard.png > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Attachments: ReleaseWizard.png > > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step > by step, helping you to to run the right commands in the right order, > generating > e-mail templates with the correct texts, versions, paths etc, obeying > the voting rules and much more. It also serves as a documentation of all the > steps, with timestamps, preserving log files from each command etc, showing > only > the steps and commands required for a major/minor/bugfix release. It also lets > you generate a full Asciidoc guide for the release. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-8852) ReleaseWizard tool
[ https://issues.apache.org/jira/browse/LUCENE-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860685#comment-16860685 ] Jan Høydahl commented on LUCENE-8852: - It is perhaps a bit hard to test all of it without doing a release, but with the `--dry-run` option you will still get a good feel. At this stage I hope to attract attention from some of you recent RM's ([~ichattopadhyaya], [~ab], [~shalinmangar], [~jpountz]) who still remember the process, and flesh out whether the tool works with your dev setup, and of course to weed out any bugs wrt order of steps or what steps belong with major/minor/bugfix releases. Ultimately I hope that the next RM decides to give it a spin for the 8.2 or 8.1.2 release and take the time to harden the tool further through that process, and replace the old wiki page. > ReleaseWizard tool > -- > > Key: LUCENE-8852 > URL: https://issues.apache.org/jira/browse/LUCENE-8852 > Project: Lucene - Core > Issue Type: New Feature > Components: general/tools > Environment: Python3 >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The Release Wizard guides the Release Manager through the release process > step > by step, helping you to to run the right commands in the right order, > generating > e-mail templates with the correct texts, versions, paths etc, obeying > the voting rules and much more. It also serves as a documentation of all the > steps, with timestamps, preserving log files from each command etc, showing > only > the steps and commands required for a major/minor/bugfix release. It also lets > you generate a full Asciidoc guide for the release. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: ReleaseWizard tool
I have now pushed the ReleaseWizard tool in https://issues.apache.org/jira/browse/LUCENE-8852 Appreciate all kind of feedback! -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 1. jun. 2019 kl. 20:26 skrev Jan Høydahl : > > As I said, I’ll start a thread about this, please reply to that instead of > continuing discussion in this thread which is about releaseWizard :) > > Jan Høydahl > > 1. jun. 2019 kl. 15:53 skrev Michael Sokolov <mailto:msoko...@gmail.com>>: > >> I'm not sure what the proper way to use fix version is. Suppose you back >> port a fix to multiple branches? Should fixVersion list all of them? Just >> pick one? >> >> On Wed, May 29, 2019, 6:00 PM Jan Høydahl > <mailto:jan@cominvent.com>> wrote: >> My releaseWizard tool is getting more complete as the 7.7.2 release >> progresses. Will share the code just after I complete all steps. >> >> I tested relasedocmaker and it digs up all the JIRA issues marked as >> RESOLVED for the version and creates two files. >> CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG FIXES >> etc >> One problem I found with how the CHANGELOG works is that it adds all issues >> having the version in fixVersion, even if the feature >> was already released in an earlier version. That is because of the way we >> use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" >> at the same time, even if we know that 8.2 is the version the feature will >> be released. If we stop always adding "master" to fixVersion >> but strive to keep it a list of version the feature/bugfix is FIRST >> introduced, then this tool will do the correct job. >> >> RELEASENOTES.md lists "...new developer and user-facing incompatibilities, >> important issues, features, and major improvements.". >> And if we enable the JIRA field "Release Notes" (we don't have it now), the >> content of that field will be used in the release notes instead of the JIRA >> description. >> You can select any issue to surface in RELEASENOTES by adding a certain >> label, by default "backward-incompatible". >> >> I think it could be a welcome addition to our flow. We cant' expect the >> output from the tool to be used as-is, sometimes a major feature spans >> multiple >> JIRAs etc, but it could be a good starting point, and would shift the burden >> of documenting important and breaking changes from release-time to >> commit-time, >> if we as committers manage to adjust our routines. We could even have a >> weekly job that runs the releasedocmaker and sends the output to dev@ list >> for active branches, to keep focus. >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >> >>> 17. mai 2019 kl. 13:45 skrev Jan Høydahl >> <mailto:jan@cominvent.com>>: >>> >>> Yes, I thought we could use >>> https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ >>> <https://yetus.apache.org/documentation/0.10.0/releasedocmaker/> to >>> generate the draft, and this could be wired into the releaseWizard tool. >>> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >>> >>>> 17. mai 2019 kl. 06:40 skrev Ishan Chattopadhyaya >>>> mailto:ichattopadhy...@gmail.com>>: >>>> >>>> Much needed. Thanks for working on it. >>>> >>>> Here's an idea I was thinking about yesterday: the most tedious step is to >>>> generate release highlights. We should have a JIRA field "release >>>> highlight" which, when populated, will have the text that will be featured >>>> in the announce mail and on the website in news. That way, generating >>>> those mails can be semi/fully automated. >>>> >>>> Alternatively, this field can just be a Boolean check box and title of the >>>> Jira can be used as highlight. This will force the committer to keep >>>> meaningful titles. >>>> >>>> On Thu, 16 May, 2019, 10:58 PM Jan Høydahl, >>> <mailto:jan@cominvent.com>> wrote: >>>> Just a heads-up that as part of my releasing 7.7.2 effort I'm also hacking >>>> on >>>> a releaseWizard script to replace the ReleaseTodo wiki page. It will act &
[GitHub] [lucene-solr] janhoy opened a new pull request #710: LUCENE-8852 ReleaseWizard tool
janhoy opened a new pull request #710: LUCENE-8852 ReleaseWizard tool URL: https://github.com/apache/lucene-solr/pull/710 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (LUCENE-8852) ReleaseWizard tool
Jan Høydahl created LUCENE-8852: --- Summary: ReleaseWizard tool Key: LUCENE-8852 URL: https://issues.apache.org/jira/browse/LUCENE-8852 Project: Lucene - Core Issue Type: New Feature Components: general/tools Environment: Python3 Reporter: Jan Høydahl Assignee: Jan Høydahl The Release Wizard guides the Release Manager through the release process step by step, helping you to to run the right commands in the right order, generating e-mail templates with the correct texts, versions, paths etc, obeying the voting rules and much more. It also serves as a documentation of all the steps, with timestamps, preserving log files from each command etc, showing only the steps and commands required for a major/minor/bugfix release. It also lets you generate a full Asciidoc guide for the release. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: ReleaseWizard tool
As I said, I’ll start a thread about this, please reply to that instead of continuing discussion in this thread which is about releaseWizard :) Jan Høydahl > 1. jun. 2019 kl. 15:53 skrev Michael Sokolov : > > I'm not sure what the proper way to use fix version is. Suppose you back port > a fix to multiple branches? Should fixVersion list all of them? Just pick one? > >> On Wed, May 29, 2019, 6:00 PM Jan Høydahl wrote: >> My releaseWizard tool is getting more complete as the 7.7.2 release >> progresses. Will share the code just after I complete all steps. >> >> I tested relasedocmaker and it digs up all the JIRA issues marked as >> RESOLVED for the version and creates two files. >> CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG FIXES >> etc >> One problem I found with how the CHANGELOG works is that it adds all issues >> having the version in fixVersion, even if the feature >> was already released in an earlier version. That is because of the way we >> use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" >> at the same time, even if we know that 8.2 is the version the feature will >> be released. If we stop always adding "master" to fixVersion >> but strive to keep it a list of version the feature/bugfix is FIRST >> introduced, then this tool will do the correct job. >> >> RELEASENOTES.md lists "...new developer and user-facing incompatibilities, >> important issues, features, and major improvements.". >> And if we enable the JIRA field "Release Notes" (we don't have it now), the >> content of that field will be used in the release notes instead of the JIRA >> description. >> You can select any issue to surface in RELEASENOTES by adding a certain >> label, by default "backward-incompatible". >> >> I think it could be a welcome addition to our flow. We cant' expect the >> output from the tool to be used as-is, sometimes a major feature spans >> multiple >> JIRAs etc, but it could be a good starting point, and would shift the burden >> of documenting important and breaking changes from release-time to >> commit-time, >> if we as committers manage to adjust our routines. We could even have a >> weekly job that runs the releasedocmaker and sends the output to dev@ list >> for active branches, to keep focus. >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >>> 17. mai 2019 kl. 13:45 skrev Jan Høydahl : >>> >>> Yes, I thought we could use >>> https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ to generate >>> the draft, and this could be wired into the releaseWizard tool. >>> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com >>> >>>> 17. mai 2019 kl. 06:40 skrev Ishan Chattopadhyaya >>>> : >>>> >>>> Much needed. Thanks for working on it. >>>> >>>> Here's an idea I was thinking about yesterday: the most tedious step is to >>>> generate release highlights. We should have a JIRA field "release >>>> highlight" which, when populated, will have the text that will be featured >>>> in the announce mail and on the website in news. That way, generating >>>> those mails can be semi/fully automated. >>>> >>>> Alternatively, this field can just be a Boolean check box and title of the >>>> Jira can be used as highlight. This will force the committer to keep >>>> meaningful titles. >>>> >>>>> On Thu, 16 May, 2019, 10:58 PM Jan Høydahl, wrote: >>>>> Just a heads-up that as part of my releasing 7.7.2 effort I'm also >>>>> hacking on >>>>> a releaseWizard script to replace the ReleaseTodo wiki page. It will act >>>>> as a >>>>> checklist where you see tasks that needs to be done (different for >>>>> major/minor/bug) >>>>> and mark those completed. It will also run all the commands for you and >>>>> preserve >>>>> the logs, generate e-mail templates with all versions, dates etc in >>>>> place, handle >>>>> voting rules and counting etc. It will also generate an asciidoc + HTML >>>>> page that >>>>> gives a nice overview of the whole thing :) >>>>> >>>>> Here's a teaser: >>>>> >>>>> https://asciinema.org/a/246656
Re: ReleaseWizard tool
I'm not sure what the proper way to use fix version is. Suppose you back port a fix to multiple branches? Should fixVersion list all of them? Just pick one? On Wed, May 29, 2019, 6:00 PM Jan Høydahl wrote: > My releaseWizard tool is getting more complete as the 7.7.2 release > progresses. Will share the code just after I complete all steps. > > I tested relasedocmaker and it digs up all the JIRA issues marked as > RESOLVED for the version and creates two files. > CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG > FIXES etc > One problem I found with how the CHANGELOG works is that it adds all > issues having the version in fixVersion, even if the feature > was already released in an earlier version. That is because of the way we > use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" > at the same time, even if we know that 8.2 is the version the feature will > be released. If we stop always adding "master" to fixVersion > but strive to keep it a list of version the feature/bugfix is FIRST > introduced, then this tool will do the correct job. > > RELEASENOTES.md lists "...new developer and user-facing incompatibilities, > important issues, features, and major improvements.". > And if we enable the JIRA field "Release Notes" (we don't have it now), > the content of that field will be used in the release notes instead of the > JIRA description. > You can select any issue to surface in RELEASENOTES by adding a certain > label, by default "backward-incompatible". > > I think it could be a welcome addition to our flow. We cant' expect the > output from the tool to be used as-is, sometimes a major feature spans > multiple > JIRAs etc, but it could be a good starting point, and would shift the > burden of documenting important and breaking changes from release-time to > commit-time, > if we as committers manage to adjust our routines. We could even have a > weekly job that runs the releasedocmaker and sends the output to dev@ > list for active branches, to keep focus. > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > 17. mai 2019 kl. 13:45 skrev Jan Høydahl : > > Yes, I thought we could use > https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ to > generate the draft, and this could be wired into the releaseWizard tool. > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > 17. mai 2019 kl. 06:40 skrev Ishan Chattopadhyaya < > ichattopadhy...@gmail.com>: > > Much needed. Thanks for working on it. > > Here's an idea I was thinking about yesterday: the most tedious step is to > generate release highlights. We should have a JIRA field "release > highlight" which, when populated, will have the text that will be featured > in the announce mail and on the website in news. That way, generating those > mails can be semi/fully automated. > > Alternatively, this field can just be a Boolean check box and title of the > Jira can be used as highlight. This will force the committer to keep > meaningful titles. > > On Thu, 16 May, 2019, 10:58 PM Jan Høydahl, wrote: > >> Just a heads-up that as part of my releasing 7.7.2 effort I'm also >> hacking on >> a releaseWizard script to replace the ReleaseTodo wiki page. It will act >> as a >> checklist where you see tasks that needs to be done (different for >> major/minor/bug) >> and mark those completed. It will also run all the commands for you and >> preserve >> the logs, generate e-mail templates with all versions, dates etc in >> place, handle >> voting rules and counting etc. It will also generate an asciidoc + HTML >> page that >> gives a nice overview of the whole thing :) >> >> Here's a teaser: >> >> https://asciinema.org/a/246656 >> >> >> ┌─┐ >> │ >> │ >> │ Releasing Lucene/Solr 7.7.2 RC1 >> │ >> │ >> │ >> │ Please complete the below checklist (Complete: 4/11) >> │ >> │ >> │ >> │ >> │ >> │1 - ✓ Prerequisites (3/3) >> │ >> │2 - ✓ Work with the community to decide when and how etc (1/1) >> │ >> │3 - ✓ Create branch (if needed) and update versions (4/4) >> │ >> │4 - ✓ Add new versions to JIRA (2/2) >> │ >> │5 - Build the release artifacts (2/3) >> │ >> │6 - Hold the vote and sum up the results (0/2) >> │ >> │7 - Publish the release artifacts (0/1) >> │ >> │8 - Update the website (0/1) >> │ >> │9 - Update the DOAP file (0/1) >> │ >> │ 10 - Announce the release (0/1) >> │ >> │ 11 - Tasks to do after release (0/1) >> │ >> │ 12 - Exit >> │ >> │ >> │ >> │ >> │ >> >> └─┘ >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> > >
Re: ReleaseWizard tool
Thanks for input. I’ll start a separate email thread for discussing how we use JIRA including fixVersion :) Jan Høydahl > 30. mai 2019 kl. 01:43 skrev Chris Hostetter : > > > : I tested relasedocmaker and it digs up all the JIRA issues marked as > RESOLVED for the version and creates two files. > : CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG FIXES > etc > : One problem I found with how the CHANGELOG works is that it adds all issues > having the version in fixVersion, even if the feature > : was already released in an earlier version. That is because of the way we > use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" > : at the same time, even if we know that 8.2 is the version the feature will > be released. If we stop always adding "master" to fixVersion > : but strive to keep it a list of version the feature/bugfix is FIRST > introduced, then this tool will do the correct job. > > The reason we (should always) track every fixVersion based on where things > are commited & backported is because of how important it is from the stand > point of knowing when exactly something was fixed, compared to where it > might have *needed* to be fixed. > > A bug might be found just before the 8.1.0 release that affect 7.7.0, > 8.0.0, and the current branch_8x but not master because the underlying > functionality was deprecated in 8x & removed from master -- the fix would > be committed to branch_8x and backported to branch_8_0 and branch_7_7 for > inclusion in 7.7.1 -- but maybe no one has bothered with w/an 8.0.1, and > meanwhile branch_8_1 is forked from branch_8x and already has the fix. > > if we *only* record fixVersion=7.7.1, then that can misslead people who > don't know the timing/history of the jira into thinking that if it was > fixed in 7.7.y then maybe/probably/who-knows-if it is issue in 8.x.y. > Having fixVersion=7.7.1,8.0.1,8.1.0 helps communicate several things... > > * if you are using 7.y.x lower then 7.7.1 you might be affected by this > * if you are using 8.0.y lower then 8.0.1 you might be affected by this > - since you can see in jira that 8.0.1 is unreleased: >- if/when 8.0.1 is released, it will include this fix > * if you are using 8.x.y lower then 8.1.0 then you might be affected by this > > If we *only* use fixVersion="lowest version released" it wouldn't help > people answer the question "Does this bug exist in 8.w.v if all i know is > that > the _first_ version it was fixed in was 7.x.y?" > > ...not to mention the complexity involved in _older_ bug fixe releases > happening *after* more recent feature releases with the same fix (ie: > 7.7.1 being released after 8.1.0. > > (a more rigorous use of the "affectsVersion", eg: > affectsVersion="7.7.0,7.7.1,...,7.7.0,8.0.0", can help mitigate *some* > of this confusion -- by implying that the issue does *not* affect 8.1.0 > since it isn't listed there -- but that's a lot more tedious to maintain > then just ensuring that you add a fixVersion for every place you commit) > > > -Hoss > http://www.lucidworks.com/ > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: ReleaseWizard tool
: I tested relasedocmaker and it digs up all the JIRA issues marked as RESOLVED for the version and creates two files. : CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG FIXES etc : One problem I found with how the CHANGELOG works is that it adds all issues having the version in fixVersion, even if the feature : was already released in an earlier version. That is because of the way we use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" : at the same time, even if we know that 8.2 is the version the feature will be released. If we stop always adding "master" to fixVersion : but strive to keep it a list of version the feature/bugfix is FIRST introduced, then this tool will do the correct job. The reason we (should always) track every fixVersion based on where things are commited & backported is because of how important it is from the stand point of knowing when exactly something was fixed, compared to where it might have *needed* to be fixed. A bug might be found just before the 8.1.0 release that affect 7.7.0, 8.0.0, and the current branch_8x but not master because the underlying functionality was deprecated in 8x & removed from master -- the fix would be committed to branch_8x and backported to branch_8_0 and branch_7_7 for inclusion in 7.7.1 -- but maybe no one has bothered with w/an 8.0.1, and meanwhile branch_8_1 is forked from branch_8x and already has the fix. if we *only* record fixVersion=7.7.1, then that can misslead people who don't know the timing/history of the jira into thinking that if it was fixed in 7.7.y then maybe/probably/who-knows-if it is issue in 8.x.y. Having fixVersion=7.7.1,8.0.1,8.1.0 helps communicate several things... * if you are using 7.y.x lower then 7.7.1 you might be affected by this * if you are using 8.0.y lower then 8.0.1 you might be affected by this - since you can see in jira that 8.0.1 is unreleased: - if/when 8.0.1 is released, it will include this fix * if you are using 8.x.y lower then 8.1.0 then you might be affected by this If we *only* use fixVersion="lowest version released" it wouldn't help people answer the question "Does this bug exist in 8.w.v if all i know is that the _first_ version it was fixed in was 7.x.y?" ...not to mention the complexity involved in _older_ bug fixe releases happening *after* more recent feature releases with the same fix (ie: 7.7.1 being released after 8.1.0. (a more rigorous use of the "affectsVersion", eg: affectsVersion="7.7.0,7.7.1,...,7.7.0,8.0.0", can help mitigate *some* of this confusion -- by implying that the issue does *not* affect 8.1.0 since it isn't listed there -- but that's a lot more tedious to maintain then just ensuring that you add a fixVersion for every place you commit) -Hoss http://www.lucidworks.com/ - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: ReleaseWizard tool
My releaseWizard tool is getting more complete as the 7.7.2 release progresses. Will share the code just after I complete all steps. I tested relasedocmaker and it digs up all the JIRA issues marked as RESOLVED for the version and creates two files. CHANGELOG.md simply lists all issues under headings IMPROVEMENTS, BUG FIXES etc One problem I found with how the CHANGELOG works is that it adds all issues having the version in fixVersion, even if the feature was already released in an earlier version. That is because of the way we use JIRA fixVersion, adding both e.g. "master (9.0)" and "8.2" at the same time, even if we know that 8.2 is the version the feature will be released. If we stop always adding "master" to fixVersion but strive to keep it a list of version the feature/bugfix is FIRST introduced, then this tool will do the correct job. RELEASENOTES.md lists "...new developer and user-facing incompatibilities, important issues, features, and major improvements.". And if we enable the JIRA field "Release Notes" (we don't have it now), the content of that field will be used in the release notes instead of the JIRA description. You can select any issue to surface in RELEASENOTES by adding a certain label, by default "backward-incompatible". I think it could be a welcome addition to our flow. We cant' expect the output from the tool to be used as-is, sometimes a major feature spans multiple JIRAs etc, but it could be a good starting point, and would shift the burden of documenting important and breaking changes from release-time to commit-time, if we as committers manage to adjust our routines. We could even have a weekly job that runs the releasedocmaker and sends the output to dev@ list for active branches, to keep focus. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 17. mai 2019 kl. 13:45 skrev Jan Høydahl : > > Yes, I thought we could use > https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ > <https://yetus.apache.org/documentation/0.10.0/releasedocmaker/> to generate > the draft, and this could be wired into the releaseWizard tool. > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com <http://www.cominvent.com/> > >> 17. mai 2019 kl. 06:40 skrev Ishan Chattopadhyaya > <mailto:ichattopadhy...@gmail.com>>: >> >> Much needed. Thanks for working on it. >> >> Here's an idea I was thinking about yesterday: the most tedious step is to >> generate release highlights. We should have a JIRA field "release highlight" >> which, when populated, will have the text that will be featured in the >> announce mail and on the website in news. That way, generating those mails >> can be semi/fully automated. >> >> Alternatively, this field can just be a Boolean check box and title of the >> Jira can be used as highlight. This will force the committer to keep >> meaningful titles. >> >> On Thu, 16 May, 2019, 10:58 PM Jan Høydahl, > <mailto:jan@cominvent.com>> wrote: >> Just a heads-up that as part of my releasing 7.7.2 effort I'm also hacking on >> a releaseWizard script to replace the ReleaseTodo wiki page. It will act as a >> checklist where you see tasks that needs to be done (different for >> major/minor/bug) >> and mark those completed. It will also run all the commands for you and >> preserve >> the logs, generate e-mail templates with all versions, dates etc in place, >> handle >> voting rules and counting etc. It will also generate an asciidoc + HTML page >> that >> gives a nice overview of the whole thing :) >> >> Here's a teaser: >> >> https://asciinema.org/a/246656 <https://asciinema.org/a/246656> >> >> ┌─┐ >> │ │ >> │ Releasing Lucene/Solr 7.7.2 RC1│ >> │ │ >> │ Please complete the below checklist (Complete: 4/11) │ >> │ │ >> │ │ >> │1 - ✓ Prerequisites (3/3)│ >> │2 - ✓ Work with the community to decide when and how etc (1/1) │ >> │3 - ✓ Create branch (if needed) and update versions (4/4)│ >> │4 - ✓ Add new versions to JIRA (2/2) │ >> │5 - Build the
Re: ReleaseWizard tool
Yes, I thought we could use https://yetus.apache.org/documentation/0.10.0/releasedocmaker/ to generate the draft, and this could be wired into the releaseWizard tool. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 17. mai 2019 kl. 06:40 skrev Ishan Chattopadhyaya : > > Much needed. Thanks for working on it. > > Here's an idea I was thinking about yesterday: the most tedious step is to > generate release highlights. We should have a JIRA field "release highlight" > which, when populated, will have the text that will be featured in the > announce mail and on the website in news. That way, generating those mails > can be semi/fully automated. > > Alternatively, this field can just be a Boolean check box and title of the > Jira can be used as highlight. This will force the committer to keep > meaningful titles. > > On Thu, 16 May, 2019, 10:58 PM Jan Høydahl, <mailto:jan@cominvent.com>> wrote: > Just a heads-up that as part of my releasing 7.7.2 effort I'm also hacking on > a releaseWizard script to replace the ReleaseTodo wiki page. It will act as a > checklist where you see tasks that needs to be done (different for > major/minor/bug) > and mark those completed. It will also run all the commands for you and > preserve > the logs, generate e-mail templates with all versions, dates etc in place, > handle > voting rules and counting etc. It will also generate an asciidoc + HTML page > that > gives a nice overview of the whole thing :) > > Here's a teaser: > > https://asciinema.org/a/246656 <https://asciinema.org/a/246656> > > ┌─┐ > │ │ > │ Releasing Lucene/Solr 7.7.2 RC1│ > │ │ > │ Please complete the below checklist (Complete: 4/11) │ > │ │ > │ │ > │1 - ✓ Prerequisites (3/3)│ > │2 - ✓ Work with the community to decide when and how etc (1/1) │ > │3 - ✓ Create branch (if needed) and update versions (4/4)│ > │4 - ✓ Add new versions to JIRA (2/2) │ > │5 - Build the release artifacts (2/3)│ > │6 - Hold the vote and sum up the results (0/2) │ > │7 - Publish the release artifacts (0/1) │ > │8 - Update the website (0/1) │ > │9 - Update the DOAP file (0/1) │ > │ 10 - Announce the release (0/1) │ > │ 11 - Tasks to do after release (0/1) │ > │ 12 - Exit │ > │ │ > │ │ > └─┘ > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com <http://www.cominvent.com/> >
Re: ReleaseWizard tool
Much needed. Thanks for working on it. Here's an idea I was thinking about yesterday: the most tedious step is to generate release highlights. We should have a JIRA field "release highlight" which, when populated, will have the text that will be featured in the announce mail and on the website in news. That way, generating those mails can be semi/fully automated. Alternatively, this field can just be a Boolean check box and title of the Jira can be used as highlight. This will force the committer to keep meaningful titles. On Thu, 16 May, 2019, 10:58 PM Jan Høydahl, wrote: > Just a heads-up that as part of my releasing 7.7.2 effort I'm also hacking > on > a releaseWizard script to replace the ReleaseTodo wiki page. It will act > as a > checklist where you see tasks that needs to be done (different for > major/minor/bug) > and mark those completed. It will also run all the commands for you and > preserve > the logs, generate e-mail templates with all versions, dates etc in place, > handle > voting rules and counting etc. It will also generate an asciidoc + HTML > page that > gives a nice overview of the whole thing :) > > Here's a teaser: > > https://asciinema.org/a/246656 > > > ┌─┐ > │ > │ > │ Releasing Lucene/Solr 7.7.2 RC1 > │ > │ > │ > │ Please complete the below checklist (Complete: 4/11) > │ > │ > │ > │ > │ > │1 - ✓ Prerequisites (3/3) > │ > │2 - ✓ Work with the community to decide when and how etc (1/1) > │ > │3 - ✓ Create branch (if needed) and update versions (4/4) > │ > │4 - ✓ Add new versions to JIRA (2/2) > │ > │5 - Build the release artifacts (2/3) > │ > │6 - Hold the vote and sum up the results (0/2) > │ > │7 - Publish the release artifacts (0/1) > │ > │8 - Update the website (0/1) > │ > │9 - Update the DOAP file (0/1) > │ > │ 10 - Announce the release (0/1) > │ > │ 11 - Tasks to do after release (0/1) > │ > │ 12 - Exit > │ > │ > │ > │ > │ > > └─┘ > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > >
ReleaseWizard tool
Just a heads-up that as part of my releasing 7.7.2 effort I'm also hacking on a releaseWizard script to replace the ReleaseTodo wiki page. It will act as a checklist where you see tasks that needs to be done (different for major/minor/bug) and mark those completed. It will also run all the commands for you and preserve the logs, generate e-mail templates with all versions, dates etc in place, handle voting rules and counting etc. It will also generate an asciidoc + HTML page that gives a nice overview of the whole thing :) Here's a teaser: https://asciinema.org/a/246656 ┌─┐ │ │ │ Releasing Lucene/Solr 7.7.2 RC1│ │ │ │ Please complete the below checklist (Complete: 4/11) │ │ │ │ │ │1 - ✓ Prerequisites (3/3)│ │2 - ✓ Work with the community to decide when and how etc (1/1) │ │3 - ✓ Create branch (if needed) and update versions (4/4)│ │4 - ✓ Add new versions to JIRA (2/2) │ │5 - Build the release artifacts (2/3)│ │6 - Hold the vote and sum up the results (0/2) │ │7 - Publish the release artifacts (0/1) │ │8 - Update the website (0/1) │ │9 - Update the DOAP file (0/1) │ │ 10 - Announce the release (0/1) │ │ 11 - Tasks to do after release (0/1) │ │ 12 - Exit │ │ │ │ │ └─┘ -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com
