Am 2017-01-09 um 19:58 schrieb Stephen Connolly:
If the commit mentions all the issues, e.g. [MNG-1235, MNG-4568] there
should be reasonable tracking... but if you feel more confident with one
issue per commit I see no issue with that either
Personally, yes. I have seen comments from users on issues where they
refer to a specific commit. Luckily, those were one issue per commit.
Made it pretty easy to analyze. I'd like to keep it that way.
Michael
On Mon 9 Jan 2017 at 18:51, Michael Osipov <micha...@apache.org> wrote:
Am 2017-01-09 um 16:13 schrieb Christian Schulte:
Hi,
there have been various issues in JIRA regarding the launcher scripts.
Is it possible to squash all those commits into one and then mention all
JIRA issues in the commit message so that the commit is added to each
JIRA issue? Last time I did this I think Jenkins was able to add
comments to all issues involved. I would just copy the launchers from
the pre-reset-master branch to master and just mention all issues in the
commit.
What about traceability for users? They would not be able to find the
distinct change for a ticket anymore. It makes it hard to trace a
regression.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Sent from my phone
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
