Let's take things slower for everything after 3.5.0 The only one to put speed on is 3.5.0... and I even fear we are going too fast there
On Wed 1 Feb 2017 at 22:50, Christian Schulte <[email protected]> wrote: > Am 02/01/17 um 23:41 schrieb Stephen Connolly: > > On 1 February 2017 at 21:20, Christian Schulte <[email protected]> wrote: > > > >> Am 02/01/17 um 22:13 schrieb Stephen Connolly: > >>> 1.2.0 will not be in Maven 3.5.0 > >>> > >>> Let's get 3.5.0 out the door first > >> > >> Yes. That's why I updated the version in the poms to match the ranges > >> from the ITs. > > > > > > Please don't do that. > > > > We have a lot of stuff to merge, and limited build resources, could you > > just hold back (or better still delete) on any post 3.5.0 changes until > > after we get 3.5.0 finished, otherwise it is hard for people to know what > > to review. If you want to keep them ready, I recommend creating PRs on > > GitHub for them, we can then push the branches back to ASF after we get > > 3.5.0 out the door > > > > I can move all of this to Github. No problem. Are the branches ok that > way? Should I create a pull request per issue? How to handle commits > depending on each other (e.g. pull request #100 requires pull requests > #1 to #99 to already be merged)? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sent from my phone
