I wrote: > In a sense we're not done with beta2 yet, since we have between 1 and > 2.5 architectures that are still in positions to possibly be added to > the beta in a week or two. At the same time, I am eager to open unstable > back up to continued development especially with so many improvements > already waiting to go in. The conflict here is that if a package is > destablised in unstable, and then the beta2 "backport" needs to get a > minor fix to that package into sarge to make it work on a pending > architecture, I won't be able to get that fix into sarge; it will be > blocked by the changes in unstable. > > So starting after tomorrow's dinstall (just in case something goes > wrong), unstable is reopened for uploads of: > > I. NEW udebs (partman, etc), that are not present in sarge. > II. Any changes necessary for mips, alpha, and powerpc subarches, > targeted at beta 2. > III. udebs that are only for architectures that do not plan to > release with beta 2 (such as boot loader installers for > unreleased architectures) > IV. udebs that are only for architectures that have already > released for beta 2 > > But is still closed to uploads of: > > X. Developmental changes of udebs that are in beta2. (busybox, > build/, base-installer, main-menu, anna, etc, etc) I talked this over with aj, and we may be able to relax this somewhat. It may be possible to upload udebs directory to testing, and have them moved in from testing-proposed-updates. I'll investigate further, and if it works out, we'll be able to make changes to more stuff in unstable. -- see shy jo
Attachment:
signature.asc
Description: Digital signature