[RP] When to release?

[Erik de Bruin <er...@ixsoftware.nl>]

Hi,

I'm using a new 'tag': [RP] for Release Process related thread, to
make filtering easier.

I want to ask for ideas about the criteria for starting a release.
Everyone can be a Release Manager (RM) and start a release. A release
takes a significant amount of time from the community, and this
community has a lot of projects that 'need' releases. With limited
resources, it seems to make sense to sort of triage which subproject
will be put up for release.

So, in addition to finding someone who is willing to be RM, it seems
prudent to ask the community the following question:

Is there enough support for releasing this subproject at this point in time?

My suggestion would be to put this to a vote. And in the vote, we
should indicate that anyone voting in favor promises to make at least
an effort to help out during the testing and RC phases.

What this aims to accomplish is to gauge the available resources in
the community and helps to avoid the situation where the RM puts a lot
of effort in preparing an RC, only to find out that there is hardly
anyone interested enough to help out with testing and voting.

Thoughts?

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

RE: [RP] When to release?

[Chris Martin <ch...@outlook.com>]

Yep, same here. I will make best efforts to be available for new releases :)
 
Chris
 
> From: aharui@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [RP] When to release?
> Date: Mon, 8 Dec 2014 16:31:41 +0000
> 
> Sorry, kept forgetting to reply.  I would prefer we not create a schedule.
>  When to release should factor in momentum, importance to the community,
> even marketing opportunities like conferences.
> 
> IMO, if a someone wants to take the time and effort to be an RM for a
> release, and can make the case that the new things in the release are
> going to be worth the effort to release it, and it won’t take away from
> momentum of someone else trying to release one of our other packages,
> then, until my work situation changes, I will always find time to review
> it (although I may not get to it right away).   And if I don’t see enough
> other folks step up to review that release, until Peter’s work situation
> changes, I will ask Peter to review it as well.
> 
> So, at least for now, anyone who wants to be an RM can be pretty sure
> there will be 3 voters.
> 
> -Alex
> 
> On 12/8/14, 5:08 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
> wrote:
> 
> >     Should we just leave a one month break, in-between releases and
> >start working on the next one after that?  Meaning there could be an SDK
> >release every 2 months or up to 6 times a year.  Releases would show
> >minor revisions unless there is a significant addition to the change list.
> >
> >-Start release cycle (takes roughly a month)
> >-After release is complete 1 month to gather more changes.
> >-Start next release cycle.
> >
> >
> >-Mark
> 
 		 	   		  

Re: [RP] When to release?

[Alex Harui <ah...@adobe.com>]

Sorry, kept forgetting to reply.  I would prefer we not create a schedule.
 When to release should factor in momentum, importance to the community,
even marketing opportunities like conferences.

IMO, if a someone wants to take the time and effort to be an RM for a
release, and can make the case that the new things in the release are
going to be worth the effort to release it, and it won’t take away from
momentum of someone else trying to release one of our other packages,
then, until my work situation changes, I will always find time to review
it (although I may not get to it right away).   And if I don’t see enough
other folks step up to review that release, until Peter’s work situation
changes, I will ask Peter to review it as well.

So, at least for now, anyone who wants to be an RM can be pretty sure
there will be 3 voters.

-Alex

On 12/8/14, 5:08 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:

>     Should we just leave a one month break, in-between releases and
>start working on the next one after that?  Meaning there could be an SDK
>release every 2 months or up to 6 times a year.  Releases would show
>minor revisions unless there is a significant addition to the change list.
>
>-Start release cycle (takes roughly a month)
>-After release is complete 1 month to gather more changes.
>-Start next release cycle.
>
>
>-Mark

RE: [RP] When to release?

[Kessler CTR Mark J <ma...@usmc.mil>]

     Should we just leave a one month break, in-between releases and start working on the next one after that?  Meaning there could be an SDK release every 2 months or up to 6 times a year.  Releases would show minor revisions unless there is a significant addition to the change list.

-Start release cycle (takes roughly a month)
-After release is complete 1 month to gather more changes.
-Start next release cycle.


-Mark

Re: [RP] When to release?

[Tom Chiverton <tc...@extravision.com>]

On 07/12/14 07:29, Erik de Bruin wrote:
> Is there enough support for releasing this subproject at this point in time?
I think this is always a good thing to ask :-)

I'm not aware of anything like a roadmap that says we'll release version 
X of Y on date Z, so we don't have that to kinda push us along. I don't 
see any need to have them either.

So our releases are either bug fixes (one bug that's "big enough", or 
"it's been so long, there are many fixes, we should") or features ("we 
finished months of work to get Z done").

Tom