Re: [DISCUSS] How to deal with the disabling of public sign ups for jira.a.o(enable github issues?)

2022-12-01 Thread Duo Zhang
Currently all the comment on github PR will be sent to issues@hbase, like this one https://lists.apache.org/thread/jbfm269b4m24xl2r82l8b0t3pmqr44hr But I think this can only be used as an archive, to make sure that all discussions are recorded on asf infrastructure. For github issues, I'm

Re: [DISCUSS] How to deal with the disabling of public sign ups for jira.a.o(enable github issues?)

2022-12-01 Thread Bryan Beaudreault
Should we have them sent to private@? Just thinking in terms of reducing spam to users who put their email and full name on a public list. One thought I had about bug tracking is whether we could use some sort of github -> jira sync. I've seen them used before, where it automatically syncs issues

Re: [DISCUSS] How to deal with the disabling of public sign ups for jira.a.o(enable github issues?)

2022-12-01 Thread Duo Zhang
I've filed HBASE-27513 for changing the readme on github. At least let's reuse the existing mailing list for acquiring jira account. Thanks. 张铎(Duo Zhang) 于2022年11月29日周二 22:34写道: > > Bump and also send this to user@hbase. > > We need to find a way to deal with the current situation where >