cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <>
Subject Re: Call for 4.2 and 4.1.1 Release Managers!
Date Wed, 27 Mar 2013 17:00:52 GMT
On Thu, Mar 21, 2013 at 4:09 PM, Musayev, Ilya <> wrote:
> Chip
> Would you please collaborate as to what release manager does. An examples would be nice.
> Thanks
> ilya

Hi Ilya:

So the short description is 'cat herder'

The real tasks/duties - assuming a feature release:

Act as the release schedule reminder - effectively driving and
enforcing the dates we agreed to earlier in the release cycle.
Triage/manage the bugs/new features coming into a feature release,
ensuring the severity is set appropriately and drawing attention to
things that get ignored/dropped.
Calling for votes
Creating releases (and signing, and getting them uploaded and mirrored)
Acting as change control when we start locking down a branch for
release - essentially ensuring that changes after a certain period get
some minimum level of review and testing, and that we aren't deviating
from that. Chip has called himself the human gerrit because of this.

The point releases are a bit different - there are no new features,
and you really are trying to focus on bugfixes, so point releases
should be a bit less work. Experience has shown that most folks aren't
as happy to fix bugs as to develop new features. So you become much
more of a 'attention seeker' - or perhaps 'attention driver' is a
better word. - driving attention to things that need to be fixed. It
also means spending copious amounts of time in Jira (as you would in a
feature release, but this is even more pervasive) You essentially have
to look at bugs reported against newer releases and see if they apply
- if patches for them are applicable to your release (e.g. if I fix a
bug for 4.2 - does that bug apply to 4.1? Should the fix be in 4.1.1?)


View raw message