Re: Question about issue tracker

2018-01-01 Thread cowwoc

Done: https://github.com/apache/incubator-netbeans/pull/351

Gili

On 2017-12-31 4:49 PM, John McDonnell wrote:
You could, but for something this small, maybe we could convince you 
to join the effort :)  then there's no need to file a JIRA ticket, you 
could always fork the repo, make the change in your local repo and 
then submit a PR, explicitly pointing out why you think the change is 
needed.


All of this could be done quicker than a ticket, as it would probably 
be viewed as a low priority item ;)


Details are found here: 
https://cwiki.apache.org/confluence/display/NETBEANS/Development+Environment 
and 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408 
(still work in progress)


Regards

John

On 31 December 2017 at 21:44, cowwoc > wrote:


Hi John,

Thank you! Is it okay if I file a RFE asking for the download link
to get added to README.md?

Gili


On 2017-12-31 8:52 AM, John McDonnell wrote:

Hi Cowwoc,

At the moment NetBeans in migrating over to Apache, and in the
latter half of 2017, the first initial code drop took place
containing the NetBeans platform and the basic Java modules,
etc...  As a result the old codebase stored in Oracle, i.e.
https://netbeans.org/community/sources/
 is no longer applicable
for use since the more up to date changes are happening in the
code base found: https://github.com/apache/incubator-netbeans


This means the daily builds should be taken from here:

https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/




In relation to the exception reporter I believe there was some
discussion about this, but I cannot seem to find it on the
mailing lists, so maybe I'm imagining this.  But your right,
something will need to be done about this.


Please check out the new daily builds and please file any defects
against the JIRA link previously provided. - If there are any
high profile defects that might block you please report them as
soon as possible thanks.

John

On 31 December 2017 at 12:42, cowwoc > wrote:

Hi Geertjan,

I am getting the nightly builds from
http://bits.netbeans.org/download/trunk/nightly/latest/


Gili


On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:

Which nightly builds are you referring to specifically?

Can you provide a URL just to make sure we’re talking about
the same thing?

Gj

On Sunday, December 31, 2017, cowwoc
>
wrote:

Hi,

Are there any plans to open up (migrate) the issue
tracker for the broader apache community to tackle
existing/old Netbeans bugs?

I ask because I feel like the bandwidth for fixing Java
Editor bugs is like sucking a milkshake through a straw:
major bugs are being reported at an expoentially-growing
rate and they are being fixed at a rate of 1-2 a week.
The nightly builds are frankly barely usable anymore. I
am specifically concerned about Maven + Java projects
where I routinely get NullPointerExceptions and "slow
action" errors (actions taking 13-20 seconds to complete
on a seemingly random basis).

This component needs more love. And soon. Can you please
prioritize accordingly?

Thank you,
Gili

(For context, I've been using Netbeans since 1999 so
when I say things are unstable I've got a long
track-record to judge by)



-
To unsubscribe, e-mail:
users-unsubscr...@netbeans.apache.org

For additional commands, e-mail:
users-h...@netbeans.apache.org


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












Re: Question about issue tracker

2018-01-01 Thread Emilian Bold
See https://issues.apache.org/jira/browse/NETBEANS-164

--emi
​

> Original Message 
>Subject: Re: Question about issue tracker
>Local Time: 31 December 2017 3:52 PM
>UTC Time: 31 December 2017 13:52
>From: mcdonnell.j...@gmail.com
>To: cowwoc 
>users@netbeans.apache.org
>
>Hi Cowwoc,
>
>At the moment NetBeans in migrating over to Apache, and in the latter half of 
>2017, the first initial code drop took place containing the NetBeans platform 
>and the basic Java modules, etc...  As a result the old codebase stored in 
>Oracle, i.e. https://netbeans.org/community/sources/ is no longer applicable 
>for use since the more up to date changes are happening in the code base 
>found: https://github.com/apache/incubator-netbeans
>
>This means the daily builds should be taken from here: 
>https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/
>
>In relation to the exception reporter I believe there was some discussion 
>about this, but I cannot seem to find it on the mailing lists, so maybe I'm 
>imagining this.  But your right, something will need to be done about this.  
>
>
>Please check out the new daily builds and please file any defects against the 
>JIRA link previously provided. - If there are any high profile defects that 
>might block you please report them as soon as possible thanks.
>
>John
>
>On 31 December 2017 at 12:42, cowwoc  wrote:
>>Hi Geertjan,
>>
>> I am getting the nightly builds from 
>> http://bits.netbeans.org/download/trunk/nightly/latest/
>>
>> Gili
>>
>>
>>On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:
>>>Which
>>>  nightly builds are you referring to specifically? 
>>>
>>>Can you provide a URL just to make sure we’re talking about
>>>the same thing?
>>>
>>>
>>>Gj
>>>
>>> On Sunday, December 31, 2017, cowwoc 
>>>  wrote:
>>>
Hi,

 Are there any plans to open up (migrate) the issue tracker
for the broader apache community to tackle existing/old
Netbeans bugs?

 I ask because I feel like the bandwidth for fixing Java
Editor bugs is like sucking a milkshake through a straw:
major bugs are being reported at an expoentially-growing
rate and they are being fixed at a rate of 1-2 a week. The
nightly builds are frankly barely usable anymore. I am
specifically concerned about Maven + Java projects where I
routinely get NullPointerExceptions and "slow action" errors
(actions taking 13-20 seconds to complete on a seemingly
random basis).

 This component needs more love. And soon. Can you please
prioritize accordingly?

 Thank you,
 Gili

 (For context, I've been using Netbeans since 1999 so when I
say things are unstable I've got a long track-record to
judge by)


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

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


>>

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

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



RE: January 2018 Podling Report draft

2018-01-01 Thread constantin drabo
It is ok for me too !

Constantin

?? La Terre est le berceau de l'humanit??, mais on ne passe pas sa vie enti??re 
dans un berceau. ??
- ConstantinE. Tsiolkovski , p??re de l'astronautique?? et de 
l'a??rospatiale modernes.

De : Geertjan Wielenga 
Envoyé : dimanche 31 décembre 2017 02:03
À : us...@netbeans.incubator.apache.org
Objet : January 2018 Podling Report draft

Hi all,

Periodically (every 4 months after the first 3 months), podlings
(i.e., projects that are in the Apache incubator) need to provide a
status report.

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

Above is the report for January 2018, where we need to provide our
status, since it's 4 months since the last time we did this.

I have added a draft in there -- look for NetBeans in the above and
you'll find it.

Comments/additions/ideas/corrections, welcome.

Ideally, the report is something on which we can work together, i.e.,
it shouldn't be one person filling in the report, it should be a
community effort.

Thanks and happy new Apache NetBeans (incubating) year!

Gj

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

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