Having gone through the migration from CVS to SVN and from our internal, rather onerous bug and change tracking system to Trac I suddenly find that we have lost the plot.
We started out attempting to improve our processes with a view to simplifying procedural requirements and reducing the load on engineers so that they could get more work done.
Now I find that the group driving these changes has become so focussed on the processes and procedure that considerations of minimising the procedural requirements while maximising their benefits has all but gone.
Essentially we got into a bike shed argument (which I started) and we all know that it is impossible to resolve those.
So here's the question:
If you enforce having a Trac ticket number in every commit and you do a lot of internal releases of your code should you open a single ticket and log all release commits to that ticket or should you have one Trac ticket per release? An acceptable answer is to allow both approaches.
What do you think?