On Mon, 31 Jan 2022 at 09:49, Neil C Smith <[email protected]> wrote: > > On Mon, 31 Jan 2022 at 08:11, Geertjan Wielenga > <[email protected]> wrote: > > > > GitHub, please. > > > > We need to set Jira to readonly soon. > > Yes. I was going to look at website, etc. this week. We need to > update inbound links in a few places first. > > We probably want to remove the JIRA permission for users to create new > issues, but allow commenting and PMC issue creation to continue in the > short term. At least, given we're following Airflow's recommendations > on migration, that's what they currently have I think. We might have > to ask infra@ on that setup - not sure we have access to all required? > > See also https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-7120 > which we should do similar.
The website links are now updated, and people clicking through to report issues from the IDE should be flowing through to GitHub already. So, initially the consensus thread talked about a full switch on release of NB13. But should we bring that forward and request infra@ disable all new issue creation (for normal users anyway) now? I don't see anything in the JIRA permissions available to do what Airflow have here without infra@ help? Best wishes, 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
