You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Michael Shuler <mi...@pbandjelly.org> on 2016/11/29 18:11:42 UTC
3.10 fixver, CHANGES.txt, and the cassandra-3.11 branch
Sam and I fixed up CHANGES.txt and fix versions in JIRA that had 3.11.
Since 3.10 has not been released yet,and the cassandra-3.11 branch was
created from the 3.10-tentative tag for fixed on top of 3.10, the
cassandra-3.11 branch will be used for the 3.10 release, as well as for
fixed bugs on top of 3.10 that will become 3.11. There should be no JIRA
tickets or CHANGES entries for 3.11, until such time that 3.10 is
actually released :)
Any new features / improvements targeted for 3.12 should be committed to
the cassandra-3.X branch. This should hopefully help the cassandra-3.11
branch settle down.
--
Kind regards,
Michael
Re: 3.10 fixver, CHANGES.txt, and the cassandra-3.11 branch
Posted by Michael Shuler <mi...@pbandjelly.org>.
Paulo pinged me on irc about getting CASSANDRA-12905 in for 3.10, so
that has been marked as release critical for 3.10 in JIRA.
--
Kind regards,
Michael
On 12/05/2016 01:26 PM, Michael Shuler wrote:
> I have again removed the 3.11 version from JIRA and corrected
> CHANGES.txt for 3.10.
>
> I'll run through the test results on the cassandra-3.11 branch and see
> where we are at for a possible 3.10 release vote #5. There appear to be
> no open 3.10 JIRA tickets at this time.
>
Re: 3.10 fixver, CHANGES.txt, and the cassandra-3.11 branch
Posted by Michael Shuler <mi...@pbandjelly.org>.
I have again removed the 3.11 version from JIRA and corrected
CHANGES.txt for 3.10.
I'll run through the test results on the cassandra-3.11 branch and see
where we are at for a possible 3.10 release vote #5. There appear to be
no open 3.10 JIRA tickets at this time.
--
Kind regards,
Michael
On 11/29/2016 12:11 PM, Michael Shuler wrote:
> Sam and I fixed up CHANGES.txt and fix versions in JIRA that had 3.11.
>
> Since 3.10 has not been released yet,and the cassandra-3.11 branch was
> created from the 3.10-tentative tag for fixed on top of 3.10, the
> cassandra-3.11 branch will be used for the 3.10 release, as well as for
> fixed bugs on top of 3.10 that will become 3.11. There should be no JIRA
> tickets or CHANGES entries for 3.11, until such time that 3.10 is
> actually released :)
>
> Any new features / improvements targeted for 3.12 should be committed to
> the cassandra-3.X branch. This should hopefully help the cassandra-3.11
> branch settle down.
>