On 29 Jun 2006, at 14:59, Justin Erenkrantz wrote:
What I'd suggest is that we create a branch that has whatever API-busting change we want. What's the specific example of something that would force a 2.x? Neither errors nor IO abstraction should necessarily force 2.x.
+1 interesting developments like IO, and overdue rationalisation like errnums, can perfectly well be a 1.3, or 1.4, etc. Stability/back compatibility isa Good Thing. -- Nick Kew
