Differences between revisions 16 and 17
Revision 16 as of 2005-01-02 16:02:20
Size: 2194
Editor: anonymous
Comment:
Revision 17 as of 2005-01-03 07:02:10
Size: 2243
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 * AddAnotherRepositoryBetweenUnstableAndTesting

The goal of this suite of pages is to gather the collective wisdom of Debian developers on new release methodologies for Debian, with an aim toward reversing the current trend of it taking longer and longer for us to make a release.

This set of pages is being developed because while plenty of people have made various suggestions on debian-devel, this has only resulted in threads with hundreds of messages, with debate being more rational in some places than others.

Feel free to add new pages, or add new arguments pro or con to a page, but do respect the opinions of others and bear in mind that the idea is to arrive at a set of well specified proposals for how Debian can release, and not to promote your idea over all others. If your opinion does not represent the consensus of a pro or con for a release method, add it as a comment with your name on it.

The list of release proposals:

Besides a new release process, it is also very interesting to figure out why the current process scales so badly. Where are the bottlenecks and what can we do about them?

This is an evolving document -- refer to RecentChanges to find newly updated pages.

  • I would like to also propose a goal based release: To have an actual goal for that round of Debian development. This current release, for the end user, appears to be a software update. Not a very big change in policy. It might be worthwhile to set goals for what people would like to see changed, or advanced, then decide on a good time frame so everyone is on the same page, working toward the same goal, and knowing where they stand. This appears to work pretty well for kde.

- Christain (Debian user)