Re: [VOTE] Change the default branch for ozone-site from asf-site to master

2024-02-13 Thread Ayush Saxena
+1 -Ayush > On 14-Feb-2024, at 10:12 AM, Sumit Agrawal > wrote: > > Hi, > > The contents of asf-site are automatically *generated from master and >> committed* >> by a GitHub Action >> < >> https://github.com/apache/ozone-site/blob/master/.github/workflows/regenerate.yml >>> . >> From there

Re: [VOTE] Change the default branch for ozone-site from asf-site to master

2024-02-13 Thread Sumit Agrawal
Hi, The contents of asf-site are automatically *generated from master and > committed* > by a GitHub Action > < > https://github.com/apache/ozone-site/blob/master/.github/workflows/regenerate.yml > >. > From there, existing ASF services read the .asf.yml >

Re: [VOTE] Change the default branch for ozone-site from asf-site to master

2024-02-13 Thread Tejaskriya Madan
Hi, Thank you Ethan for bringing this up. I remember facing the same issues you have mentioned when I had to make changes in the ozone-site repo for the first time. I'm +1 for this change. Tejaskriya On Mon, Feb 12, 2024 at 9:46 PM Zita Dombi wrote: > Hi, > > Thanks Ethan for bringing this up,

Re: Supported releases

2024-02-13 Thread Sumit Agrawal
I think we can choose option "1" if any one is using 1.3.0 release, 1. Define support as “security fixes only” and include support for 1.3.0 Incoming bugs are quite high, so fixing in the old version will be difficult at this point of time, can upgrade to a higher version. Regards Sumit On W

Re: Supported releases

2024-02-13 Thread Ethan Rose
While I would also be surprised if people are successfully running an unpatched version of 1.3.0, it seems like a circular dependency to decide which versions to support based on what people are using. People will generally prefer to use supported versions so our messaging here informs their decisi

Re: RFC: Deprecate Slack and move to GitHub Discussions

2024-02-13 Thread Ritesh Shukla
Summary so far: 1. Community wide announcements and notifications via emails are best. 2. Community engagement on technical topics (stuff that search engines should be aware of) best done on GitHub Discussions 3. There should be community feedback around how to organize GitHub Discussions to better