I'm +1 on rolling an 0.20.4 RC (not 0.20.3.1) and moving our current 0.20.4 to 0.20.5
I would actually like to see 2248 put into a release ASAP so we can work out any new potential issues sooner than later. JG > -----Original Message----- > From: jdcry...@gmail.com [mailto:jdcry...@gmail.com] On Behalf Of Jean- > Daniel Cryans > Sent: Monday, April 05, 2010 6:52 PM > To: hbase-dev@hadoop.apache.org; apurt...@apache.org > Subject: Re: Vote on 0.20.3.1 > > Well we have to put up a RC, this would be when we have enough votes? > > There's also the question if 2248 should be included. > > J-D > > On Mon, Apr 5, 2010 at 6:49 PM, Andrew Purtell <apurt...@apache.org> > wrote: > > +1 > > > > What is the release schedule? By end of this week? > > > > Why not make it 0.20.4 as Todd asks? > > > > - Andy > > > >> From: Jean-Daniel Cryans > >> I propose that we tag rev# 919707 (just before the backport > >> of group commit) and apply a couple of the other biggest > >> fixes that happened after that: > >> > >> HBASE-2174 Stop from resolving HRegionServer addresses to > >> names using DNS on every heartbeat > >> HBASE-2308 Fix the bin/rename_table.rb script, make it work > >> again > >> HBASE-2023 Client sync block can cause 1 thread of a > >> multi-threaded client to block all others > >> HBASE-2305 Client port for ZK has no default > >> HBASE-2323 filter.RegexStringComparator does not work with > >> certain bytes > >> HBASE-2147 run zookeeper in the same jvm as master > >> during non-distributed mode > >> HBASE-2355 Unsynchronized logWriters map is mutated from > >> several threads in HLog splitting > >> HBASE-2358 Store doReconstructionLog will fail if > >> oldlogfile.log is empty and won't load region > >> HBASE-2365 Double-assignment around split > >> HBASE-2087 The wait on compaction because "Too many > >> store files" holds up all flushing > >> HBASE-2252 Mapping a very big table kills region > >> servers > >> > >> We could do without 2308,2305,2147 but the rest is pretty > >> important. > > > > > > > > > > > >
