On Fri, 16 Jan 2004, Junichi Uekawa wrote: > Hi, > > It seems to be another round of large-scale dependency chain, > close to release, thus we probably need a scheduled freezing > to get this thing to be released in sarge at all. > > Here's a rough timeline that I came up with: > > > 16 Jan 2004 : jack hits unstable > 18 Jan 2004 : Maintainer uploads are done by this date.
Hi, Two days for doing the maintainer uploads seems to be optimisitic, .. :) but we have to push toget this through. In general the roadmap is good. I would add that, if possible, only versions that have been in unstable or experimental at least get uploaded. To upload new versions, we have time between 11 Feb and 1 Mar. .. but probably this is too restrictive. I am tempted to upload a new version of qjackctl, for example, but haven done yet, because it might not compile on other architectures .. on the other hand, I don't know if the version from experimental compiles. Cheers Guenter > 25 Jan 2004 : All packages are NMU'd, or hinted 'remove' from testing in > -release > Uploads are freezed except for serious bug fixes > 1 Feb 2004 : Final upload, or hinted 'remove' from testing > 11 Feb 2004 : All jack-related packages enter testing, or gets removed from > testing. > > 1 Mar 2004 : New jack release to Debian unstable. > > > > How does this look like ? > > > > regards, > junichi > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
