+1
Am 16. August 2019 17:55:31 MESZ schrieb Daniel Gruno :
>On 8/16/19 5:52 PM, Peter Kovacs wrote:
>> People will also if you have 10 000 open issues that are open because
>no one solved them.
>> If people write a good bug report then fine. If nobody can work with
>it, they should reopen it when
On 8/16/19 5:52 PM, Peter Kovacs wrote:
People will also if you have 10 000 open issues that are open because no one
solved them.
If people write a good bug report then fine. If nobody can work with it, they should reopen it when they are willed to
write more.
I think a LOT of this comes
People will also if you have 10 000 open issues that are open because no one
solved them.
If people write a good bug report then fine. If nobody can work with it, they
should reopen it when they are willed to write more.
My 2 cent
Am 16. August 2019 15:31:33 MESZ schrieb Scott Palmer :
>Please
Please NEVER close an issue that has not been verified as fixed or no-longer
relevant.
That is the #1 way to discourage participation. "I report the bug - nobody
fixed it , they just closed the issue without even considering it" … that’s a
crap way to do things.
By all means change the state
I think a stacktrace alone is also valuable, especially if you start
counting duplicates. The old error reporting infra used to aggregate such
duplicates.
People also won't answer the same day for a follow-up. Because they might
be busy. But also because they might have lost interest in that
Hi,
I agree with points made by Matthias.
Yesterday I tried to go through issues without assigned component and
assign at least PHP ones.
I found a lot of filed bugs containig only stack trace without any
specific steps leading to exception. Requests to provide more specific
information
Hi,
Am Montag, den 12.08.2019, 16:10 +0200 schrieb Geertjan Wielenga:
>
> There's understandable frustration by people reporting issues ( such as our
> issue filer hero Chris Lenz :-) ) about issues being filed and not being
> responded to.
>
this might sound rude, but at this time I would no
On Tue, 13 Aug 2019 at 15:05, Glenn Holmer wrote:
> I still think NetCAT should be in continuous operation, doing some of
> the things you suggest (like creating and updating specifications).
+1 for that idea.
Working out all the details of how NetCAT fits with the new release
schedule is still
On Mon, 12 Aug 2019 at 20:49, Laszlo Kishalmi wrote:
> Well tools JIRA vs GitHub could be a side discussion though as you might
> noticed, I'm mostly a JIRA guy.
The problem is more the level of UI complexity for the casual / end
user. It takes too long to work out how to find anything, or
On 8/12/19 9:10 AM, Geertjan Wielenga wrote:
> There's understandable frustration by people reporting issues ( such as our
> issue filer hero Chris Lenz :-) ) about issues being filed and not being
> responded to.
>
> Partly, I think that simply filing issues and then moving on, and then
> being
I think that GitHub discussions are mainly focus On things once they have been
submitted for acceptance and in the case of PR discussion are more like “code
review” type discussion
I think that JIRA Discussions were more discussions leading up to the
resolution of this issue and identifying
I want to fix the issue I have filed, but I have a time issue. In the
meantime I just thought I quickly fill what I know today.
On 12.08.19 21:48, Laszlo Kishalmi wrote:
> Well tools JIRA vs GitHub could be a side discussion though as you
> might noticed, I'm mostly a JIRA guy.
>
> I use the
is, that Github issues are not available for netbeans.
Cheers
Chris
Von: Emilian Bold
Gesendet: Montag, 12. August 2019 21:54
An: dev@netbeans.apache.org
Betreff: Re: Lots of issues reported, how to handle them?
BTW, Hacktoberfest is coming soon. Maybe make all that month all about
fixing JIRA
BTW, Hacktoberfest is coming soon. Maybe make all that month all about
fixing JIRA issues? (And tag/create easy issues on GitHub for people
that want to be part of Hacktoberfest?)
--emi
On Mon, Aug 12, 2019 at 10:49 PM Laszlo Kishalmi
wrote:
>
> Well tools JIRA vs GitHub could be a side
Well tools JIRA vs GitHub could be a side discussion though as you might
noticed, I'm mostly a JIRA guy.
I use the following dashboard:
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12332552
And from time to time, check the recent issues:
Maybe GitHub could be used to handle support request and jira could be used for
code issues.
What needs to be done is to handle the wrong issues to the right place. And
some exchange approach.
Am 12. August 2019 18:24:22 MESZ schrieb Geertjan Wielenga
:
>Let's stay focused on the topic of the
Often times the issue filler has no knowledge or time to actually fix
anything. In an ideal world they would provide patches but it's not
possible. (Not to mention I had a ton of patches grow stale in the
Oracle Bugzilla so even a patch doesn't do much actually).
Maybe we need a NetBUG program
Let's stay focused on the topic of the thread, feel free to start new
threads if you have some other topic to discuss.
The problem identified thus far is that we're discussing here, on GitHub,
and in JIRA.
That is suboptimal.
It is also difficult to know how to prioritize issues in this way.
On Mon, Aug 12, 2019 at 9:45 AM Neil C Smith wrote:
> On Mon, 12 Aug 2019 at 16:29, Jack Woehr wrote:
> > A friend of mine opines that NB has had its day and the Java world has
> > moved on to Eclipse mostly.
>
> Neither helpful, nor true! ;-)
>
> Neil
>
>
I certainly hope not, having been on
On Mon, 12 Aug 2019 at 15:11, Geertjan Wielenga wrote:
> How can we handle this situation?
>
> Maybe we can create tribes around certain areas and then have the tribes
> work together to respond to issues, create specifications, lead discussions
> on the mailing list, and implement the technical
On Mon, 12 Aug 2019 at 16:29, Jack Woehr wrote:
> A friend of mine opines that NB has had its day and the Java world has
> moved on to Eclipse mostly.
Neither helpful, nor true! ;-)
Neil
-
To unsubscribe, e-mail:
This sounds like a population density issue.
A friend of mine opines that NB has had its day and the Java world has
moved on to Eclipse mostly.
If one has a big open source project and not enough folks are hacking on
it, it starts to shrink.
That's sort of happening to OpenBSD.
On Mon, Aug 12,
Hi all,
There's understandable frustration by people reporting issues ( such as our
issue filer hero Chris Lenz :-) ) about issues being filed and not being
responded to.
Partly, I think that simply filing issues and then moving on, and then
being upset when no one picks up the issues, is
23 matches
Mail list logo
