Joey Hess wrote: > > arch/hppa/palo-installer > 0.0.7 has some new changes from Colin, which I'd just as soon > avoid in sarge due to lack of testing. Better to apply the > translation fixes to the sarge branch and release that. Since the fix is in sarge it only needs a release from there. Someone else will have to do it as my hppa is not usable: joey@bison:~>svn co svn+ssh://svn.debian.org/svn/d-i/branches/d-i/sarge d-i-sarge svn: relocation error: svn: undefined symbol: �� :-( > > arch/i386/grub-installer > 1.08 has some new changes from me, which only affect lvm 1 and > which I'd just as soon avoid in sarge due to lack of testing. > Better to apply the translations fixes to the sarge branch and > release that. Released from sarge branch as 1.07.1 > > arch/ia64/elilo-installer > 1.3 in unstable is probably safe though not really needed for > rc3. > 1.4 is unreleased and has more changes, which I'd just as soon > avoid for sarge. > Probably best to merge 1.3 to sarge branch and then apply the > translations to there and release a 1.3.1. Or test the pending > 1.4. Still todo. > > arch/s390/dasd > 0.0.11 in trunk has template naming and other changes that I > don't see a need to put in sarge. Better to apply the > translation fixes to sarge branch and release that. > > arch/s390/netdevice > 0.0.8 ditto as s390-dasd. Still needs upload, though the fixes are in the sarge branch. > > arch/sparc/silo-installer > 1.00 was just released and has changes I'm unsure of. > We either need to get that tested until we're sure it's ok for > sarge, or superscede it with an upload from the sarge branch > with the translation fixes. Still todo. > > base-installer > Trunk is forked with post-sarge changes. Translation fixes > should be applied to sarge branch and released. 1.13.2 released from sarge branch. > > cdebconf > Trunk is forked with post-sarge changes. Translation fixes > should be applied to sarge branch and released. To complicate things, 0.74 from trunk got into sid already, and the non-udeb parts have already reached testing. I do consider the 0.7[34] changes as better post-sarge, but that may not be possible at this point w/o uploading a reverted version. > > iso-scan > 1.04 in trunk has a few changes, it might be better to apply the > translation fixes to sarge branch and release that. 1.03.1 released from sarge branch. > > kbd-chooser > 1.09 has usb change that I've not yet decided about for sarge. > Doesn't help that it's not yet built on arm, i386, or mips, > nearly a month after its upload. Unsure what to do. Still todo. > > netcfg > 1.08 in trunk has several changes, untested. Better to apply > translation fix to sarge branch and release from there. Released 1.07.1 from sarge branch, which also includes a code change. > > network-console > 0.0.11 includes a security fix and is oked for sarge. > 0.0.12 in trunk has template name changes that I slighyly would > prefer to avoid. > Unsure what to do, possibly merge 0.0.11 to sarge branch, along > with template fixes, and release from there. Or go with 0.0.12. Still todo. > > prebaseconfig > Has a new code change in trunk, don't know if this will make > sarge or not; if not the translations should be applied to sarge > branch and a release done from there. Released 1.06.1 from sarge branch. > > preseed > Branched for sarge; translations need to be updated in sarge > branch and a release done from there. Released 1.01.1 to t-p-u from sarge branch. -- see shy jo
Attachment:
signature.asc
Description: Digital signature