On Mon, Nov 25, 2013 at 9:12 AM, Marcus Eriksson <krum...@gmail.com> wrote:

> would it be possible to include
> https://issues.apache.org/jira/browse/CASSANDRA-6284 ? It is tagged 2.0.4
> but it feels pretty serious.
>

Sorry, but that one missed the train. And in any case, we try to avoid
blocking releases unless there's a new regression and that one is not new.
To put it another way, you'll still be better off with 2.0.3 than with
2.0.2 even if 2.0.3 is not bug free.

But if it turns out that CASSANDRA-6284 is a big problem for many people,
we can just release 2.0.4 quickly.

--
Sylvain


>
>
> On Fri, Nov 22, 2013 at 6:32 PM, Vijay <vijay2...@gmail.com> wrote:
>
> > +1
> >
> > Regards,
> > </VJ>
> >
> >
> > On Fri, Nov 22, 2013 at 2:24 PM, Sylvain Lebresne <sylv...@datastax.com
> > >wrote:
> >
> > > With now CASSANDRA-6374 included, I propose the following artifacts for
> > > release as
> > > 2.0.3.
> > >
> > > sha1: 3c9760bdb986f6c2430adfc13c86ecb75c3246ac
> > > Git:
> > >
> > >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.2-tentative
> > > Artifacts:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-164/org/apache/cassandra/apache-cassandra/2.0.2/
> > > Staging repository:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-164/
> > >
> > > The artifacts as well as the debian package are also available here:
> > > http://people.apache.org/~slebresne/
> > >
> > > The vote will be open for 72 hours (longer if needed).
> > >
> > > [1]: http://goo.gl/Ougwt2 (CHANGES.txt)
> > > [2]: http://goo.gl/8O6gX2 (NEWS.txt)
> > >
> >
>

Reply via email to