Release management thoughts for Dapper Drake

[Ante Karamatic]

On Sat, 2005-10-15 at 15:21 +0200, Ivan Krstic wrote:

> You didn't comment on adding some extra time to the release cycle until
> the release becomes enterprise-ready: I'm interested to hear what you think.

1 month isn't quite enough for testing enterprise ready services. Maybe
different aproach would be better. Why not take whole 6 months? Hoary
doesn't have obsolete postfix or apache or php (yes, it's 4, but read
on...) or any other service.

Imagine that we now call Hoary enterprise ready. It would be more up to
date than, for example RHEL4.2. Is it tested? Yeah! 6 moths of use is
quite enough testing.

Hipoteticly: with Breezy getting to desktop, we could push Hoary as a
enterprise ready OS. ... When Dapper+1 hits desktop, we could say Dapper
is enterprise ready. It would be well tested and well supported.

We could even provide some sort of updates that would contain all bug
fixes in those 6 month. And every six month release new bugfix updates.
Yes, we could even backport some services from Dapper+1, but that's not
good idea since we don't want to support so much different versions.

What do you think about that?

-- 
Ante Karamatic <ivoks at ubuntu.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.ubuntu.com/archives/ubuntu-devel/attachments/20051015/d074e48a/attachment.pgp