16 Sep
2006
16 Sep
'06
9:35 p.m.
Khalid B wrote:
Another problem is that we often don't know if the next release will be an x+1.0 or x.y+1, so we can't say "ported for 5.0" before Dries makes that decision. This is another case where code names for future releases will help.
That is probably the single best argument I've seen for code naming releases before they are released -- so we can refer to them easily and accurately in documentation of all kinds (project pages, CVS comments, postings, etc.).