Fwd: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira)
Because of spam users, the infra team plans to shutdown self registration of jira account and suggests ASF projects to make use of github issuesfor tracking customer facing questions/bugs. What should we do? -- Forwarded message - 发件人： fluxo Date: 2022年10月22日周六 09:02 Subject: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira) To: Hello PMC members, As I'm sure most of you are aware, the spam issues on Jira are getting worse. We are seeing spam user creation of over 10,000 accounts per year, and receive many requests per month from project members for help addressing spam complaints. Infra is taking steps to disable public Jira signups. Infra has developed a self-service tool by which folks on a PMC can request a Jira account for non-ASF contributors: https://selfserve.apache.org/ Click "Create a Jira user account" to go to: https://selfserve.apache.org/jira-acct.html You need to enter a username for the new Jira account. We will reject the request if there is an existing account with that username. If this person may ultimately become a committer, Infra recommends that they choose a username that they can also use for their LDAP username. Next, the tool asks you to enter their Display Name. This is the "public name" which will appear on all their Jira posts and comments. Last, the tool asks you to enter the user's email address. We expect the PMC to exercise due diligence in making sure the contributor's email works. If it does not, they will not get the password reset mail. Infra knows this process change places an increasing burden on PMC members for managing contributors, and makes it harder for people to contribute bug reports. We suggest projects consider using GitHub Issues for customer-facing questions/bug reports/etc., while maintaining development issues on Jira. You can enable GitHub Issues for your repository via https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Repositoryfeatures Infra has targeted 6 November for the date we switch off public signups for issues.apache.org/jira . Please let us know if this will place any significant burden on your teams. We are following an aggressive timeline because of the serious impact spam users have on the safety and stability of our infrastructure. As always, if you have any questions or comments about this, please let us know! -Chris (fluxo) -- @fluxo Chris Lambertus ASF Infrastructure
Re: [VOTE] The second release candidate for HBase 2.5.1 (RC1) is available
+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_292): ok - mvn clean apache-rat:check -D skipTests * Built from source (1.8.0_292): ok - mvn clean install -D skipTests -DskipTests * Built from source (11.0.11): ok - mvn clean install -D skipTests -D hadoop.profile=3.0 -DskipTests * Reviewed API Compatibility summary: ok * Reviewed nightly Jenkins: ok * Compiled tag vs Hadoop 3.3.4, launched pseudo-distributed cluster, ltt -write 7:100:5 -num_keys 10, ltt -read 100:10 -num_keys 10: ok On Tue, Oct 18, 2022 at 2:47 AM Andrew Purtell wrote: > > Please vote on this Apache HBase release candidate, hbase-2.5.1RC0. > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache HBase 2.5.1 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 2.5.1RC1: > > https://github.com/apache/hbase/tree/2.5.1RC1 > > This tag currently points to git reference 894ac15342. > > The release files, including signatures, digests, as well as CHANGES.md > and RELEASENOTES.md included in this RC can be found at: > > https://dist.apache.org/repos/dist/dev/hbase/2.5.1RC1/ > > The compatibility report can be found here: > > > https://dist.apache.org/repos/dist/dev/hbase/2.5.1RC1/api_compare_2.5.0_to_2.5.1RC1.html > > All changes are in line with our compatibility guidelines, except one > change where we intentionally removed a constant field in a public > interface. The change was required to resolve deadlocks during static > initialization under certain conditions. Refer to HBASE-27381 for more > details. > > Maven artifacts are available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachehbase-1499/ > > Artifacts were signed with the 0xD5365CCD key which can be found in: > > https://downloads.apache.org/hbase/KEYS > > To learn more about Apache HBase, please see > > http://hbase.apache.org/ > > Thanks, > Your HBase Release Manager
Re: [VOTE] The second release candidate for HBase 2.5.1 (RC1) is available
> Checked logs and web page, the region visualizer showed two pictures, which > was a bit strange but not a blocker I believe(or maybe it is by design?) Yes, this is by design. The lower bar is selectable -- the user can reduce the range of hosts displayed by click-and-drag horizontally on that bar. I found it useful when using the visualizer on a cluster with several hundreds of hosts. It may not be relevant in other deployment scenarios. UX improvements welcome :) On Tue, Oct 18, 2022 at 12:58 PM 张铎(Duo Zhang) wrote: > > +1 binding > > Checked sigs and sums: Matched > Rat check: Passed > Built from source: Succeeded with 8u292 > Run UTs: > Run 'mvn test -PrunAllTests -Dsurefire.rerunFailingTestsCount=3 > -Dsurefire.firstPartForkCount=0.5C -Dsurefire.secondPartForkCount=0.5C > -fn &>test.logPassed with 8u292, good. > Started a mini cluster: > Checked logs and web page, the region visualizer showed two > pictures, which was a bit strange but not a blocker I believe(or maybe > it is by design?) > Tried basic shell commands, no problem > Run LTT to load 1 rows, and use scan and count in shell, can > return all the 1 rows without error > > Thanks. > Andrew Purtell 于2022年10月18日周二 08:47写道： > > > > > > Please vote on this Apache HBase release candidate, hbase-2.5.1RC0. > > > > The VOTE will remain open for at least 72 hours. > > > > [ ] +1 Release this package as Apache HBase 2.5.1 > > [ ] -1 Do not release this package because ... > > > > The tag to be voted on is 2.5.1RC1: > > > > https://github.com/apache/hbase/tree/2.5.1RC1 > > > > This tag currently points to git reference 894ac15342. > > > > The release files, including signatures, digests, as well as CHANGES.md > > and RELEASENOTES.md included in this RC can be found at: > > > > https://dist.apache.org/repos/dist/dev/hbase/2.5.1RC1/ > > > > The compatibility report can be found here: > > > > > > https://dist.apache.org/repos/dist/dev/hbase/2.5.1RC1/api_compare_2.5.0_to_2.5.1RC1.html > > > > All changes are in line with our compatibility guidelines, except one > > change where we intentionally removed a constant field in a public > > interface. The change was required to resolve deadlocks during static > > initialization under certain conditions. Refer to HBASE-27381 for more > > details. > > > > Maven artifacts are available in a staging repository at: > > > > https://repository.apache.org/content/repositories/orgapachehbase-1499/ > > > > Artifacts were signed with the 0xD5365CCD key which can be found in: > > > > https://downloads.apache.org/hbase/KEYS > > > > To learn more about Apache HBase, please see > > > > http://hbase.apache.org/ > > > > Thanks, > > Your HBase Release Manager
