Hey all,

Like Anastasia said, a bunch of us met on Connect today to talk about the release process today.

She summarized the direction we are taking with the documentation. Here it is again in case you missed it:

http://fluidproject.org/pipermail/fluid-work/2009-February/003668.html

Other decisions we made today:

* Anyone in the community can be a release manager. For things that require commit access or special passwords, we'll pair you up with a committer who will help.

* We're going to go with a less onerous process for testing Fluid- all.js for Infusion 0.8, and as our new build system evolves we'll make sure it includes supports for making QA testing the release easier.

* We're going to stop testing the Infusion .war file directly. We're confident that the Maven process for building the .war won't introduce any new errors that aren't caught in the regular testing process.

* We won't test the non-minified source distribution directly, since it is identical to the repository version and will be covered through our regular process.

On another note, I'd like to thank Eli for agreeing to be the release manager for Infusion 0.8. He'll be working closely alongside Anastasia and Justin to make sure it's easy for everyone in the community to cut a release.

Comments, questions, ideas are always welcome.

Colin

---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org

_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to