Inline. > 1) Set the fix version for all a.b.c versions, where c > 0. > 2) For each major release line, set the lowest a.b.0 version. >
Sounds reasonable. > > The -alphaX versions we're using leading up to 3.0.0 GA can be treated as > a.b.c versions, with alpha1 being the a.b.0 release. > Once 3.0.0 GA goes out, a user would want to see the diff from the latest 2.x.0 release (say 2.9.0). Are you suggesting 3.0.0 GA would have c = 5 (say) and hence rule 1 would apply, and it should show up in the release notes? > > As an example, if a JIRA was committed to branch-2.6, branch-2.7, branch-2, > branch-3.0.0-alpha1, and trunk, it could have fix versions of 2.6.5, 2.7.3, > 2.8.0, 3.0.0-alpha1. The first two fix versions come from application of > rule 1, and the last two fix versions come from rule 2. > > I'm very eager to move this discussion forward, so feel free to reach out > on or off list if I can help with anything. > I think it is good practice to set multiple fix versions. However, it might take the committers a little bit to learn. Since the plan is to cut 3.0.0 off trunk, can we just bulk edit to add the 3.0.0-alphaX version? > > Best, > Andrew >
