RE: NetBeans splash screen discussion on Twitter

[Joseph Jalbert]

Seems like a good candidate, only one I have seen recently.  
Colors look  a tad bit loud, but then it is supposed to be a "Splash" screen 
isn't it? 
Not at all a criticism: that would be when it is boring and flat colored.

-Original Message-
From: Geertjan Wielenga [mailto:geertjan.wiele...@googlemail.com] 
Sent: Tuesday, March 27, 2018 7:41 AM
To: dev@netbeans.incubator.apache.org
Subject: NetBeans splash screen discussion on Twitter

https://twitter.com/David_Schulz86/status/978297102525706241

Looks good, what do people think?

Gj



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

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

Re: Bugs potentially relating to nb-javac

[cowwoc]

I remember Netbeans used to produce file dumps for parsing errors and 
ask users to attach them to bug reports... What happened to that?


Having run into many such bugs in the past I usually can't share the 
full project because of its commercial nature, or I can't remember what 
I did to reproduce the problem.


In developer builds, it would be nice if Netbeans could remember what 
steps led to the bug occurring (Exception Reporter used to do this) and 
dump something minimal (not the entire project) so it could be attached 
to the bug report. Is this a realistic expectation or does something 
prevent us from doing this?


Gili

On 2018-03-28 8:48 PM, Eirik Bakke wrote:

Yes, good point, I will try to gather more information and add it to the
JIRAs as each of these bugs reappear. Each of these bugs are intermittent,
so I'm not quite sure how to reproduce them yet.

For a start, I added some sample class files to
https://issues.apache.org/jira/browse/NETBEANS-430 , which reappeared
today.

-- Eirik

On 3/28/18, 6:19 AM, "Jan Lahoda"  wrote:


Hi Eirik,

Thanks for reporting the bugs. One thing I'd like to point out is that
while it is sometimes possible for someone working on the code to fix a
bug
based just on a stacktrace, having a way to reproduce a problem usually
leads to much faster and efficient fix.

This is particularly true for (nb-)javac, where the problem often is that
something didn't happen even though it should have, and the observable
exception is only a consequence of that.

Jan


On Tue, Mar 27, 2018 at 5:19 PM, Eirik Bakke  wrote:


I've now used NetBeans 9.0 Beta for the six weeks since it was
released. I
found several bugs that are potentially related to the nb-javac plugin:

NETBEANS-455 "The
bytes do not represent a valid class" error while invoking the "Apply
Code
Changes" action
NETBEANS-454
AssertionError/"Wrong diagnostic handler ... DeferredDiagnosticHandler"
when opening Java autocomplete
NETBEANS-453
"Incorrect number of type arguments" exception during Java editing
NETBEANS-430
"Invalid
or deleted file", "Absent Code attribute" exceptions during Java editing
and app/test running
NETBEANS-531
"Duplicate method name in class" when running maven app with
CoS
enabled

Might any of these be related to the changes that were made to separate
out nb-javac from the Apache distribution? Or could it be a JDK9 thing?
Note that the Maven projects in question were all JDK8, while the IDE
was
running JDK9.

-- Eirik



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

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






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

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

Re: Exception reporting broken

[Eirik Bakke]

Could this be a case of someone importing java.sql.Date by accident when
only java.util.Date is needed? In JDK8 this would not cause an immediate
problem, but JDK9 might have moved the java.sql.* classes to a separate
now-inaccessible module.

On 3/28/18, 10:06 AM, "Antonio"  wrote:

