Differences between revisions 2 and 3
Revision 2 as of 2004-12-27 07:53:25
Size: 826
Editor: anonymous
Comment:
Revision 3 as of 2004-12-27 09:43:25
Size: 952
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
Other thoughts:
This could be combinated with the ReleasePerSubsystem model, core would simply be a subsystem in this model.

Pick a subset of Debian that is the core. Release the core only when it's ready, which should be more frequently than when all of Debian is ready. For the other stuff, users would have to [FIXME: do what?]

Pros:

  • Shorter release cycles - don't have to wait for Gnome/KDE/insert-big-and-not-essential-package-of-choice-here.
  • Package pool could theoretically be reduced to a few megabytes.

Cons:

  • Users are on their own with most of the applications, since Debian's archive is de-facto reduced to just another pool with almost no QA (3rd party pools can do the same).
  • Security updates only for core packages, or the need for another security infrastructure (when and where to release security updates for non-core packages?).

Other thoughts: This could be combinated with the ReleasePerSubsystem model, core would simply be a subsystem in this model.

See ReleaseProposals for alternatives.