I'm not a fan of blocking a new rc because of bugs that are not
regressions new in that release.  I'd also like to get more testing on
the 1.2 fixes since b2.  But we can call it b3 instead of rc1 if you
want.

On Mon, Dec 3, 2012 at 1:19 PM, Brandon Williams <dri...@gmail.com> wrote:
> On Fri, Nov 30, 2012 at 4:17 AM, Sylvain Lebresne <sylv...@datastax.com> 
> wrote:
>> We've fixed pretty much all know issues since beta2 (remains 2 issues tagged
>> 1.2.0 but none are really critical if they don't make it anyway) so so I
>> propose the following artifacts for release as 1.2.0-rc1.
>
> I think we should solve CASSANDRA-5009 first (which was discovered
> after this vote.)  While it's rare to trigger, the impact is pretty
> severe.
>
> -Brandon



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder, http://www.datastax.com
@spyced

Reply via email to