Re: plans for d-i rc2 (and Oldenburg meeting)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
At 18 Sep 04 00:07:32 GMT,
Joey Hess wrote:
> Since a string freeze takes at least a week, and getting all the images
> built and tested for release took two weeks last time, we're still some
> time from a rc2 release. The Oldenburg meeting is coming up next week,
> and I dislike trying to do releases at such meetings. Still, we've
> probably now reached the point where installation reports from rc1 are
> less useful, and where we want users to be trying the latest version of
> the installer.
Sigh, it sounds Debian can't release Sarge on "19 September 2004", and
release late isn't only a few days. Is it true?
> This release would not rc1 involve a string freeze and a full set of
> updated translations. It might even be broken on some architectures, if
> some arches are currently broken. It would simply be a consistent
> snapshot of what we have accomplished in the 2 months since rc1. It
> would probably still take about a week to get it built and released; the
> release building could begin right after Oldenburg for a release near
> the beginning of next month. The rc2 release would then probably not
> happen until the end of next month.
Does our process prevent Sarge release schedule?
It sounds "We won't release Sarge till end of October or maybe beginning
of November".
> Alternatively, we could skip this and go ahead with getting rc2 out
> immediatly after Oldenburg. That would mean probably a string freeze the
> last week of this month, and a rc2 release near the middle of next month.
And it sounds "We won't release Sarge till middle or end of October".
> Which alternative is better, I leave up to you -- and the timetables of
> the release managers.
Hmm, I couldn't agree with both plan, especially about schedule. 2nd
plan is near my wish, but both look make Sarge release too late.
After RC2 released, what's our action? If user find/report a bug, we
try to reproduce and fix... Then, release RC3, 4, ...?
I think it is better to next d-i release is really final, won't accept
any modification and fix to trunk.
I hope string freeze comes really soon.
I remember previous string-freeze event... Someone changes too many
messages, and someone won't keep a schedule. I don't want same
doing. And "Native English" improves meaning of message for English,
but unfortunately in my experience it doesn't improve so for
translated message. It simply causes an endless work for many
translators.
If you try to improve some features and suppose new message for
translation, how about add it into templates file before implement it?
We don't need to wait string freeze time by this.
Please don't lead us death march, Joey and release managers. :-)
I think Sarge is simply middle goal for Debian. We have a chance to
improve or fix minor problem by next point release or major release.
Late and late for "it's not perfect" causes disappointment of
developers/workers/users. At least I'm disappointed.
Thanks,
- --
Kenshi Muto
kmuto@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAkFMBEwACgkQQKW+7XLQPLFazwCgiy1bU7RBgpOpJfblQFCG54aP
2OMAnjgvuIUiF5CO3mbJtKqWOEhaopUq
=kKZ+
-----END PGP SIGNATURE-----
Reply to: