Re: NetCAT 10.0 evaluation

2018-10-30 Thread Geertjan Wielenga
>
> 4. Wasn't there a discussion about only 3 releases per calendar year?
> This would lower the rush and increase quality IMO.
>

I would not be opposed to that. The quarterly release proposal has not
formally been adopted, i.e., it's been proposed and we're going along with
it until we feel that maybe it's the wrong direction -- and three times a
year could be good too.

Gj


On Tue, Oct 30, 2018 at 6:49 PM Jiří Kovalský 
wrote:

> Hi Geertjan,
>
> nice post-mortem summary. My rough comments:
>
> 1. The proposal represents very minimalistic version of NetCAT, which
> however in the past used to be a platform with a defined start and end
> dates, where people gathered around particular features, distributed
> work, reviewed test specs for accuracy (updated old ones or created
> brand new ones) and then started testing daily builds, discussed their
> findings, filed issues, reviewed tutorials, participated in surveys.
> Activity of individual participants was tracked and evaluated at the end
> and best participants were rewarded for their activity and contribution
> and then everyone had time to catch up with other things/projects/life
> so from that point of view I can't predict if and how same people will
> keep contributing in the long term.
>
> 2. I agree we need to invite volunteers and immediately start finding
> tribe leaders and then utilize them. Not doing this for NetCAT 10.0 was
> a big mistake. Typically these should be the best performers from
> previous runs.
>
> 3. Identified blockers need constant attention. Testing stuff is only a
> step A. Step B (fixing bugs) is equally if not more important.
>
> 4. Wasn't there a discussion about only 3 releases per calendar year?
> This would lower the rush and increase quality IMO.
>
> -Jirka
>
> Dne 30.10.2018 v 11:55 Geertjan Wielenga napsal(a):
>
> > Hi all,
> >
> > For me, this was the first NetCAT process, we're trying to wrap it up now
> > and tomorrow -- so please do one or two more if you can find the time,
> just
> > send a mail and say which one you'd like to do -- and for me it was the
> > first time to take part at all.
> >
> > I have put some thoughts here:
> >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_NetCAT-2B10.0-2BEvaluation=DwIBaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4=7Z4USmmnTaTdZQ7-0HkIgLmqQzsU6L9ZN7bIwTrKC20=p5CkwD-PJ2NjKkjLpZM2x1zuLS_EkwtF-rOVETXwtfY=
> >
> > Others, feel free to add your thoughts and evaluations, or reply in this
> > thread with them, and thanks for your enthusiasm and great job, I think,
> > for how much we've done in so short a time.
> >
> > Gj
> >
>
> -
> To unsubscribe, e-mail: netcat-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: netcat-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>


Re: NetCAT 10.0 evaluation

2018-10-30 Thread Jiří Kovalský

Hi Geertjan,

nice post-mortem summary. My rough comments:

1. The proposal represents very minimalistic version of NetCAT, which 
however in the past used to be a platform with a defined start and end 
dates, where people gathered around particular features, distributed 
work, reviewed test specs for accuracy (updated old ones or created 
brand new ones) and then started testing daily builds, discussed their 
findings, filed issues, reviewed tutorials, participated in surveys. 
Activity of individual participants was tracked and evaluated at the end 
and best participants were rewarded for their activity and contribution 
and then everyone had time to catch up with other things/projects/life 
so from that point of view I can't predict if and how same people will 
keep contributing in the long term.


2. I agree we need to invite volunteers and immediately start finding 
tribe leaders and then utilize them. Not doing this for NetCAT 10.0 was 
a big mistake. Typically these should be the best performers from 
previous runs.


3. Identified blockers need constant attention. Testing stuff is only a 
step A. Step B (fixing bugs) is equally if not more important.


4. Wasn't there a discussion about only 3 releases per calendar year? 
This would lower the rush and increase quality IMO.


-Jirka

Dne 30.10.2018 v 11:55 Geertjan Wielenga napsal(a):


Hi all,

For me, this was the first NetCAT process, we're trying to wrap it up now
and tomorrow -- so please do one or two more if you can find the time, just
send a mail and say which one you'd like to do -- and for me it was the
first time to take part at all.

I have put some thoughts here:

https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_NetCAT-2B10.0-2BEvaluation=DwIBaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4=7Z4USmmnTaTdZQ7-0HkIgLmqQzsU6L9ZN7bIwTrKC20=p5CkwD-PJ2NjKkjLpZM2x1zuLS_EkwtF-rOVETXwtfY=

Others, feel free to add your thoughts and evaluations, or reply in this
thread with them, and thanks for your enthusiasm and great job, I think,
for how much we've done in so short a time.

Gj



-
To unsubscribe, e-mail: netcat-unsubscr...@netbeans.apache.org
For additional commands, e-mail: netcat-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



NetCAT 10.0 evaluation

2018-10-30 Thread Geertjan Wielenga
Hi all,

For me, this was the first NetCAT process, we're trying to wrap it up now
and tomorrow -- so please do one or two more if you can find the time, just
send a mail and say which one you'd like to do -- and for me it was the
first time to take part at all.

I have put some thoughts here:

https://cwiki.apache.org/confluence/display/NETBEANS/NetCAT+10.0+Evaluation

Others, feel free to add your thoughts and evaluations, or reply in this
thread with them, and thanks for your enthusiasm and great job, I think,
for how much we've done in so short a time.

Gj