Okay. Code cutoff EOD then. 

Is there a volunteer for doing the release tomorrow?

If not, I’ll do it using AP’s Google Doc [1]. If I do wind up doing the 
release, you’ll be able to find me on #jclouds in an emotionally distressed 
state.

Everett

[1] 
https://docs.google.com/document/d/10LkAD8Wk5Kcj38nQghTW-bQdCOXaxZad5W5Chu6HUCA/edit


On Oct 3, 2014, at 5:52 PM, Adrian Cole <adrian.f.c...@gmail.com> wrote:

> Sounds fair. Thanks for standing up for regular releases :)
> 
> -A
> 
> On Fri, Oct 3, 2014 at 3:49 PM, Everett Toews
> <everett.to...@rackspace.com> wrote:
>> So it’s a pretty normal and natural thing that, when a release is called 
>> for, people put up their hands and say “hold off for just a bit, I’ve got 
>> one more thing I want to add!”
>> 
>> If projects did hold off then nothing would ever get released because 
>> there’s always some good reason to put a hold on things.
>> 
>> Users expect a release from us every 6 weeks because that’s the minor 
>> release cadence we’ve committed to. 1.8.1 is already 3 weeks late according 
>> to our minor release cadence. I propose we stick with the schedule below and 
>> anything not in by Monday EOD can simply wait until the next release. It’s 
>> only 6 weeks away.
>> 
>> To prevent this from happening next time, I’ve been a little more specific 
>> on the Roadmap [1] based on our cadence. If people have more foreknowledge 
>> of when a release is going to happen, they can get that thing they want in 
>> there prior to the code freeze.
>> 
>> I’m hoping this isn’t too much to ask for and we can just ship some code.
>> 
>> Thanks,
>> Everett
>> 
>> 
>> On Oct 2, 2014, at 11:12 AM, Everett Toews <everett.to...@rackspace.com> 
>> wrote:
>> 
>>> Let's schedule the release of 1.8.1.
>>> 
>>> All code into 1.8.x by Monday, Oct. 6 EOD
>>> Begin release on Tuesday, Oct. 7
>>> 
>>> Can someone volunteer to do the actual release steps?
>>> 
>>> I'll be catching up with work stuff all next week after being on the road 
>>> for a few weeks but I can do it if necessary.
>>> 
>>> Thanks,
>>> Everett
>>> 
>> 

Reply via email to