I would suggest to identify then with BLOCKER severity.
-Jirka
Dne 2.11.2018 v 12:46 Geertjan Wielenga napsal(a):
Sure, fair enough, the problem though is how to identify them in the issue
tracker.
Gj
On Fri, Nov 2, 2018 at 12:33 PM Sasha Alexander Romanenko <[email protected]>
wrote:
That defeats purpose of issue tracker. This information needs to be readily
available on report or query, not dispersed emails.
пт, 2 нояб. 2018 г., 7:30 Geertjan Wielenga
[email protected]:
Maybe one way to approach this would be to ask everyone in NetCAT to
list 3
of the issues they filed that they'd prioritize for fixing over all
others,
regardless of whether they're blockers, i.e., simply 'my world would be a
good deal better if the following 3 were to be fixed', just add them as a
response in this thread.
Gj
On Fri, Nov 2, 2018 at 12:28 PM Alexander Romanenko <
[email protected]> wrote:
I was setting "affected version" to 10 for my issues - it looked like
that
was the label for this iteration of testing, so could maybe search by
that
too.
пт, 2 нояб. 2018 г. в 7:18, Geertjan Wielenga
<[email protected]>:
Well, I'd like to see all the issues that have been filed during the
NetCAT
program.
I'd also somehow like to see which ones really need to be fixed,
which
ones
can no longer be reproduced in 10-vc2 (maybe everyone in NetCAT can
check
whether all their issues can still be reproduced in NetCAT and then
add a
'NetCAT 10' label so we can collect then all), which ones need to be
prioritized, etc.
Gj
On Fri, Nov 2, 2018 at 9:28 AM Jiří Kovalský <
[email protected]
wrote:
Why do we need such filter?
-Jirka
Dne 2.11.2018 v 04:20 Leo Donahue napsal(a):
Good question, I was wondering if we should have been using
JIRA
labels
for NetCAT 9 and 10 issues. That would allow you to filter.
On Thu, Nov 1, 2018 at 5:10 AM Geertjan Wielenga
<[email protected]> wrote:
Is there a way to get a list of all the issues filed through the
NetCAT
program?
Gj
On Thu, Nov 1, 2018 at 9:36 AM <[email protected]> wrote:
Hello Jiri, hello Alexander,
here are my thoughts.
1. Tickets in strange state
The luxury of dedicated people paid by Sun/Oracle to pay
attention
to
bugs, develop features, respond to e-mails and the like are
gone.
With
the same argument statement "...the dev team cannot address
each
issue..." makes no sense because there is no dev team. The dev
team
is
you.
I am afraid I support Alexander here. I bet there are people
who
have
no
idea how to code using Java, yet still use NetBeans (e.g. PHP,
HTML,
C/C++).
Complaining about issues being ignored equals showing own
misunderstanding how open source software development works.
Good
news
is that you can filter the issues reported in October, trying
to
reproduce them one by one, adding your investigations and
setting
their
status and/or priorities correctly. When do you plan to do
that?
I also got impression (from what I have read on pages dedicated
to
the
process) that we should focus on testing only.
But, at the same time, I agree with you, Jiri. If there are no
dedicated
developers anymore (I mean, people who are actually paid for
developing
NetBeans), then, solving issues lays on volunteers and I won't
raise
this
kind of objections (not tackling the issues in Jira). Simply,
the
landscape
of NetBeans has changed and I need to adapt to it.
2. Tribe leaders are useless
I am afraid I disagree. True tribe leaders are precious asset
for
NetCAT. They simply act as managers, communicating with their
tribe
members, finding their strengths/weaknesses, then distributing
the
work
load, periodically checking the status/progress, reminding
about
incomplete tasks, triaging issues, escalating the most serious
ones
to
the NetCAT program coordinators, organizing meetups, etc. If
these
do
not exist, everything falls on plates of NetCAT program
coordinators
which are obviously overloaded which leaves NetCAT
participants
with
impression of chaos, ignorance or frustration.
OK, maybe it's still happening, maybe all these activities are
still
taking place, but, to be honest, I haven't seen that this time
that
much.
I remember older editions of NetCAT, with weekly reports
summarizing
activities, providing information to whole team, so it knew
where
it
was
standing at any, given, time. So, this time, I thought that
NetCAT
was
targeted more towards solo players who want to decide for
themselves
how
to
update docs, what to choose for testing, etc. Which, in fact,
suits
me
better :)
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
For further information about the NetBeans mailing lists,
visit:
https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Mailing-2Blists&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4&m=bav55yn4OB_qRWlPyg-3eJxbD1-VSSiM3rlfkRSmb04&s=F_nGJasZFETJzbaEQ5jlaHNRp9JVwzJm8vodU36w0M4&e=
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Mailing-2Blists&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4&m=OLXzSoP2kiRq-Dn69obkWr5NkRkOZUDIx6QFHxbtaWE&s=2tZUbz7_GDIGgaH0xgUYF19uodGj5PSUotAd-WpNpDc&e=
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
