So what you mean is that the right thing to do is, if someone plans to
have something fixed/working for next-major is to *add* the next-major
fix version *without removing* the trunk label, right? Sounds correct.
Vincenzo
Noel J. Bergman wrote:
Jürgen Hoffmann wrote:
All he is doing is that he is tagging certain jira-issues,
that they are fixed in the next-major
Well, that is the thing. They may or may not be. What there ARE closed in
is trunk. I don't really care if they are listed against next-major, but
when we actually have code for next-major (remember: trunk is copied, then
PRUNED to become next-major), it may turn out that they are not resolved in
next-major at all.
All that I asked him to do was stop removing trunk as a label, since that IS
where the issue is resolved.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
