Here's my list: Working well:
1. Jenkinsfile and multibranch 2. Actually discussing changes before merging 3. We got a release at last with coloured logging Needs improvement: 1. I was not happy at all with the chaos in trying to plan out the scope of 3.5.0 2. Very difficult to determine which branches are in-flight for 3.5.0 vs future versions and who owns the branches, esp when looking from Jenkins 3. Seems to have been an excessive amount of (seemingly needless) rebasing of branches, with an impact on our capacity to review commits On Sat 11 Mar 2017 at 21:56, Stephen Connolly < [email protected]> wrote: > Hi all, > > I think it is a good thing if we take stock of where we are and how we are > doing. I would really appreciate if everyone could take a few minutes to > respond with their top three of two areas: > > * What is working well > > * What is not working well > > I'll consolidate the responses after 72h and see if there are any themes > that can be identified > > On the stuff that is not working well, I'll try and pick the three most > popular themes, we can then have a round of discussion on those three > themes to see if anyone has any ideas to improve those aspects of how we > work and hopefully we can have some votes to change things for the better. > > By the way, this is open to anyone in any way what so ever involved with > the Maven 3.5.0-alpha-1 effort (assuming you are paying attention to the > dev list ;-) ) > > Thanks in advance for your time, > > -Stephen > > P.S. As alpha-2 is near, I'll probably wait until after 3.5.0 before I try > this again (assuming people like this idea) > -- Sent from my phone
