I do not recall releasing M milestone versions in the past. I know Eclipse uses milestones but the concept here feels more like an alpha or beta. You could call a -snapshot past a certain date or an RC a milestone I suppose. Can we just sync up pool and dbcp on their respective trunks?
I could see a string of RCs until dbcp is happy for example. Otho, this happiness could just be achieved on trunks... Gary On Apr 12, 2012, at 15:46, Mark Thomas <ma...@apache.org> wrote: > 1. Fix all the open bugs. DONE - until someone opens another Jira ;) > 2. Clean up the docs. TODO > 3. Release 2.0.0.M1 > 4. Work on DBCP2, updating POOL2 as required (e.g. moving the abandoned > object code to POOL2) > 5. React to feedback on 2.0.0.M1 > 6. Release 2.0.0.Mn as required > 7. Release 2.0.0 > > Thoughts? Comments? Feedback? > > The one issue I have is that I have no clue how the release process for > POOL works. I see the scripts Phil wrote but do not immediately see how > they'd work with the plan above (also note I know nothing about Maven). > Help appreciated. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
