: My only comment is that 5.5 coming just a few days after 5.4.x seems : pretty short, but maybe it'll take a month to get the first Git build : ironed out anyway...
Even if if everything goes smoothly and we discover that magically everything still works and we are "ready" to do a 5.5 release by monday -- that doesn't mean we have to. It just means we've demonstrated sooner rather then later that the release process is up to date and ready to work with git. Someone could, in theory, build a 5.5-RC1 with absolutely no changes compared to 5.4.1, and we could all just agree *not* to release it. (correct me if i'm wrong, but once the RC is up on the dist repo we've proven everything we need to prove about the release process as it pertains to git, correct?) : : As always, though, when I'm not doing the work so it's not my decision. : : On Thu, Jan 21, 2016 at 5:46 AM, [email protected] : <[email protected]> wrote: : > +1 fine idea Rob! : > : > On Thu, Jan 21, 2016 at 2:18 AM Robert Muir <[email protected]> wrote: : >> : >> one idea, we could use it to our advantage: as soon as we go to git, : >> immediately (e.g. after just a few days or whatever) start a 5.5 : >> release? : >> : >> besides keeping things less confusing, it could make the 6.0 release : >> more easygoing. because we'd have already worked through the pain of : >> release process and tooling changes with a technically "easier" : >> release otherwise. IMO basically a major release is hard enough on its : >> own, we might want to separate the two things... : >> : >> basically we'd suffer the one-time pain of "first git release" : >> immediately up-front, when svn->git is fresh in our minds. after that : >> first release its on the wiki and no big deal... : >> : >> guess there are downsides to this idea too, e.g. it'd be effort that : >> could be spent on 6.0, having to backport git build system changes to : >> 5.x, etc. : >> : >> On Wed, Jan 20, 2016 at 6:58 PM, Shawn Heisey <[email protected]> wrote: : >> > All indications I've seen are that there will be no 5.5 release, that : >> > once : >> > the git transition is complete, the focus will be on stabilizing the 6.0 : >> > release. Is this a correct statement? There are quite a lot of things : >> > mentioned in the 5.5 section of CHANGES.txt, plenty for a minor release. : >> > : >> > If we are abandoning work on branch_5x, I am OK with it, I'm just : >> > looking : >> > for information. : >> > : >> > Thanks, : >> > Shawn : >> > : >> > : >> > --------------------------------------------------------------------- : >> > To unsubscribe, e-mail: [email protected] : >> > For additional commands, e-mail: [email protected] : >> > : >> : >> --------------------------------------------------------------------- : >> 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] : : -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
