[csw-maintainers] automated catalog promotion for packages

[Ben Walton]

Excerpts from Geoff Davis's message of Fri Nov 11 12:10:10 -0500 2011:

Hi Guys,

> While I can't speak for all of the arcanery behind our bug filing
> process, I'd like to point out the case where someone files a bug
> requesting an upgrade of a package. Those types of bugs should not
> normally block promotion of a previous version of a package. I guess
> it should block if it's a security consideration or something like
> that, but a request to go to Cfengine 3 should not block a Cfengine
> 2 package for example.

Some very good points have been raised here so far.  I'll try to reply
to as many as possible right now.

This has been noted a few times and it's something I didn't consider
last night.  I think it's a very good fit though.  We just need to
decide which type and severity combinations should stop the clock on a
promotion.  We can augment the classes with more categories as
required to make the functionality what we want.

A maintainer should have the ability to downgrade a bug such that the
clock is reset.  Should the countdown resume or be reset to two weeks?
I'm inclined to think that unless new bugs are filed, it simply
resumes from where it left off, but as the expiration approaches, that
doesn't leave much wiggle room for any squabbling over the semantics
of a downgrade.  (That knife can cut both ways.)

More to come as replies where appropriate.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302