Looking for trac workflow ideas. Since we’re moving to a feature based development, how should we manage tickets and milestones?
Current problems:
- 3.3 milestone has a lot of tickets related to notifications and visual editor
- Trac has no bulk ticket management, so it’s a pain to move them one by one every time a feature is pushed back
- Once a version is released, it’s nice to have every ticket fixed in the right milestone as reference for changes in that version
In summary, considering that 3.3 is going to be Sounds + bugfixes, I’m having a hard time figuring out what’s important by looking at http://ios.trac.wordpress.org/query?status=assigned&status=new&status=accepted&status=reopened&group=status&milestone=3.3
How do we manage this better for future releases/features?
