Charlie Dobbie wrote:
[x] Apache Wicket 1.4 (Non-binding vote)
Having declared 2.0 a dead-end, you shouldn't release anything with
the same version number within six months at least - there's too much
potential for confusion IMHO. Not to mention tutorials and code
snippets that are floating around labelled "for Wicket 2.0". Yikes.
I have to agree with this, much as it may be a pain for the book. :-/
I'm inclined to adopt the full-on Apache versioning scheme, which means:
- Non-backwards compatible updates are x.0.0
- Backwards compatible updates are x.y.0
- Forwards/backwards interchangable patch versions are x.y.z
What about 3.0.0 with a move to this versioning scheme thereafter?
Regards,
Al
