Specifically, the version number for the release should probably be 2.2, since that's the 5.x version that's been released. Unless there are functional changes, we should do the same for 6.x?
So, solr-6.x/trunk should have a pom.xml version of: <version>2.2-SNAPSHOT</version> ... which I'll then upgrade when I create the release branch. Karl On Tue, May 10, 2016 at 9:14 AM, Karl Wright <[email protected]> wrote: > Ok, I'll try to make a release branch and pull together a release > candidate when I have a moment. > > Can I ask why the version is now 2.5 though? > > Thanks!! > Karl > > > On Tue, May 10, 2016 at 9:06 AM, Ahmet Arslan <[email protected]> > wrote: > >> Hi, >> >> I renamed the bak file, added a license header and made some trivial >> changes. >> Committed revision 1743169. >> >> I think it is ready to go now. >> >> Thanks, >> Ahmet >> >> >> >> On Tuesday, May 10, 2016 10:17 AM, Karl Wright <[email protected]> >> wrote: >> Do you think this is ready for release now? >> Karl >> >> >> >> On Tue, May 10, 2016 at 3:06 AM, Karl Wright <[email protected]> wrote: >> >> > Thank you!! >> > >> > Karl >> > >> > >> > On Tue, May 10, 2016 at 3:03 AM, Shinichiro Abe < >> > [email protected]> wrote: >> > >> >> Hi, >> >> >> >> I just fixed tests to pass now, r1743105. >> >> >> >> Regards, >> >> Shinichiro Abe >> >> >> >> > 2016/04/23 20:05、Karl Wright <[email protected]> のメール： >> >> > >> >> > We've got a new plugin now that Lucene/Solr 6.0 has been released. >> Does >> >> > anyone want to handle its first release? >> >> > >> >> > Karl >> >> >> >> >> > >> > >
