On 11.11.21 16:08, Neil C Smith wrote:
On Thu, 11 Nov 2021 at 14:55, Eric Bresie <[email protected]> wrote:
- Issue templates
- Pull request template
- Repository admins accept content reports
-
Assume since Issues are not presently in use that probably explains the
Issue template, but do the other items need to be considered?
Interesting. Maybe. What does the last one mean exactly?!
In addition to the wiki page mentioned above, I do recommend just
having a look at how Airflow have their repository configured.
https://github.com/apache/airflow
They do have a simple PR template. The issues layout / forms are
great - try working through the Issues / New Issue process!
Neil
---------------------------------------------------------------------
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
I do like the github issue tracker since it appears to be simpler while
still doing its job. To keep an issue tracker useful, it does need
maintenance though. E.g many projects automatically close issues if they
are inactive for a certain amount of time. Having 32k open issues on
jira like NB has, is no longer observable.
Many "critical" issues i commented on asking if its still a problem were
in fact already fixed. This has to be automated, nobody should have to
do that manually. If the original poster cares about the issue and its
closed by mistake, believe me, it will be reopened.
i am for github issues, but someone would actually have to write the
templates, and then also try to automate things, otherwise it will be
jira 2.0 in a year or two.
-michael
---------------------------------------------------------------------
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
