The group has been very active in developing out services and demo apps, now that activity will be even more transparent by tracking the changes as they are submitted, prioritized, assigned, developed and tested.
The sourceforge tracker has rather obvious limitations (fixed workflow, no assigned tester field, on and on) but it's free. Any suggestions are appreciated.
This can also be used by the community to suggest new features, services or bugfixes.
To support this tracking, I'm recapping our development workflow below (which is available as a pretty graphic on the wiki):
- User Enter Feature/Bug with description (with or without use case)
- Admin Prioritize/Assign change
- Developer creates (or updates if use case exists) and posts use case, use case is reviewed
- Developer codes change in new branch with automated unit testing (JUnit, etc)
- Developer assigns change to tester (other than developer)
- Tester reviews code and either approves (go to #7) or notes required changes (go to #3)
- Developer committs change to trunk/release
- Admin closes Feature/Bug
Posts
No comments:
Post a Comment