[67cat] [news] Results from CA survey

[Jiri Kovalsky]

Hello NetCAT team,

   I am glad to announce that NetBeans 6.7 release received its Go! from community. We have closed the Community Acceptance survey and results [1] are already publicly available. 79% of 144 total respondents agree that NetBeans 6.7 RC2/RC3 builds are stable enough to become the official release. About ~10% of respondents who objected against releasing now selected 21 stopper candidates [2]. We evaluated all of them and fixed 3 critical bugs plus we plan to deliver 4 more issues in Patch 1 via NetBeans Update Center. In addition to that we are in touch with over 20 most critical respondents to clarify their feedback and assure that nothing gets overlooked.

[1] http://qa.netbeans.org/processes/cat/67/ca_results.html
[2] http://wiki.netbeans.org/NB67CABugsEvaluation

I would like to thank everybody who participated in this very important survey.

Have a nice day,
-Jirka

[Nigel Leck]

I wonder if there is a pattern to the people that were critical ? Could it be they are the ones with the largest code base ?

[Jiri Kovalsky]

Hi Nigel,

   as you know we didn't ask people for size and type of their projects but I think you are partially right. According to my investigations based on reading comments it seems like problematic are freeform projects with thousands classes and non-standard setup of dependencies. At least this is my humble opinion.

-Jirka

Nigel Leck wrote:

> I wonder if there is a pattern to the people that were critical ? Could it be
> they are the ones with the largest code base ?

[Goran E]

... and standard Grails projects.

I did nothing special to my grails projects other than adding a few
plugins. But NetBeans has always had trouble with them, more or less.
I zipped up and sent one of my three semi-large grails projects to the
NB developers a couple of days ago. Hope they can use it to track down
some issues. I'm prepared to send the other two if it's neccesary.

/Goran Ehrsson

Jiri Kovalsky wrote:

> Hi Nigel,
>
>   as you know we didn't ask people for size and type of their projects
> but I think you are partially right. According to my investigations
> based on reading comments it seems like problematic are freeform
> projects with thousands classes and non-standard setup of
> dependencies. At least this is my humble opinion.
>
> -Jirka
>
> Nigel Leck wrote:
>
>> I wonder if there is a pattern to the people that were critical ?
>> Could it be
>> they are the ones with the largest code base ?

[Jiri Kovalsky]

+1

Goran plus one other guy have these problems with Grails. And yes, we have the project and investigate it already.

Thanks a lot Goran!
-Jirka

Goran Ehrsson wrote:

> ... and standard Grails projects.
>
> I did nothing special to my grails projects other than adding a few
> plugins. But NetBeans has always had trouble with them, more or less.
> I zipped up and sent one of my three semi-large grails projects to the
> NB developers a couple of days ago. Hope they can use it to track down
> some issues. I'm prepared to send the other two if it's neccesary.
>
> /Goran Ehrsson
>
> Jiri Kovalsky wrote:
>> Hi Nigel,
>>
>>   as you know we didn't ask people for size and type of their projects
>> but I think you are partially right. According to my investigations
>> based on reading comments it seems like problematic are freeform
>> projects with thousands classes and non-standard setup of
>> dependencies. At least this is my humble opinion.
>>
>> -Jirka
>>
>> Nigel Leck wrote:
>>
>>> I wonder if there is a pattern to the people that were critical ?
>>> Could it be
>>> they are the ones with the largest code base ?

[Nigel Leck]

In our case we created a freeform project because we had to fit into an existing project structure. If NB isn't dominating by market share this is likely to always be the case.

Jiri Kovalsky wrote:

seems like problematic are freeform projects with thousands classes

[esmithbss]

+1

And Rails Code-Completion (Erno is already investigating).


Sincerely,

Eric M. Smith
Burning Sun Enterprises
http://typicalisoverrated.com
http://creativity.burningsunenterprises.com

On Jun 25, 2009, at 6:38 AM, Jiri Kovalsky <Jiri.Kovalsky@...>  
wrote:

> +1
>
> Goran plus one other guy have these problems with Grails. And yes,  
> we have the project and investigate it already.
>
> Thanks a lot Goran!
> -Jirka
>
> Goran Ehrsson wrote:
>
>> ... and standard Grails projects.
>> I did nothing special to my grails projects other than adding a few  
>> plugins. But NetBeans has always had trouble with them, more or less.
>> I zipped up and sent one of my three semi-large grails projects to  
>> the NB developers a couple of days ago. Hope they can use it to  
>> track down some issues. I'm prepared to send the other two if it's  
>> neccesary.
>> /Goran Ehrsson
>> Jiri Kovalsky wrote:
>>> Hi Nigel,
>>>
>>>  as you know we didn't ask people for size and type of their  
>>> projects but I think you are partially right. According to my  
>>> investigations based on reading comments it seems like problematic  
>>> are freeform projects with thousands classes and non-standard  
>>> setup of dependencies. At least this is my humble opinion.
>>>
>>> -Jirka
>>>
>>> Nigel Leck wrote:
>>>
>>>> I wonder if there is a pattern to the people that were critical ?  
>>>> Could it be
>>>> they are the ones with the largest code base ?

[Erno Mononen]

That particular code completion issue
(http://www.netbeans.org/issues/show_bug.cgi?id=167260) should be fixed
in the 6.7 clone now, it turned out to be a duplicate of
http://www.netbeans.org/issues/show_bug.cgi?id=167193.

Erno

Eric M. Smith wrote:

> +1
>
> And Rails Code-Completion (Erno is already investigating).
>
>
> Sincerely,
>
> Eric M. Smith
> Burning Sun Enterprises
> http://typicalisoverrated.com
> http://creativity.burningsunenterprises.com
>
> On Jun 25, 2009, at 6:38 AM, Jiri Kovalsky <Jiri.Kovalsky@...> wrote:
>
>> +1
>>
>> Goran plus one other guy have these problems with Grails. And yes, we
>> have the project and investigate it already.
>>
>> Thanks a lot Goran!
>> -Jirka
>>
>> Goran Ehrsson wrote:
>>
>>> ... and standard Grails projects.
>>> I did nothing special to my grails projects other than adding a few
>>> plugins. But NetBeans has always had trouble with them, more or less.
>>> I zipped up and sent one of my three semi-large grails projects to
>>> the NB developers a couple of days ago. Hope they can use it to
>>> track down some issues. I'm prepared to send the other two if it's
>>> neccesary.
>>> /Goran Ehrsson
>>> Jiri Kovalsky wrote:
>>>> Hi Nigel,
>>>>
>>>>  as you know we didn't ask people for size and type of their
>>>> projects but I think you are partially right. According to my
>>>> investigations based on reading comments it seems like problematic
>>>> are freeform projects with thousands classes and non-standard setup
>>>> of dependencies. At least this is my humble opinion.
>>>>
>>>> -Jirka
>>>>
>>>> Nigel Leck wrote:
>>>>
>>>>> I wonder if there is a pattern to the people that were critical ?
>>>>> Could it be
>>>>> they are the ones with the largest code base ?