Thanks for all the detail. I do appreciate your time in replying. I'm
not fond of the idea of trying to cherry-pick trunk and delay further..
This has just been an odd and unorthodox moment in time to adopt release
management, and I simply wish to do what's best for users. It's late,
and I need to
Please don’t make me argue over 3.8/3.9 again. We are way, way over our
original schedule at this point.
Releasing 3.9 now breaks no promises. You still get more than a month of purely
bug fixes in the release.
And if we only do 3.8 off the current cassandra-3.9 branch, then trunk becomes
the
Jonathan's is a pretty compelling perspective.
--
Michael
On 09/23/2016 07:04 PM, Aleksey Yeschenko wrote:
> Both are effectively 3.9 on steroids. One month of features and
> improvements with 2 months of bug fixes on top.
>
> If anything, this overdelivers.
>
> -- AY
>
> On 23 September
Both are effectively 3.9 on steroids. One month of features and improvements
with 2 months of bug fixes on top.
If anything, this overdelivers.
--
AY
On 23 September 2016 at 17:02:05, Jonathan Haddad (j...@jonhaddad.com) wrote:
(non-binding) -1 on releasing 2 versions with the same version
(non-binding) -1 on releasing 2 versions with the same version number.
Everything that's been communicated to the world has been that there would
be a feature release, then a bug fix release a month later. This breaks
that promise.
On Fri, Sep 23, 2016 at 4:23 PM Michael Shuler
Thanks! I'll do these release builds and start votes, first thing Monday
morning, unless I find some time on Sunday.
--
Michael
On 09/23/2016 05:15 PM, Aleksey Yeschenko wrote:
> Branch 3.8 off 3.9 with a commit that only changes the version in all
> appropriate places.
>
> Two separate votes
Branch 3.8 off 3.9 with a commit that only changes the version in all
appropriate places.
Two separate votes works.
--
AY
On 23 September 2016 at 12:36:54, Michael Shuler (mich...@pbandjelly.org) wrote:
The cassandra-3.9 branch HEAD, commit bb371ea, looks good to release
(which will also