>Mmmm java.sql.Date? That's weird.
>
>AFAIK JIRA uses a JSON REST API, so no sql is involved (I think).
>
>I wrote some instructions at [1] for setting up the JIRA plugin, but it
>threw some NullPointerExceptions while running... :-(
>
>
>[1]
>https://cwiki.apache.org/confluence/display/NETBEANS/Submitting+issues+in+
>JIRA
>
>On 28/03/18 13:50, Peter Nabbefeld wrote:
>> Thank You, Geertjan!
>> 
>> BTW, when trying to add Apache NetBeans Jira to Services/Task
>> Repositories, I get an exception ("java.lang.NoClassDefFoundError:
>> java.sql.Date"). Probably a JDK 9 issue.
>> 
>> Kind regards
>> Peter
>> 
>> 
>> Am 28.03.2018 um 13:18 schrieb Geertjan Wielenga:
>>> https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-491
>>>
>>> Gj
>>>
>>> On Wed, Mar 28, 2018 at 11:46 AM, Peter Nabbefeld
>>> 
>>> wrote:
>>>
 Hello,

 trying to submit an exception report leads me to
 http://statistics.netbeans.org/analytics/detail.do?id=232241

 As I'd expect JIRA on Apache web site should be used (and NetBeans
 BugZilla seems to be empty now), I'd see this as a broken (important)
 feature.

 My original problem is a regression with NB Hints system (using Java
 editor). Surely, the bug is already in JIRA database and I guess
You're
 working on it - where can I track progress?

 Kind regards
 Peter

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

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




>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>> 
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> 
>> 
>> 
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
>For further information about the NetBeans mailing lists, visit:
>https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>


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

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

Re: Bugs potentially relating to nb-javac

[Eirik Bakke]

Yes, good point, I will try to gather more information and add it to the
JIRAs as each of these bugs reappear. Each of these bugs are intermittent,
so I'm not quite sure how to reproduce them yet.

For a start, I added some sample class files to
https://issues.apache.org/jira/browse/NETBEANS-430 , which reappeared
today.

-- Eirik

On 3/28/18, 6:19 AM, "Jan Lahoda"  wrote:

>Hi Eirik,
>
>Thanks for reporting the bugs. One thing I'd like to point out is that
>while it is sometimes possible for someone working on the code to fix a
>bug
>based just on a stacktrace, having a way to reproduce a problem usually
>leads to much faster and efficient fix.
>
>This is particularly true for (nb-)javac, where the problem often is that
>something didn't happen even though it should have, and the observable
>exception is only a consequence of that.
>
>Jan
>
>
>On Tue, Mar 27, 2018 at 5:19 PM, Eirik Bakke  wrote:
>
>> I've now used NetBeans 9.0 Beta for the six weeks since it was
>>released. I
>> found several bugs that are potentially related to the nb-javac plugin:
>>
>> NETBEANS-455 "The
>> bytes do not represent a valid class" error while invoking the "Apply
>>Code
>> Changes" action
>> NETBEANS-454
>> AssertionError/"Wrong diagnostic handler ... DeferredDiagnosticHandler"
>> when opening Java autocomplete
>> NETBEANS-453
>> "Incorrect number of type arguments" exception during Java editing
>> NETBEANS-430
>>"Invalid
>> or deleted file", "Absent Code attribute" exceptions during Java editing
>> and app/test running
>> NETBEANS-531
>> "Duplicate method name in class" when running maven app with
>>CoS
>> enabled
>>
>> Might any of these be related to the changes that were made to separate
>> out nb-javac from the Apache distribution? Or could it be a JDK9 thing?
>> Note that the Maven projects in question were all JDK8, while the IDE
>>was
>> running JDK9.
>>
>> -- Eirik
>>


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

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

Re: Exception reporting broken

[Antonio]

Mmmm java.sql.Date? That's weird.

AFAIK JIRA uses a JSON REST API, so no sql is involved (I think).

I wrote some instructions at [1] for setting up the JIRA plugin, but it 
threw some NullPointerExceptions while running... :-(



[1]
https://cwiki.apache.org/confluence/display/NETBEANS/Submitting+issues+in+JIRA

On 28/03/18 13:50, Peter Nabbefeld wrote:

Thank You, Geertjan!

BTW, when trying to add Apache NetBeans Jira to Services/Task 
Repositories, I get an exception ("java.lang.NoClassDefFoundError: 
java.sql.Date"). Probably a JDK 9 issue.


Kind regards
Peter


Am 28.03.2018 um 13:18 schrieb Geertjan Wielenga:

https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-491

Gj

On Wed, Mar 28, 2018 at 11:46 AM, Peter Nabbefeld 


wrote:


Hello,

trying to submit an exception report leads me to
http://statistics.netbeans.org/analytics/detail.do?id=232241

As I'd expect JIRA on Apache web site should be used (and NetBeans
BugZilla seems to be empty now), I'd see this as a broken (important)
feature.

My original problem is a regression with NB Hints system (using Java
editor). Surely, the bug is already in JIRA database and I guess You're
working on it - where can I track progress?

Kind regards
Peter

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

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







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

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





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

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

Re: Exception reporting broken

[Peter Nabbefeld]

Thank You, Geertjan!

BTW, when trying to add Apache NetBeans Jira to Services/Task 
Repositories, I get an exception ("java.lang.NoClassDefFoundError: 
java.sql.Date"). Probably a JDK 9 issue.


Kind regards
Peter


Am 28.03.2018 um 13:18 schrieb Geertjan Wielenga:

https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-491

Gj

On Wed, Mar 28, 2018 at 11:46 AM, Peter Nabbefeld 
wrote:


Hello,

trying to submit an exception report leads me to
http://statistics.netbeans.org/analytics/detail.do?id=232241

As I'd expect JIRA on Apache web site should be used (and NetBeans
BugZilla seems to be empty now), I'd see this as a broken (important)
feature.

My original problem is a regression with NB Hints system (using Java
editor). Surely, the bug is already in JIRA database and I guess You're
working on it - where can I track progress?

Kind regards
Peter

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

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







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

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

Re: Exception reporting broken

[Geertjan Wielenga]

https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-491

Gj

On Wed, Mar 28, 2018 at 11:46 AM, Peter Nabbefeld 
wrote:

>
> Hello,
>
> trying to submit an exception report leads me to
> http://statistics.netbeans.org/analytics/detail.do?id=232241
>
> As I'd expect JIRA on Apache web site should be used (and NetBeans
> BugZilla seems to be empty now), I'd see this as a broken (important)
> feature.
>
> My original problem is a regression with NB Hints system (using Java
> editor). Surely, the bug is already in JIRA database and I guess You're
> working on it - where can I track progress?
>
> Kind regards
> Peter
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Podling Report Reminder - April 2018

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 April 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, April 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/April2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

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

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

Re: Bugs potentially relating to nb-javac

[Jan Lahoda]

Hi Eirik,

Thanks for reporting the bugs. One thing I'd like to point out is that
while it is sometimes possible for someone working on the code to fix a bug
based just on a stacktrace, having a way to reproduce a problem usually
leads to much faster and efficient fix.

This is particularly true for (nb-)javac, where the problem often is that
something didn't happen even though it should have, and the observable
exception is only a consequence of that.

Jan


On Tue, Mar 27, 2018 at 5:19 PM, Eirik Bakke  wrote:

> I've now used NetBeans 9.0 Beta for the six weeks since it was released. I
> found several bugs that are potentially related to the nb-javac plugin:
>
> NETBEANS-455 "The
> bytes do not represent a valid class" error while invoking the "Apply Code
> Changes" action
> NETBEANS-454
> AssertionError/"Wrong diagnostic handler ... DeferredDiagnosticHandler"
> when opening Java autocomplete
> NETBEANS-453
> "Incorrect number of type arguments" exception during Java editing
> NETBEANS-430 "Invalid
> or deleted file", "Absent Code attribute" exceptions during Java editing
> and app/test running
> NETBEANS-531
> "Duplicate method name in class" when running maven app with CoS
> enabled
>
> Might any of these be related to the changes that were made to separate
> out nb-javac from the Apache distribution? Or could it be a JDK9 thing?
> Note that the Maven projects in question were all JDK8, while the IDE was
> running JDK9.
>
> -- Eirik
>

Re: Help wanted with fixing NetBeans 9.0 blockers

[Neil C Smith]

On Tue, 27 Mar 2018 at 20:45 Antonio  wrote:

> In my case: Jira is very slow. Finding an issue is a pain in the neck.
>

Well, yes, there's that as well! :-)  But we need somewhere it all comes
together somehow - the old bugzilla had issues, patches and code reviews
tied together much better than we have now?

On Wed, 28 Mar 2018 at 08:24 Christian Lenz  wrote:

> I’m also for it, to sync Github with Jira, atm the bug section at Github
> for incubator-netbeans is hidden. I think there was a reason for that, but
> this is not that good, because as often as I said, not everyone is using
> JIRA and will use it. They see github and will try to add a ticket and they
> can’t.
>

I think this is an ASF requirement?  Or at least that a canonical list of
issues exists on the ASF side.  Seems like there are sync tools out there
though (eg. CoreOS has one)

Best wishes,

Neil

-- 
Neil C Smith
Artist & Technologist
www.neilcsmith.net

Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org

Exception reporting broken

[Peter Nabbefeld]

Hello,

trying to submit an exception report leads me to 
http://statistics.netbeans.org/analytics/detail.do?id=232241


As I'd expect JIRA on Apache web site should be used (and NetBeans 
BugZilla seems to be empty now), I'd see this as a broken (important) 
feature.


