On 07/07/11 03:42, Rob Lanphier wrote:
http://live.gnome.org/ThreePointOne <snip> having clear deadlines for proposing new features, deadlines for features being done or pulled, and other date-risk mitigation strategies.
Having a roadmap like Gnome is the way I am advocating.
Another way I could consider is having a stable branch and only merge in stable/reviewed patches. After each merge you can either: - hold for more patches - release on live site - tag a release (beta, RC...) This path is probably as predictable as the first one. Its drawback is that new features might have less attention.
Anyway, both ways are *very* far away from our wiki-way of handling /trunk/ (which is messy).