Update: The patch is now in all repos except hbase-site. As always, speak up if you see something odd.
I plan to commit the hbase-site patch over the coming weekend so that I have some time to fix/revert changes if something goes wrong (will put it up for review before then). Let me know if anyone disagrees with the timing or the approach. On Tue, May 5, 2020 at 9:24 AM Bharath Vissapragada <bhara...@apache.org> wrote: > Yes, Peter. We need to do the same for other repos. The problem here is > that (IIUC), there is no way to know whether a particular change works > without actually committing it to the repo. So, there is a chance that > things could go wrong. So far it looks like it is working, so I'll make the > github/jira configs for other repos today. > > Will do hbase-site last, as the configs seem a little tricky and we could > easily take the site down if we misconfigure something. > > On Tue, May 5, 2020 at 8:38 AM Sean Busbey <sean.bus...@gmail.com> wrote: > >> I believe Bharath's plan is to check out how things go on the main repo >> and >> then roll out to the others. >> >> On Tue, May 5, 2020 at 10:06 AM Peter Somogyi <psomo...@apache.org> >> wrote: >> >> > That's great! >> > Do we need to do the same for the other repositories? >> > >> > >> > On Tue, May 5, 2020 at 12:03 AM Stack <st...@duboce.net> wrote: >> > >> > > Good stuff Bharath, >> > > S >> > > >> > > On Mon, May 4, 2020 at 12:48 PM Bharath Vissapragada < >> > bhara...@apache.org> >> > > wrote: >> > > >> > > > Hi, >> > > > >> > > > I just committed this change >> > > > < >> > > > >> > > >> > >> https://github.com/apache/hbase/commit/da7c6cc059660478eaeb5695b2283a8d90b66a7b >> > > > > >> > > > that >> > > > changes the way we integrate with the ASF infra. Refer to >> HBASE-24261 >> > > > <https://issues.apache.org/jira/browse/HBASE-24261>. As mentioned >> in >> > the >> > > > jira, there _might be_ some unintended consequences, for example, >> > issues >> > > > like >> > > > >> > > > - Something new popped up in the project Github page that was not >> there >> > > > before >> > > > - Project emails being sent to wrong aliases messing up my labels >> > > > - Github PR is spamming jiras with unnecessary comments etc. >> > > > >> > > > These are just some random examples I came up with and they may or >> may >> > > not >> > > > happen, but incase you notice anything odd w.r.t infrastructure, >> please >> > > > report on the jira or respond to this email. Once we are sure that >> all >> > > the >> > > > mailing lists and PR linking is working as expected, we need to do >> > > similar >> > > > fixes in our other repos (and branches). >> > > > >> > > > - Bharath >> > > > >> > > >> > >> >> >> -- >> Sean >> >
