Thanks! I'll cut the release branch today, shall use the wizard to begin with.
On Sat, 24 Sep, 2022, 5:56 am Houston Putman, <[email protected]> wrote: > Thanks for volunteering for the release Ishan! > > Make sure to use the release wizard the whole way through. Starting with > the 9.0 release there are lots of added steps, but luckily they are > automated via the wizard! > > - Houston > > On Mon, Sep 19, 2022 at 10:17 AM Houston Putman <[email protected]> > wrote: > > > I think it's probably safe to release with 9.3, since thats been in for a > > while now. Unless there are some big improvements/fixes you think make it > > worth-while? > > > > Generally I think upgrading to any minor/patch version within the same > > major version is safe for now. Having Solr/Lucene have different major > > versions is a different conversation entirely, but luckily one we > shouldn't > > need to have for some time... > > > > - Houston > > > > On Mon, Sep 19, 2022 at 9:54 AM Alessandro Benedetti < > [email protected]> > > wrote: > > > >> Thanks for voluntering! > >> So I noticed we are on Lucene 9.3 now (and 9.4 should be released soon). > >> > >> A couple of questions: > >> > >> 1) should we wait for Lucene 9.4 release, include the new library > >> dependency and then cut the branch? > >> > >> 2) in the past I noticed not necessarily a continuously incremental > >> release > >> version (recently but also in the past there are various gaps): > >> > >> [image: [DIR]] 7.4.0/ > >> <https://archive.apache.org/dist/lucene/solr/7.4.0/> > >> 2018-06-22 08:04 - [image: [DIR]] 7.5.0/ > >> <https://archive.apache.org/dist/lucene/solr/7.5.0/> > >> 2018-09-22 16:26 - [image: [DIR]] 7.6.0/ > >> <https://archive.apache.org/dist/lucene/solr/7.6.0/> > >> 2018-12-13 23:04 - [image: [DIR]] 7.7.0/ > >> <https://archive.apache.org/dist/lucene/solr/7.7.0/> > >> 2019-02-08 15:09 - [image: [DIR]] 7.7.1/ > >> <https://archive.apache.org/dist/lucene/solr/7.7.1/> > >> 2019-02-27 11:55 - [image: [DIR]] 7.7.2/ > >> <https://archive.apache.org/dist/lucene/solr/7.7.2/> > >> 2019-06-04 09:39 - [image: [DIR]] 7.7.3/ > >> <https://archive.apache.org/dist/lucene/solr/7.7.3/> > >> 2020-07-03 03:48 - [image: [DIR]] 8.0.0/ > >> <https://archive.apache.org/dist/lucene/solr/8.0.0/> ... > >> > >> So my question, should the next release be Solr 9.1 (that includes > >> Lucene 9.X) or Solr 9.X(that includes Lucene 9.X). > >> > >> I know that are separate projects right now, I am just wondering if > >> being aligned in version could still be a benefit to ease both users > >> and developers/integrators approaches. > >> > >> > >> Cheers > >> > >> -------------------------- > >> *Alessandro Benedetti* > >> Director @ Sease Ltd. > >> *Apache Lucene/Solr Committer* > >> *Apache Solr PMC Member* > >> > >> e-mail: [email protected] > >> > >> > >> *Sease* - Information Retrieval Applied > >> Consulting | Training | Open Source > >> > >> Website: Sease.io <http://sease.io/> > >> LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter > >> <https://twitter.com/seaseltd> | Youtube > >> <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github > >> <https://github.com/seaseltd> > >> > >> > >> On Thu, 15 Sept 2022 at 22:06, Jan Høydahl <[email protected]> > wrote: > >> > >> > +1 and thanks for volunteering! > >> > > >> > > 15. sep. 2022 kl. 18:55 skrev Ishan Chattopadhyaya < > >> > [email protected]>: > >> > > > >> > > Hi devs, > >> > > > >> > > It has been long since 9.0 release and we have quite a few changes > >> > already > >> > > in the 9x branch. I'd like to volunteer for a 9.1 release, if there > >> are > >> > no > >> > > objections. I'm planning to cut the release branch in a week from > now, > >> > and > >> > > build the RC in another week from then. > >> > > > >> > > Please let me know if there are any concerns or outstanding issues > >> (due > >> > to > >> > > which we should delay this). > >> > > > >> > > Thanks, > >> > > Ishan > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [email protected] > >> > For additional commands, e-mail: [email protected] > >> > > >> > > >> > > >
