my own topics: What is working well: 1. we're managing to do releases with confidence on what's inside 2. there are some discussions (even if not in an efficient way: IMHO, some changes should become proposals in the Wiki) 3. Jenkins hook to check branches (even if not perfect, it works sufficiently well and was absolutely necessary for our RTC workflow)
What is not working well: 1. git history is messed with "git merge" commits and originating branches: IMHO we should avoid it 2. commits@ is messed with rebase messages: hard to track really useful changes 3. I fear once 3.5.0 is out we're back to wild: the process to discuss new features, or even non-trivial changes, is not yet strong Thank you for animating the discussion: it's hard but useful Regards, Hervé Le samedi 11 mars 2017, 21:56:14 CET Stephen Connolly a écrit : > 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) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
