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 ana
Anyone know where the JIRA plugin is?
I believe its not migrated yet, so thought it might be part of the 8.2
update center but I cant see it.
Any idea where it is, or where the sources might be?
Regards
John
We could mirror issues to GitHub for Hacktoberfest. Where there's a
will there's a way.
--emi
On Mon, Aug 12, 2019 at 11:30 PM Christian Lenz wrote:
>
> I like the idea with the Mentors. Sometimes, when I want to fix an self
> created issue by my own, I don’t know whom to ask. And everytime ask
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 foll
I like the idea with the Mentors. Sometimes, when I want to fix an self created
issue by my own, I don’t know whom to ask. And everytime asking the whole
mailing list, seems not that great I thinl. My 2 cents.
Still what is missing for Hacktoberfest, that NetBeans will shown on the list
is, tha
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 discussi
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:
https://issues.apache.org/jira/se
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 sim
Done
On Mon, 12 Aug 2019 at 10:55, Geertjan Wielenga wrote:
> Hi all,
>
> In many ways, developer surveys are problematic and their results dubious,
> however it would be nice to see NetBeans better represented in some of them
> -- there's a new one that takes about 5 minutes to complete and is
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.
Ho
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 th
Chris, thank you for your reply!
I think I may be on to something. I've checked the project properties of
the NetBeans Build System and in Java Sources Classpath it had "JDK 12
(Default)" selected for Java Platform. I changed it to JDK 1.8 and the
build worked!
However doing so has changed n
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 s
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: dev-unsubscr..
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 subopti
Hi all,
In many ways, developer surveys are problematic and their results dubious,
however it would be nice to see NetBeans better represented in some of them
-- there's a new one that takes about 5 minutes to complete and is focused
on a number of recent developments in the Java ecosystem:
https
If you have the project open in NetBeans, right click on the root of the
project, go to Properties and in the tree ensure you have the correct JDK in
the Compile leaf and that the Sources match at least 1.7 but go for 1.8. You
should be able to build 11.x on anything >=8 but I would try just 8 w
19 matches
Mail list logo
