Re: [SUMMARY] [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Tibor, Could you move this to its own thread. Let's keep this retrospective thread closed. It's done it's job Thanks in advance, - Stephen On Sun 19 Mar 2017 at 13:46, Tibor Digana wrote: > What marketing can we do in order to hire new developers? > In my experience

Re: [SUMMARY] [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

What marketing can we do in order to hire new developers? In my experience employees are still asking the same question "How much do they pay" ;-) I am still trying to explain that you are improving Maven used in your daily work. I do not want this great project to see dying. It's being widely

[SUMMARY] [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

On Sat 11 Mar 2017 at 21:56, Stephen Connolly < stephen.alan.conno...@gmail.com> 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

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

--first-parent On Wed 15 Mar 2017 at 00:39, Christian Schulte wrote: > Am 03/14/17 um 01:27 schrieb Jeff Jensen: > >> The date of the commit is not the date it got committed to master, but > the > > date it got committed to some branch, no longer existing after the > commit. >

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Am 03/14/17 um 01:27 schrieb Jeff Jensen: >> The date of the commit is not the date it got committed to master, but the > date it got committed to some branch, no longer existing after the commit. > If this is the way GIT works, so be it. I just don't like it. It could not > be more confusing. >

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Hi, On 11/03/17 22:56, Stephen Connolly 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 1. Using Jenkinsfile

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Hi Laird, On 13/03/17 23:22, Laird Nelson wrote: On Mon, Mar 13, 2017 at 2:26 PM Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: Gentle reminder. If you can see this thread, you are entitled to contribute. This thread is about discovering where the Maven project can improve how we

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

i really appreciate how smooth running about 20 of our inhouse projects with the alpha did went. Concerning git clients: - a really.nice CLI client is called tig, you should try it. Running tig --all is revealing most things you are used to from UI clients. All in all I found the discussions

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Thanks for the reminder. :-) Working well: 1. Strong release lead 2. CI in better shape 3. Good momentum (right now) Not working well: 1. Scope slipping. "Just one more small thing..." 2. Not a shared view on version meaning (e.g. what's a bug fix release?) 3. Hard to keep up on ML discussions

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

> The date of the commit is not the date it got committed to master, but the date it got committed to some branch, no longer existing after the commit. If this is the way GIT works, so be it. I just don't like it. It could not be more confusing. A couple of thoughts in case they help you. 1. Git

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Am 03/11/17 um 22:56 schrieb Stephen Connolly: > 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 The Jenkins

Contributing Javadoc (was Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1)

Am 03/13/17 um 23:22 schrieb Laird Nelson: > On Mon, Mar 13, 2017 at 2:26 PM Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > Gentle reminder. If you can see this thread, you are entitled to > contribute. This thread is about discovering where the Maven project can > improve how

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

On Mon, Mar 13, 2017 at 2:26 PM Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: Gentle reminder. If you can see this thread, you are entitled to contribute. This thread is about discovering where the Maven project can improve how we work in order to grow our community. I'll bite. (I

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

>>What is working well 1. Maven still continues developing new visions and milestones. 2. The discipline to start code review of a branch. 3. Jenkinsfile + automatically tested branches >>What is not working well 1. long discussions on ML. I would like to kindly ask you to prefer Pull Requests in

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

What is working well: 1. Despite the mess that resulted in the birth of 3.5.0, the project was set back on track successfully. 2. There is good feedback on the version, which sets up solid grounds for the future. 3. Not the only one for this point but... colorized logging is truly great!

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Gentle reminder. If you can see this thread, you are entitled to contribute. This thread is about discovering where the Maven project can improve how we work in order to grow our community. Everyone's opinions are welcome... We just ask that at this phase you just provide up to 3 sentences on

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

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

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Let's try ... * What is working well 1. Automations/Processes improvements with Jenkins 2. Many more interactions to get the release out (it revivified the dev community) 3. After so many years we have coloured logging !!! LOL * What is not working well 1. Our SCM notifications are really not

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

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

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Thanks Robert for seeding contributions . On Sun 12 Mar 2017 at 11:59, Robert Scholte wrote: > Let me kick off with my list: > > What is working well: > 1. It looks like we're going to have a new official Maven release soon. > 2. Some take their responsibility to start a

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Let me kick off with my list: What is working well: 1. It looks like we're going to have a new official Maven release soon. 2. Some take their responsibility to start a discussion. It is good to rate the impact of changes if we want to stay one of the worlds standards. 3. We're all

[DISCUSS] Retrospective on Maven 3.5.0-alpha-1

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