Plan for tomorrow's (20070604) Release Engineering meeting

[Patrice Dumas]

On Sun, Jun 03, 2007 at 11:08:23AM -0400, Jesse Keating wrote:
> /topic RELENG-Meeting - Updates Policy - JesseKeating

About update policy, first I think that it should be easy to do 
something like:

make go-to-release

which would use the changelog entry (or something similar). If I recall
well this is already more or less agreed.

It should also be possible for a maintainer to decide what amount of
time the package should stay in the testing repo. The default would be
something reasonable (one week?). The rel-eng team could have the 
possibility to block the update at any time if they find something is 
abnormal.

For example 
make go-to-release 1
would make the package stay 1 day in testing repo.

And there should be automatic checks for broken deps, for duplicated
provides, for upgrade path.
 
> /topic RELENG-Meeting - Freeze Policy - JesseKeating

On that topic, I think that during a freeze there shouldn't be a need to 
mail to rel-eng to push to the frozen collection. It should be a
specific target, so for example to push to the frozen collection one
should do

make build
make go-to-freeze

Then the rel-eng would see that (together with the changelog entry), and 
block if something seems dubious, or if it is too late in the freeze. It 
would be nice to have checks for broken deps, for duplicated provides, 
for upgrade path. And when rel-eng block something they should be able
to simply contact the maintainer, for example by replying to a mail, or
optionally on fedora-devel or a similar list.

--
Pat