Houston, see my JIRA comment to perhaps automate all of this with Jenkins. Then the only manual task for the RM would be to create the Jenkins job after cutting a new release branch.
Jan > 16. nov. 2021 kl. 19:32 skrev Houston Putman <[email protected]>: > > Here is a preliminary PR to add this to the release wizard. > https://github.com/apache/solr/pull/419 > <https://github.com/apache/solr/pull/419> > > On Tue, Nov 16, 2021 at 10:12 AM Houston Putman <[email protected] > <mailto:[email protected]>> wrote: > Actually instead of modifying the htaccess files, I'll try to publish th 8_11 > ref guide. > > On Tue, Nov 16, 2021 at 10:11 AM Houston Putman <[email protected] > <mailto:[email protected]>> wrote: > Cassandra, > > I'd be happy to help get it into the release wizard. We definitely shouldn't > have any processes that rely on one person. > > In the meantime, I'll update the htaccess files to use guide/8_10 instead of > guide/8_11 until we can get that up and running. > > - Houston > > On Tue, Nov 16, 2021 at 8:02 AM Cassandra Targett <[email protected] > <mailto:[email protected]>> wrote: > I appreciate the offer, Ashutosh, but I don’t think you could have done it, > since it requires committer access. > > 8.11 is now out, and the Solr website .htaccess updated to redirect to the > 8.11 Ref Guide but there is no `guide/8_11` path there because I was on a > desperately needed vacation and didn’t monitor the list every day to know it > was time for me to get back to keyboard and run Ref Guide publishing tasks. > > We really need to make publishing the Ref Guide part of the release process > starting in 9.0. I’d have done it already but I don’t really understand the > overall release process, and don’t know where it fits or how it should, etc. > I’ve said several times that I need assistance here. I’ll file a blocker Jira > for 9.0 because if we agree that the Ref Guide is a key aspect of the > community and it should be published with the main artifact release (both of > which I thought we agreed on), it shouldn’t rely only on 1 person, and any of > us should be able to take 1 week away from the world without a list of > semi-urgent problems piling up for them unnecessarily. > > I’ll also see when/if I can fit in fixing the 8.10 Guide and pushing up 8.11. > > Cassandra > On Nov 10, 2021, 10:30 AM -0600, ashu <[email protected] > <mailto:[email protected]>>, wrote: >> Hi team, >> >> Plase let me do it. >> >> Regards, >> Ashutosh >> On Wed, 10 Nov 2021, 9:42 pm Cassandra Targett, <[email protected] >> <mailto:[email protected]>> wrote: >> I screwed it up somehow when I pushed the final pages. I’m traveling on >> vacation and won’t be able to fix it until sometime next week after I catch >> up with day job stuff (could easily be 2-3 weeks before I can get to it). >> Instructions on how to republish to fix it are in the actual ref guide if >> anyone else is so inclined: >> https:/solr.apache.org/guide/8_10/how-to-contribute.html#publish-the-final-guide >> >> <https://https/solr.apache.org/guide/8_10/how-to-contribute.html#publish-the-final-guide>. >> >> Cassandra >> On Nov 9, 2021, 4:29 PM -0600, Houston Putman <[email protected] >> <mailto:[email protected]>>, wrote: >>> I see it too. >>> >>> Old ref guides can be updated though, it happens every time a patch release >>> is made. >>> >>> On Tue, Nov 9, 2021 at 5:18 PM Mike Drob <[email protected] >>> <mailto:[email protected]>> wrote: >>> When looking at an 8_10 reference guide, many pages have the DRAFT >>> watermark on them - e.g. >>> https://solr.apache.org/guide/8_10/solr-upgrade-notes.html >>> <https://solr.apache.org/guide/8_10/solr-upgrade-notes.html> >>> >>> Is this my browser caching something or do other people see it too? If this >>> is on the server side, can we update these? We'll have to do this again soo >>> for 8.11 as well, but the old ref guides don't go away so it's still >>> valuable, I think. >>> >>> Mike
