Re: Progress check for 3.5.0

On Tue 31 Jan 2017 at 19:29, Michael Osipov wrote: > Am 2017-01-22 um 11:22 schrieb Stephen Connolly: > > I'm currently waiting on Hervé to start the 1.0.3 release of resolver. > > > > Once we get that I'm going to start cutting RCs (I plan 2 a week apart) > > > > Once we

Re: Progress check for 3.5.0

Am 2017-01-22 um 11:22 schrieb Stephen Connolly: I'm currently waiting on Hervé to start the 1.0.3 release of resolver. Once we get that I'm going to start cutting RCs (I plan 2 a week apart) Once we have a stable RC I will cut the release, and start a clock towards 3.5.1 (6 weeks approx)

Re: Progress check for 3.5.0

Am 2017-01-31 um 03:37 schrieb Hervé BOUTEMY: Le dimanche 29 janvier 2017, 22:11:16 CET Michael Osipov a écrit : Am 2017-01-29 um 20:47 schrieb Hervé BOUTEMY: resolver integration is ready in MNG-6110 branch: please review I'll merge in 48h I believe that

Re: Progress check for 3.5.0

Le dimanche 29 janvier 2017, 22:11:16 CET Michael Osipov a écrit : > Am 2017-01-29 um 20:47 schrieb Hervé BOUTEMY: > > resolver integration is ready in MNG-6110 branch: please review > > I'll merge in 48h > > I believe that bfc35976e2883bb922ef6e1787917a28215532b7 and >

Re: Progress check for 3.5.0

Am 2017-01-29 um 20:47 schrieb Hervé BOUTEMY: resolver integration is ready in MNG-6110 branch: please review I'll merge in 48h I believe that bfc35976e2883bb922ef6e1787917a28215532b7 and 37c936d0ff778967dd4d9f68edfd60c3bea76e17 should be one commit because they are highly coupled.

Re: Progress check for 3.5.0

resolver integration is ready in MNG-6110 branch: please review I'll merge in 48h I prepared MNG-5878 branch for "add support for module name != artifactId in every calculated URLs (project, SCM, site): special project.directory property" I'd like to have seconds to merge that branch into 3.5.0

Re: Progress check for 3.5.0

Am 2017-01-25 um 22:08 schrieb Christian Schulte: Am 01/25/17 um 20:53 schrieb Michael Osipov: Am 2017-01-22 um 13:58 schrieb Michael Osipov: Am 2017-01-22 um 11:22 schrieb Stephen Connolly: I'm currently waiting on Hervé to start the 1.0.3 release of resolver. Once we get that I'm going to

Re: Progress check for 3.5.0

