adding a QA responsibility to the release team??

Ian Monroe ian at
Sun Sep 18 18:34:54 UTC 2011

On Sun, Sep 18, 2011 at 20:21, Rex Dieter <rdieter at> wrote:
> On 09/17/2011 11:59 AM, Giorgos Tsiapaliwkas wrote:
>> So,i propose a new timeline addition in which we will check our tarballs
>> better and a new bugzilla compoment in which we will be able to
>> report regressions and critical bugs which hasn't been fixed.
> There's already a week between initial tarball creation (for packagers) and
> official release.  Are you proposing making this longer? or... some other
> workflow?
> 2 additional comments:
> * I think it may be unwise to conflate release engineering with QA, they
> really are 2 distinct items (though obviously interelated).
> * I'm also of a mind there's no special need for additional bugzilla
> components... in the past, when/if regressions or blockers identified in our
> "week", they were dealt-with appropriately.

Seems like the basic issue is that the (official) release + a week or
two is usually more stable then the release. But that's because the
release spurred people to find bugs and fix them.


More information about the release-team mailing list