OK so I can sign you up for the stable team?  ;)  As per my previous email i'm 100% sure we would do a stable release if we had people tending to issues.  The only problem is you would have to be on IRC tending to issues because if tony sees someone asking about a problem he'll be diving in to fix it before they can say "I have this one".  This also means working in a similar manner we do already.  Our process is very chaotic at times but it has served us well so far.  

The goal is to leave Anthony alone so he can move forward and let the stable team manage the jira's and issues on the list related to stable.

/b

On Feb 18, 2010, at 10:10 PM, David Knell wrote:


Lon Baker <lon@kickasspixels.com> wrote:

The development branch is where feature requests and non-critical bugs
reports would be filed for the next production release.

The current process leaves a gap between production ready and
development code that may become greater over time.

Going against the grain here, I agree with you.  The current way of
doing things is, in my opinion, not well thought through - there's no
reason to tag and release versions if the answer to any issue is 'make
current', and support is not available unless that's been done.  Far
better to either have meaningful releases with stable and devel
branches, or not to have releases at all.

--Dave