Differences between revisions 34 and 37 (spanning 3 versions)
Revision 34 as of 2005-01-08 08:56:26
Size: 3665
Editor: anonymous
Comment:
Revision 37 as of 2009-03-16 03:32:58
Size: 1608
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
- Ozgur Murat Homurlu
Line 24: Line 23:
See ReleaseProposals for alternatives.[http://www.zy-image.com 摄影学校]
[http://www.ltjz2000.com/beijingsijiazhentan.htm 北京私家侦探]
[http://www.timead.net/zgjs.html 窄告]
[http://www.etoo.cn/jianruishiyou 尖锐湿疣]
[http://www.etoo.cn/jlb 计量泵]
[http://www.etoo.cn/yiliao/nwgd.htm 内外固定]
[http://www.etoo.cn/yiliao/jkhc.htm 进口耗材]
[http://www.etoo.cn/yiliao/gkhc.htm 骨科耗材]
[http://www.etoo.cn/yiliao/gkqc.htm 骨科器材]
[http://www.etoo.cn/yiliao/ylqx.htm 医疗器械]
[http://www.etoo.cn/yiliao/ylqc.htm 医疗器材]
[http://www.16safe.com/qiche/anquan.htm 轮胎安全]
[http://www.16safe.com/qiche/znjc.htm 智能监测]
[http://www.16safe.com/qiche/luntai.htm 轮胎防爆]
[http://www.16safe.com/qiche/qiche.htm 汽车轮胎]
[http://www.ltjz2000.com/zhentan.htm 私人侦探]
[http://www.ltjz2000.com/sj.htm 私家侦探]
[http://www.ltjz2000.com/xunren.htm 寻人]
[http://www.ltjz2000.com/hydc.htm 婚姻调查]
[http://www.ltjz2000.com/dc.htm 调查]
[http://www.ltjz2000.com/zhentan.htm 侦探]
[http://www.ltjz2000.com/sj.htm 北京私家侦探]
[http://www.ltjz2000.com/dc.htm 调查公司]
[http://www.etoo.cn/zhaigao 窄告]
[http://www.etoo.cn/sports 健身器材]
[http://www.etoo.cn/sports 健康器材]
[http://www.etoo.cn/sports 体育器材]
[http://www.etoo.cn/stadium 场馆设备]
[http://www.etoo.cn/stadium 跑步机]
[http://www.etoo.cn/21win-win 拓展训练]
[http://www.wjmgy.com 脉管炎]
[http://www.wjmgy.com/1 脉管炎]
See ReleaseProposals for alternatives.

Note: This proposal doesn't solve the problem on its own, it's somehow higher level than other proposals. Probably some other proposal like FixedReleaseDate is needed as well.

Proposal:

Current release method is preserved (with some (this is where the other propsals are used) improvements). Only change made is permitting fixing RC bugs in stable even if packages' behaviour or upstream versions change (but doesn't break the rest of the system). Of course this kind of upgrades should be avioded as much as possible and abusing of the opportunity to fix bugs after release must be prevented. After sometime of stable release "Really Stable" which has the current policy of stable is released. I have, like, 9 months periods of release cycle for "new stable" and 18 months for "Really Stable" in my mind. I suppose this implies FixedReleaseDate. This propasal can be an extension to FixedReleaseDate or other proposals.

Pros:

  • Those who want newer versions of software will benefit from "new stable". They will accept upgrades which change behaviour of a package as long as these are well documented.
  • People who like current stable and > 1 years release cycles will benefit from "Really Stable" more than current stable since the "Really Stable" will have more real life usage testing (in new stable phase).

Cons:

  • Security team will have to maintain two different releases at the same time.
  • Developers will possibly need to do more work for preparing fixes in "new stable" .

See ReleaseProposals for alternatives.