Re: RFC: New Upload Procedure

[Christian Schwarz <schwarz@monet.m.isar.de>]

Hi!

I'm glad that everyone likes the proposal. Here are the comments I have
received so far:

(1) Everyone seems to be confused by the "closes"/"closed" so we might
want to change this. Someone suggested to use "fixes" all the time: 

  foo (1.0-5) unstable; urgency=low

    * Recompiled with libc6, fixes:Bug#98765,Bug#98766

   -- Wile E. Coyote <coyote@debian.org>  Wed, 29 Oct 1997 14:22:37 -0600

  [snip]

  Format: 1.5
  Date: Wed, 29 Oct 1997 14:22:37 -0600
  Source: foo
  Binary: foo
  Architecture: source all
  Version: 1.0-5
  Distribution: unstable
  Urgency: low
  Maintainer: Wile E. Coyote <coyote@debian.org>
  Fixes: 98765 98766 99999
  Description: 

Is this ok with everyone?


(2) A few people have suggested to relax the matching pattern for the
"fixes" tag in the changelog file. I agree that we should consider making
the patter case-insensitive and allowing white spaces:

           /fixes:\s*bug\#\d+\(,\s*bug\#\d+\)*/i

This would match

    * Recompiled with libc6, fixes: Bug#98765, Bug#98766
    * Removed `rm -rf /' from postrm script, FIXES:BUG#99999

but not

    * Fixed bug#1234 partially

Comments?


(3) Ioannis suggested to introduce a more general syntax:
        [@Close 7889 7777]
which could also be used for other tags like that:
        [@Delay 2days]
        [@Notify  eric@alaska.com  joe@blue.book.com ] 
I think that we don't need such a general solution and that the syntax
differs too much from how the changelog files looks now. Other opinions?


(4) A few people were uncertain about the time when the announcement will
be sent: The announcement should be sent to the list as soon as the file
is available in Incoming since this has proven to be useful when an error
is made with the upload (e.g. releasing a "new upstream release" to
"stable" without comments :-) Often, such errors are discovered by other
developers before the package actually gets installed.

However, I agree that "stable" uploads should be announced only after the
package has actually been installed. So I suggest this:

   - _any_ upload (even "stable" ones) are announced on
debian-devel-changes right after the package appeared in Incoming on
master

   - "stable" uploads are announced again when the package is installed in
the archive; this time the announcement is sent to debian-changes
    (we might consider posting a "change summary" instead of the
individual changelog files in that case)

Comments?


(5) Fabrizio suggested that each developer can have a ~/.changes-template
file in his/her home directory on master, which (the file :) is inserted
at the top of the message then. The file can contain something like this:

  ---- cut ----
  Hi folks!
  as usual you'll find this package also in ftp://ftp.my.site/my/dir/

  %.changes%

  Have a nice day!
  me
  --
  my signature
  ---- end ----

What do others think?



Any comments are appreciated.


Thanks,

Chris

--                  Christian Schwarz
                   schwarz@monet.m.isar.de, schwarz@schwarz-online.com
                  schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
                       
                PGP-fp: 8F 61 EB 6D CF 23 CA D7  34 05 14 5C C8 DC 22 BA
              
 CS Software goes online! Visit our new home page at
 	                                     http://www.schwarz-online.com


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .