I've never understood this. Why? I realize we don't want to keep release 6.x forever, but what is it about a week in this case that's so horrible? We're not talking about introducing back-compat issues here.
On Thu, Aug 10, 2017 at 2:43 AM, Adrien Grand <[email protected]> wrote: > Releasing 6.7 means we cannot start the 7.0 release process until 6.7 is > out. Do we really want to delay 7.0 even more? I won't object to releasing > 6.7 but if we want to do it let's get a vote started today. > > Le mer. 9 août 2017 à 22:31, Jan Høydahl <[email protected]> a écrit : >> >> +1 >> >> >> Den 9. aug. 2017 kl. 20.18 skrev David Smiley <[email protected]>: >> >> +1 >> I think a 6.7 release would be very good. >> >> On Tue, Aug 8, 2017 at 5:46 PM Mike Drob <[email protected]> wrote: >>> >>> +1 >>> >>> Release early, release often! >>> >>> On Tue, Aug 8, 2017 at 4:27 PM, Erick Erickson <[email protected]> >>> wrote: >>>> >>>> Solr and Lucene have had fixes backported to 6x (not 6.6) since the >>>> 7.0 label was set, most in Solr. Some of the fixes are useful "in the >>>> field", I've back-ported some of them myself. >>>> >>>> What objections are there to a 6.7 release? We'd always prefer to >>>> release nothing except important bug fixes on a prior branch, but the >>>> release process for 7.0 has taken some time and changes have >>>> accumulated. >>>> >>>> This might be the last, best time to wrap up 6x with a 6.7 as much as >>>> we can before officially releasing 7.0. >>>> >>>> What do people think? >>>> >>>> Erick >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >> -- >> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker >> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: >> http://www.solrenterprisesearchserver.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
