You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Sean Busbey <bu...@cloudera.com> on 2014/02/25 01:42:22 UTC

[DISCUSS] Updating planned release dates

Right now, Jira lists the following scheduled release dates:

* 1.5.1 : 2013-07-24
* 1.4.5 : 2013-10-31
* 1.6.0 : 2013-11-24

I'd like to update these to reflect when we currently think things are
likely to complete.

Here's my WAG:

* 1.5.1 : 2014-02-28
* 1.4.5 : 2014-03-19
* 1.6.0 : 2014-05-29

My reasoning:

* 1.5.1 RC2 failed due to a miscommunication, RC3 is unlikely to have issues
* AFAIK, 1.4.5 still needs to go through most of the long run tests and
that will take time. I'd like to wait to start until we have lessons from
the 1.5.1 release in hand.
* 1.6.0 still has a ton of tickets, that date is based on a net burn down
rate of just over 1 per business day (after adjusting for the time it takes
to do tests)

Thoughts?

-Sean

Re: [DISCUSS] Updating planned release dates

Posted by Josh Elser <jo...@gmail.com>.
Agreed on 1.5.1 (just sent out RC3). I can just update it if you'd like 
when I close out the Jira version.

re: lessons-learned, I think I have most (all?) of them documented 
already[1]. Things I didn't know I made a point to write down. That, 
coupled with the script that Christopher made, makes a pretty thorough 
guide, IMO. I'd defer to what Mike (he's the RM for 1.4.5, right?) thinks.

Personally, I haven't been looking heavily at 1.6.0 since mid-January, 
so I can't comment there either.

[1] http://accumulo.apache.org/releasing.html
On 2/24/14, 7:42 PM, Sean Busbey wrote:
> Right now, Jira lists the following scheduled release dates:
>
> * 1.5.1 : 2013-07-24
> * 1.4.5 : 2013-10-31
> * 1.6.0 : 2013-11-24
>
> I'd like to update these to reflect when we currently think things are
> likely to complete.
>
> Here's my WAG:
>
> * 1.5.1 : 2014-02-28
> * 1.4.5 : 2014-03-19
> * 1.6.0 : 2014-05-29
>
> My reasoning:
>
> * 1.5.1 RC2 failed due to a miscommunication, RC3 is unlikely to have issues
> * AFAIK, 1.4.5 still needs to go through most of the long run tests and
> that will take time. I'd like to wait to start until we have lessons from
> the 1.5.1 release in hand.
> * 1.6.0 still has a ton of tickets, that date is based on a net burn down
> rate of just over 1 per business day (after adjusting for the time it takes
> to do tests)
>
> Thoughts?
>
> -Sean
>

Re: [DISCUSS] Updating planned release dates

Posted by Christopher <ct...@apache.org>.
Seems reasonable to update these tentatively in JIRA... but I hope
1.6.0 is out before the end of March.

I would say that the the 1.4.5 release will probably not benefit from
1.5.1's lessons learned much, though. A lot of work went into
simplifying/automating the release process in 1.5.0 that I have no
intention of replicating for 1.4.5. It may be that it would be a
minimal effort to do that, but my guess is that the release processes
between 1.4.5 and 1.5.1 will be very different.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Mon, Feb 24, 2014 at 7:42 PM, Sean Busbey <bu...@cloudera.com> wrote:
> Right now, Jira lists the following scheduled release dates:
>
> * 1.5.1 : 2013-07-24
> * 1.4.5 : 2013-10-31
> * 1.6.0 : 2013-11-24
>
> I'd like to update these to reflect when we currently think things are
> likely to complete.
>
> Here's my WAG:
>
> * 1.5.1 : 2014-02-28
> * 1.4.5 : 2014-03-19
> * 1.6.0 : 2014-05-29
>
> My reasoning:
>
> * 1.5.1 RC2 failed due to a miscommunication, RC3 is unlikely to have issues
> * AFAIK, 1.4.5 still needs to go through most of the long run tests and
> that will take time. I'd like to wait to start until we have lessons from
> the 1.5.1 release in hand.
> * 1.6.0 still has a ton of tickets, that date is based on a net burn down
> rate of just over 1 per business day (after adjusting for the time it takes
> to do tests)
>
> Thoughts?
>
> -Sean