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
> 37c936d0ff778967dd4d9f68edfd60c3bea76e17 should be one commit because
> they are highly coupled.
yes, they are coupled, but I find it useful to keep 2 visible steps: using the 
new component is easy, renaming module to match the new naming is more complex

> 9d94541f7deaf784f3bc2157c1a3c149907538b8 should be merged seperately
> because it reflects two distinct changes of the dependency overview, not
> necessarily Resolver change.
it is separate: what to you want me to do? A separate branch? Isn't it too 
extreme?

> 
> > 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
> 
> Left come comments.
thanks, done (when agreeing, or discussing when not immediately agreeing :) )

> 
> In general, both branches are fine.
on MNG-5878, in addition to the review that you did (thank you), I need an 
explicit second to merge into 3.5.0, since this issue was not agreed yet (and 
I don't want to fool anybody)

Regards,

Hervé

> 
> > Le dimanche 22 janvier 2017, 10:22:26 CET Stephen Connolly a écrit :
> >> 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 we need to get this
> >> project into a rhythm.
> >> 
> >> -Stephen
> >> 
> >> P.S. Hervé if you don't have the time to release resolver this week I let
> >> me know and I'll pick it up
> > 
> > ---------------------------------------------------------------------
> > 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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to