Issue administration question

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Issue administration question


I'm wondering what is the best way to deal with issues which need to  
be resolved for multiple versions.

Example: This morning Jaco reported an error in the 0.3 release. This  
error affects both (unreleased), 0.3.1 and 0.4.

In the past I have done this the following way:
Jira: I have set fix for only for 0.3.1, to avoid that this issue  
appears in the release notes of the 0.4 release, as they will be  
mentioned already in the release notes of the 0.3.1 release.
Svn: I have first resolved the issue in the 0.3.1 release branch. The  
commit message for the release branch is something like: GRADLE-187  
unsupported operation when adding to project archive. Then I have  
merged the commit to trunk. As a commit message I use the merge  
statement: svn merge -r791:792 

Does this makes sense or would you anyone do it differently?

- Hans

Hans Dockter
Gradle Project lead

To unsubscribe from this list, please visit: