Can we stage this logical set of changes on the same branch before merging to master (so we know we have a clean test run on the https://builds.apache.org/job/maven-jenkinsfile/ branch build)
On Mon 9 Jan 2017 at 21:41, Christian Schulte <c...@schulte.it> wrote: > Am 01/09/17 um 21:03 schrieb Michael Osipov: > > > 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. > > > > > > > I unassigned myself from those issues. You need to coordinate with Tibor > > to get things committed in order. It's multiple issues but the same > > files to change. You'll get conflicts if both of you start committing > > now without coordinating the changes. > > > > Regards, > > -- > > Christian > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- Sent from my phone
