[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

release status update



I wrote:
> We're still on track for release on the 15th. Here's a schedule up to
> then:
> 
> March 3rd       No changes to libraries past this point.
> March 6th       Final code changes for i386 enter the archive.
>                       (except new udebs and possibly partman)
> March 7th       All udebs to be copied from unstable to testing.
>                 First possibly final i386 CDs built; testing.
>                 String freeze begins.
> March 10th      String feeeze ends.
> March 14th      Final changes to udebs in archive.
>                 Final image and CD builds.
> March 15th	Release.

We're about a day behind on this schedule at the moment. The set of
udebs in unstable was copied to testing on Saturday, which gives me
something to fall back on if changes unexpectedly break something. The
March 7th cd images were not final quality, due to some initrd bloating,
and some new stuff not getting on in time. It's possible that today or
tomorrow's images will be something close to final release quality for i386.

The string freeze has not quite started, since a few strings were
changed today. Hopefully we've seen the last of that, and at least the
translators are doing well, with several languages already at 100% and
many > 90%. Also, the alioth move caused some problems. We'll push the 
end of the string freeze back to the 12th because of this late start.

The 14th is still the last day for changes to udebs, and the 13th is a
more practical deadline.

> Here, again is a checklist for what needs to be done for an architecture
> before release:
> 
>  1. CD images builds should be working (if applicable)

AFAIK, this is currently true for alpha, hppa, i386, ia64, and powerpc.
We need sparc and m68k CDs, I think work is in progress for m68k, but I
have heard nothing about sparc.

>  2. images must be in debian archive

Currently it's a bit of a mess:

- i386 is ok
- sparc images autobuilt for the first time today. Good job guys!
- powerpc continues to build every time w/o fail.
- hppa failed to build due to a missing build dep; trying that again.
- ia64 failed to build due to external breakage; trying that again.
- m68k failed to build due to using the wrong kernel; trying that again.
- mips succeeded with the previous version 3 days ago, but has not
  started/finished the latest version.

It would help if more porters could watch
http://buildd.debian.org/build.php?arch=&pkg=debian-installer and fix
problems as they show up. I appreciate those of you who do.

No other arches are being autobuilt at this time. If we want s390 or
something to be included in this release, it needs to be added to
debian/control ASAP.

>  3. at least one successful installation report per boot method

I have not had time to track installation reports. Could someone take
a pass through the list of recent reports and post a summary to the list
please? My vague impressions:

- i386 is generally working ok
- powerpc is working ok the subarches that worked last time
- once again we are almost out of time on including any more powerpc
  subarches
- s390 is working up to partitioning, and that is probably the only
  serious issue there
- m68k is working on amiga
- mips ??? haven't seen anything lately
- hppa ??? no activity lately, probably won't release
- ia64 ???
- sparc is working, mostly. May have some bad debs in testing though.
- arm is being worked on, but will not make this release (prove me
  wrong, please)

> Here is a short list of things that need to be done still before release:

And an update, as if you can't read the top of TODO yourselves. :-)

 - partman
        - testing!
        - clean up lvmcfg UI issue
        - probably go for i386, powerpc; other arches unknown
 - i18n:
        - bterm-unifont reloading. Bug#232397
 - lowmem package must enter archive
 - Check archive for udebs that need to be built on various arches;
   make sure everything is up-to-date. Also, make sure that eg,
   appropriate kernel debs have entered the archive on each
   architecture.
 - Write a release announcement.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: