[csw-maintainers] Submitting a package to the release manager

[Ben Walton]

Excerpts from Maciej (Matchek) Blizinski's message of Thu Oct 08 11:08:23 -0400 2009:

> I thought the same way, but there was a thread on this list (I
> couldn't find it in the archives) in which somebody said that the
> package file should be removed from testing when it's being send to
> the release manager. Intuitively, I would think that it's best if the
> files stays in testing/ until it's released, to avoid a gap in the
> file availability.

The tool that pushes files to the mirrors and registers it in the DB
should also reach in an rm the file iff the filename and md5sum match.
That gets the best of both worlds.  The release script is then simply
a wrapper around an email (or other trigger) to the release system.

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

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20091008/2909063f/attachment-0002.asc>