All yours then, Matt. I think all blocker issues are assigned (and I have none of them ^^). If anyone wants to reassign one to me or there is something urgent I can help with, just ping me!
On 21 May 2013 22:52, Andrew Bayer <[email protected]> wrote: > learn2notdoublereply. =) > > A. > > On Tue, May 21, 2013 at 1:51 PM, Matt Stephenson <[email protected]>wrote: > >> Ignasi, >> I can take jclouds-labs-google, I should probably learn it. >> >> >> On Tue, May 21, 2013 at 1:45 PM, Ignasi <[email protected]> wrote: >> >> > Jeremy, thanks! You have >> > https://issues.apache.org/jira/browse/JCLOUDS-62 assigned. Would you >> > be able to have a look at it? If not, no problem; I'm going to take >> > jclouds-labs-google, and can do the rest too. >> > >> > On 21 May 2013 22:19, Matt Stephenson <[email protected]> wrote: >> > > FYI : https://issues.apache.org/jira/browse/INFRA-6295 >> > > >> > > >> > > On Tue, May 21, 2013 at 9:39 AM, Andrew Bayer <[email protected] >> > >wrote: >> > > >> > >> I should be fine - I've done this before with Bigtop and Whirr, which >> is >> > >> why I volunteered to RM our first release. =) I'll try to put >> together a >> > >> checklist of pre-release tasks we've got to get done on Thursday, and >> > then >> > >> a release candidate evaluation checklist as well. >> > >> >> > >> The wiki isn't set up yet, right? I don't think Adrian's opened a >> ticket >> > >> for that... >> > >> >> > >> A. >> > >> >> > >> On Tue, May 21, 2013 at 9:34 AM, Matt Stephenson <[email protected] >> > >> >wrote: >> > >> >> > >> > Awesome, is there anything anyone can help you with? It sounds >> like a >> > >> > sizeable amount of work for one person. >> > >> > >> > >> > >> > >> > On Tue, May 21, 2013 at 8:53 AM, Andrew Bayer < >> [email protected] >> > >> > >wrote: >> > >> > >> > >> > > So overall, I'd like to try to get a first RC ready for review by >> > >> > everyone >> > >> > > by Wednesday (May 29th) next week - I get home very late Wednesday >> > >> night >> > >> > > this week, but have a bunch of work to deal with for the rest of >> the >> > >> > week, >> > >> > > so the additional time would be handy. >> > >> > > >> > >> > > After we get a first RC, we (the project and our mentors) should >> > review >> > >> > > everything for a couple days, with the goal of getting the >> > for-realz RC >> > >> > up >> > >> > > for an official vote by the PPMC (us) and IPMC (the incubator PMC) >> > by >> > >> end >> > >> > > of day on that Friday, May 31st. With the standard 72 hour >> > (excluding >> > >> > > weekends) voting window, that'll give us a shot at having an >> > official >> > >> ASF >> > >> > > release of 1.6.1-incubating done by end of day the following >> > Wednesday, >> > >> > > June 5th. But odds are that there'll be flaws in the RC we submit >> to >> > >> the >> > >> > > IPMC that'll need correcting, with some iteration/new votes, etc. >> > >> That's >> > >> > > why I'm targeting Friday May 31st for the start of the vote - that >> > >> gives >> > >> > me >> > >> > > an extra 48 hours over the weekend to deal with nitpicking. =) >> > >> > > >> > >> > > How does that sound to everyone? I know it's not quite as fast as >> we >> > >> > might >> > >> > > like, but I'd rather be safe than sorry, and I want to make sure I >> > have >> > >> > the >> > >> > > time to do this release properly *and* document the hell out of >> > >> > everything >> > >> > > so that, say, Andrew Philips can handle the next one without >> > needing me >> > >> > to >> > >> > > do much of anything. =) >> > >> > > >> > >> > > A. >> > >> > > >> > >> > >> > >> >> > >>