My original problem is a regression with NB Hints system (using Java 
editor). Surely, the bug is already in JIRA database and I guess You're 
working on it - where can I track progress?


Kind regards
Peter

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

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

AW: Help wanted with fixing NetBeans 9.0 blockers

[Christian Lenz]

I’m also for it, to sync Github with Jira, atm the bug section at Github for 
incubator-netbeans is hidden. I think there was a reason for that, but this is 
not that good, because as often as I said, not everyone is using JIRA and will 
use it. They see github and will try to add a ticket and they can’t.


Cheers

Chris

Von: Geertjan Wielenga
Gesendet: Mittwoch, 28. März 2018 08:12
An: dev@netbeans.incubator.apache.org
Betreff: Re: Help wanted with fixing NetBeans 9.0 blockers

Hi Gili,

I think you’ll find most people would rather fix issues and improve
NetBeans than respond to these kinds of e-mails — and all this
investigation you’ve done and so on: maybe it is better spent on
investigating or highlighting some specific issues? Would you prefer I
spend time responding to your e-mail, as well as the inevitable next one,
or would you prefer I fix issues and improve NetBeans instead?

Thanks,

Gj

On Wednesday, March 28, 2018, cowwoc  wrote:

> No need to get upset. I'm more than happy to walk back my numbers if the
> data backs it up.
>
> If you take a look at the link you shared (https://github.com/apache/inc
> ubator-netbeans-website/pulse/monthly) you will see that we had 13 merged
> PRs in 30 days and they are all infrastructure-related.
>
> If you take a look at https://github.com/apache/incu
> bator-netbeans/pulse/monthly you will see that we had 30 merged PRs of
> which 27 are legitimate fixes (not infrastructure-related).
>
> I will be the first to admit that I was wrong about an average of 1 fix
> per week when the reality is probably closer to 4 fixes per week (some
> fixes span multiple PRs). In my defence, here is are the two reports I've
> been looking at:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
> iew=220=NETBEANS=reporting=cumulativ
> eFlowDiagram=594=595=830&
> column=831=832=30
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?
> projectOrFilterId=project-12320634=daily&
> daysprevious=30=true=major&
> selectedProjectId=12320634=com.atlassian.jira.
> jira-core-reports-plugin%3Acreatedvsresolved-report
>
> The discussion of synchronizing JIRA and Github issue tracking is relevant
> because user-reported bugs only sit in JIRA. It's nice that people are
> fixing bugs regardless of whether or not they sit in JIRA, but again: users
> only report bugs to JIRA. If 50% of the bugs getting fixed do not come from
> JIRA it means that 50% of the development velocity is invisible to
> end-users. This also helps when discussing the prioritization of bug fixes.
>
> Gili
>
> On 2018-03-27 1:24 PM, Antonio wrote:
>
>> I fully agree with Matthias.
>>
>> In fact this has been a busy month:
>>
>> https://github.com/apache/incubator-netbeans-website/pulse/monthly
>> https://github.com/apache/incubator-netbeans-website-cleanup
>> /pulse/monthly
>> f
>> Cheers,
>> Antonio
>>
>> On 27/03/18 19:18, Matthias Bläsing wrote:
>>
>>> Hey,
>>>
>>> Am Dienstag, den 27.03.2018, 13:14 -0400 schrieb cowwoc:
>>>
 The number of resolved issues over the past 300 days is 0 :)

 In general, the pace of non-infrastructure bugs getting fixed is
 still
 very very slow (maybe 1 a week).