Am 01/25/17 um 20:53 schrieb Michael Osipov: > Am 2017-01-22 um 13:58 schrieb Michael Osipov: >> Am 2017-01-22 um 11:22 schrieb Stephen Connolly: >>> I'm currently waiting on Hervé to start the 1.0.3 release of resolver. >>> >>> Once we get that I'm going to start cutting RCs (I plan 2 a week

Re: Progress check for 3.5.0

Hi, I think the MNG-5567 should be moved to 3.5.1 as Stephen suggested but the rest could be part of 3.5.0... Kind regards Karl Heinz On 25/01/17 21:11, Michael Osipov wrote: Am 2017-01-25 um 20:57 schrieb Stephen Connolly: 5567 affects classpaths so I would prefer to keep it for 3.5.1 as

Re: Progress check for 3.5.0

Am 2017-01-25 um 20:57 schrieb Stephen Connolly: 5567 affects classpaths so I would prefer to keep it for 3.5.1 as that way it is separate from the resolver change So, FIX-3.5.1? What about the rest, any opinion? On Wed 25 Jan 2017 at 19:54, Michael Osipov wrote: Am

Re: Progress check for 3.5.0

5567 affects classpaths so I would prefer to keep it for 3.5.1 as that way it is separate from the resolver change On Wed 25 Jan 2017 at 19:54, Michael Osipov wrote: > Am 2017-01-22 um 13:58 schrieb Michael Osipov: > > Am 2017-01-22 um 11:22 schrieb Stephen Connolly: > >>

Re: Progress check for 3.5.0

Am 2017-01-22 um 13:58 schrieb Michael Osipov: Am 2017-01-22 um 11:22 schrieb Stephen Connolly: I'm currently waiting on Hervé to start the 1.0.3 release of resolver. Once we get that I'm going to start cutting RCs (I plan 2 a week apart) Once we have a stable RC I will cut the release, and

Re: Progress check for 3.5.0

Am 2017-01-22 um 22:36 schrieb Christian Schulte: [..] , MNG-6112, MNG-6113 are FIX-3.5.0 for me. FIX-3.5.0 They are so simple, they do not even require a branch and can be cherry picked to master right now. I fully agree here. @Stephen, you have expressed some concerned about these issues

Re: Progress check for 3.5.0

Go for it On Sun 22 Jan 2017 at 22:14, Michael Osipov wrote: > Am 2017-01-22 um 21:18 schrieb Michael Osipov: > > > Am 2017-01-22 um 17:35 schrieb Christian Schulte: > > >> Am 22.01.2017 um 13:58 schrieb Michael Osipov: > > >>> [..] > > >>> MNG-5837 Syntax error in bin/mvn

Re: Progress check for 3.5.0

Am 2017-01-22 um 21:18 schrieb Michael Osipov: Am 2017-01-22 um 17:35 schrieb Christian Schulte: Am 22.01.2017 um 13:58 schrieb Michael Osipov: [..] MNG-5837 Syntax error in bin/mvn on Solaris SPARC FIX-3.5.0 This is a trivial fix but to be more precise, it has to be split it two separate

Re: Progress check for 3.5.0

Am 01/22/17 um 21:18 schrieb Michael Osipov: > Am 2017-01-22 um 17:35 schrieb Christian Schulte: >> Am 22.01.2017 um 13:58 schrieb Michael Osipov: >>> [..] >>> MNG-5837 Syntax error in bin/mvn on Solaris SPARC >> >> FIX-3.5.0 > > This is a trivial fix but to be more precise, it has to be split it

Re: Progress check for 3.5.0

Am 01/22/17 um 22:20 schrieb Stephen Connolly: > Please just name each branch by the issue it is using > > Naming branches MNG-xxx+MNG-yyy is not necessary > > We can see in the history that it's On top and the names will get > ridiculous as you add more That's why I stopped creating even more

Re: Progress check for 3.5.0

Please just name each branch by the issue it is using Naming branches MNG-xxx+MNG-yyy is not necessary We can see in the history that it's On top and the names will get ridiculous as you add more On Sun 22 Jan 2017 at 21:12, Christian Schulte wrote: > Am 01/22/17 um 20:15

Re: Progress check for 3.5.0

Am 01/22/17 um 20:15 schrieb Stephen Connolly: > If you want to stack your branches in order that's fine and would save > rebasing. > > Just start with the first and push that as first issue's branch, then > continue with second issue on top of first, etc. > > We'll see from the branch history

Re: Progress check for 3.5.0

Am 2017-01-22 um 17:35 schrieb Christian Schulte: Am 22.01.2017 um 13:58 schrieb Michael Osipov: [..] MNG-5837 Syntax error in bin/mvn on Solaris SPARC FIX-3.5.0 This is a trivial fix but to be more precise, it has to be split it two separate issues: 1. local issue: naive Linux user

Re: Progress check for 3.5.0

If you want to stack your branches in order that's fine and would save rebasing. Just start with the first and push that as first issue's branch, then continue with second issue on top of first, etc. We'll see from the branch history and if something breaks along the way we can identify it

Re: Progress check for 3.5.0

Am 22.01.2017 um 18:14 schrieb Stephen Connolly: > Why are you needing to rebase constantly? > > Unless the merge has conflicts you should be fine pushing to master post > merge... if there is a test failure post merge (due to an unanticipated > interaction) we can just add the fix on top If

Re: Progress check for 3.5.0

Why are you needing to rebase constantly? Unless the merge has conflicts you should be fine pushing to master post merge... if there is a test failure post merge (due to an unanticipated interaction) we can just add the fix on top On Sun 22 Jan 2017 at 16:36, Christian Schulte

Re: Progress check for 3.5.0

Am 22.01.2017 um 13:58 schrieb Michael Osipov: > Am 2017-01-22 um 11:22 schrieb Stephen Connolly: >> I'm currently waiting on Hervé to start the 1.0.3 release of resolver. >> >> Once we get that I'm going to start cutting RCs (I plan 2 a week apart) >> >> Once we have a stable RC I will cut the

Re: Progress check for 3.5.0

If you have a clean build, it is on the agreed list and you are not changing integration tests, merge away. If you have any doubt or concerns, raise them on the list and give it 72h. Merge if nobody comments in 72h On Sun 22 Jan 2017 at 12:58, Michael Osipov wrote: > Am

Re: Progress check for 3.5.0

Am 2017-01-22 um 11:22 schrieb Stephen Connolly: I'm currently waiting on Hervé to start the 1.0.3 release of resolver. Once we get that I'm going to start cutting RCs (I plan 2 a week apart) Once we have a stable RC I will cut the release, and start a clock towards 3.5.1 (6 weeks approx) If

Re: Progress check for 3.5.0

Am 2017-01-22 um 11:22 schrieb Stephen Connolly: I'm currently waiting on Hervé to start the 1.0.3 release of resolver. Once we get that I'm going to start cutting RCs (I plan 2 a week apart) Once we have a stable RC I will cut the release, and start a clock towards 3.5.1 (6 weeks approx) If

Progress check for 3.5.0

I'm currently waiting on Hervé to start the 1.0.3 release of resolver. Once we get that I'm going to start cutting RCs (I plan 2 a week apart) Once we have a stable RC I will cut the release, and start a clock towards 3.5.1 (6 weeks approx) If you miss the boat, you can catch the next one, but