Hi,
here - hence its being used in production. so many fixes I wonder sometimes how we got away with 2.0.5
Ouch.
;-) I hope you didnt take that the wrong way - I was impressed with 2.0.5 - but 2.1.1 is a great piece of work and I would recommend people to give it a go. certainly we cannot find any issues without enough users :-)
OK. Git seems to be working well, so I think we can create a "stable" branch in git that's 2.1.1, plus any fixes that have gone in since then.
..so this would evolve into 2.1.2 etc at perticular times...
The rest of the changes (i.e. moving socket code to plug-in modules) can go into a "2.2" branch.
..the bleeding edge. makes sense
This should hopefully minimize any issues with finding bugs at the last minute, or after the release has been made.
its those pesky little niggly things that crop after after the release - they've been lurking around each release for a while now. could almost guarantee that the second 2.0.x or 2.1.x was released on the web server, there'd be a little quirk or thing wrong that was so facile or trivial. anyway, enough eyes on the release candidates and we'll be sorted :-) alan