>>>
>>> this kind of talk it total unhelpful.
>>>
>>> Matthias
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Help wanted with fixing NetBeans 9.0 blockers

[Antonio]

On 28/03/18 04:26, cowwoc wrote:
No need to get upset. I'm more than happy to walk back my numbers if the 
data backs it up.


Who's upset? I was just stating that people is busy doing work here.

Whoever is not happy with the current pace of development (issue solving 
or any other aspect of Apache NetBeans) is always free to improve it.


Those are the benefits of an open source project!

Cheers,
Antonio

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

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

Re: Help wanted with fixing NetBeans 9.0 blockers

[Geertjan Wielenga]

Hi Gili,

I think you’ll find most people would rather fix issues and improve
NetBeans than respond to these kinds of e-mails — and all this
investigation you’ve done and so on: maybe it is better spent on
investigating or highlighting some specific issues? Would you prefer I
spend time responding to your e-mail, as well as the inevitable next one,
or would you prefer I fix issues and improve NetBeans instead?

Thanks,

Gj

On Wednesday, March 28, 2018, cowwoc  wrote:

> No need to get upset. I'm more than happy to walk back my numbers if the
> data backs it up.
>
> If you take a look at the link you shared (https://github.com/apache/inc
> ubator-netbeans-website/pulse/monthly) you will see that we had 13 merged
> PRs in 30 days and they are all infrastructure-related.
>
> If you take a look at https://github.com/apache/incu
> bator-netbeans/pulse/monthly you will see that we had 30 merged PRs of
> which 27 are legitimate fixes (not infrastructure-related).
>
> I will be the first to admit that I was wrong about an average of 1 fix
> per week when the reality is probably closer to 4 fixes per week (some
> fixes span multiple PRs). In my defence, here is are the two reports I've
> been looking at:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
> iew=220=NETBEANS=reporting=cumulativ
> eFlowDiagram=594=595=830&
> column=831=832=30
> https://issues.apache.org/jira/secure/ConfigureReport.jspa?
> projectOrFilterId=project-12320634=daily&
> daysprevious=30=true=major&
> selectedProjectId=12320634=com.atlassian.jira.
> jira-core-reports-plugin%3Acreatedvsresolved-report
>
> The discussion of synchronizing JIRA and Github issue tracking is relevant
> because user-reported bugs only sit in JIRA. It's nice that people are
> fixing bugs regardless of whether or not they sit in JIRA, but again: users
> only report bugs to JIRA. If 50% of the bugs getting fixed do not come from
> JIRA it means that 50% of the development velocity is invisible to
> end-users. This also helps when discussing the prioritization of bug fixes.
>
> Gili
>
> On 2018-03-27 1:24 PM, Antonio wrote:
>
>> I fully agree with Matthias.
>>
>> In fact this has been a busy month:
>>
>> https://github.com/apache/incubator-netbeans-website/pulse/monthly
>> https://github.com/apache/incubator-netbeans-website-cleanup
>> /pulse/monthly
>> f
>> Cheers,
>> Antonio
>>
>> On 27/03/18 19:18, Matthias Bläsing wrote:
>>
>>> Hey,
>>>
>>> Am Dienstag, den 27.03.2018, 13:14 -0400 schrieb cowwoc:
>>>
 The number of resolved issues over the past 300 days is 0 :)

 In general, the pace of non-infrastructure bugs getting fixed is
 still
 very very slow (maybe 1 a week).

>>>
>>> this kind of talk it total unhelpful.
>>>
>>> Matthias
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>