Nick: Good to know that hbase 1.1 is around the corner. In the future, patch applicable to branch-1.1 should be attached to JIRA with branch-1.1 in filename for a QA run, right ?
Cheers On Thu, Apr 16, 2015 at 5:59 PM, Nick Dimiduk <[email protected]> wrote: > Devs -- > > I've created the new brach-1.1 and bumped the POM version on branch-1 to > 1.2.0-SNAPSHOT. I've also updated the pre-commit builds to watch for > "branch-1.1". I have insufficient JIRA permissions to I've not changed any > of the post-commit jobs yet. Hopefully this will be remedied in the coming > days. When committing patches, *please remember to include branch-1.1* in > your list. I'll be watching the log for the next couple days, keeping any > eye out for any patches that lose their way. > > Next up is wrangling blockers. There are currently 4 Blocker (HBASE-13149, > HBASE-13087, HBASE-10462, HBASE-13444) and 1 Critical (HBASE-13184) tickets > with fixedVersion 1.1.0. After that, build stabilization and cluster > testing. If you have some spare cycles, I'll appreciate the help :) > > I plan to post RC0 on or around April 24th. *That's 8-days from today*. > Let's see this done in time for HBaseCon! > > Thanks, > Nick > > On Tue, Apr 14, 2015 at 8:53 PM, Nick Dimiduk <[email protected]> wrote: > > > Hi Devs, > > > > I plan to create branch-1.1 on Thursday, sometime in the waking hours of > > PST. Please consider this your 48-hour-ish notice. In the mean time I'll > be > > familiarizing myself with Jenkins and setting up the relevant builds. > Once > > that bit is in order, I'll create the branch and send a followup > > notification. Stabilization of the branch will then commence. Shortly > > thereafter I'll ask to insert myself as a gatekeeper of new commits to > > branch-1.1. > > > > So basically, open season closes in 48 hours ;) > > > > Thanks a lot for your help in making this another great release for our > > esteemed project. > > > > Yours, > > -n > > > > On Wed, Apr 8, 2015 at 1:40 AM, Nick Dimiduk <[email protected]> > wrote: > > > >> Heya folks, > >> > >> We're down to a week remaining before my proposed branch date. A couple > >> big-ticket items have made it in since my last mail (HBASE-12972, > >> HBASE-12975, HBASE-11598, HBASE-13170). However, we still have about 70 > >> unresolved issues marked for this release, including 3 blockers > >> (HBASE-10462, HBASE-13087, HBASE-13149) and 2 criticals (HBASE-13184, > >> HBASE-11544). Let's get some more eyes on that lot. > >> > >> Also of notable omission: I don't see any JIRAs for bring MOB > >> (HBASE-11339) support back. The feature looks mostly finished and I > have it > >> on good authority that this is a straightforward back-port. Any takers > on > >> that? > >> > >> While I'm here rattling your chains, do us all a favor and go take the > >> latest RC's from other releases for a spin. We have two up for votes as > we > >> speak: 0.98.12 and 1.0.1. > >> > >> Happy HBaseing, > >> -n > >> > >> On Wed, Mar 25, 2015 at 6:05 PM, Nick Dimiduk <[email protected]> > >> wrote: > >> > >>> With about 100 issues beyond the 1.0.x line [0], I think it's time to > >>> start talking about our 1.1.0 release. Noteworthy goodness already > >>> committed to the branch includes: > >>> > >>> - Async RPC client (HBASE-12684) > >>> - Improved compaction controls (HBASE-8329, HBASE-12859) > >>> - Per-column family flush (HBASE-10201) > >>> - WAL on SSD (HBASE-12848) > >>> - Tons of region replica enhancements around META, WAL, and bulk > >>> loading (HBASE-11574, HBASE-11568, HBASE-11571, HBASE-11567) > >>> > >>> There's also talk of porting over the MOB goodness (HBASE-11339), > simple > >>> RPC throttling (HBASE-11598), and bits from the new procedure bus > >>> (HBASE-12439). Remember, this is a "minor release" [1] according to our > >>> newly adopted semantic versioning guide [2], which means if you want > new > >>> features in, you've got to speak up now or wait for 1.2. > >>> > >>> So timeline. Given HBaseCon [3] is right around the corner, I'd love to > >>> see the 1.1.0 bits on every attendee's laptops and fobs. To make that > >>> happen, I figure we'll need to start voting on RC's around April 24, > give > >>> me time to work out this whole RM thing and give you time to test 'em! > >>> Working back from there, we should have the major feature landed and > the > >>> release branch cut on or around April 15. Are you up for this schedule? > >>> > >>> For anyone who's bored, there's a couple unresolved blockers for this > >>> release. I'll also take your help in monitoring the jenkins builds > against > >>> branch-1. > >>> > >>> Thanks for your help in making this next release another great one! > >>> > >>> Cheers, > >>> -n > >>> > >>> [0]: http://s.apache.org/hbase-1.1-issues > >>> [1]: http://hbase.apache.org/book.html#hbase.versioning.post10 > >>> [2]: http://semver.org/ > >>> [3]: http://hbasecon.com/ > >>> > >> > >> > > >
