How to upload a package to volatile (was: Re: iso-codes upload)

[Martin Zobel-Helas <zobel@ftbfs.de>]

Hi,

On Sunday, 31 Jul 2005, you wrote:
> Hi,
> Can you please describe what is to happen next, to get it into volatile?

here comes a short description about uploading a package to volatile:

1. Send a mail to debian-volatile@lists.debian.org
   This is for discussing your changes in public. It is also a good idea to
   include a link to a unified diff. Please remember the volatile
   guidelines, i.e. make only necessary changes.
   I wish we could have more discussion on the volatile mailing list
   about packages to go into volatile, as the volatile team wants to
   know which changes the users want, and which not... Everybody on the
   list is encouraged to review the proposed changes.

2. Upload to volatile
   If you got the okay from the list, please upload at least
   source+binary-all packages to volatile-master.debian.net using FTP.
   Please document changes in debian/changelog. Just saying
      * Upload package to volatile
   is _NOT_ okay.

   If it is not your first upload to volatile and your changes to the
   previous version are security fixes, please tell us in advance. If
   you already have, please put CAN numbers in the changelog. If you
   do not have them, please tell us, we can obtain them for you. If you
   want to contact the volatile-team private, than please speak with one
   of its team members. Sometimes there are embargo dates on
   publification of security bugs / fixes. We respect them.

3. Packages are build automaticaly
   Now packages are build by the autobuilder network. No interaction is
   needed here.

4. volatile-announce-mail is being prepared
   While the package is autobuilded the volatile team will contact you
   about the content of the announce mail which is send via
   debian-volatile-announce@lists.debian.org

5. Package is released.
   The package is finally reviewed and released.


-- 
Martin Zobel-Helas
debian-volatile Team member