Hello,



Quick suggestion, I think it would help make things easier with the SVN trunk.



We currently have major releases; 0.5, 0.6 and 0.7


I would like to suggest incremental minor releases; for instance 0.6.1, 0.6.2, etc ... as stable deployments, and leaving the trunk as "unstable" instead of constantly hearing "svn is broken".

Perhaps starting off as branches in SVN for professional licenses?

I'm currently handling this methodology on my own box; always marking the revision as stable or unstable for roll backs, having it stored in SVN would be awesome, and easier for you to say "roll back to 0.6.2 to fix the problem".

Cheers,
Timothy