Yes, the mailing list will stay as is (but I imagine even more activity will move to Github, which is already true to a large extent today).
On Thu, May 30, 2019 at 4:44 AM Samuel Marks <[email protected]> wrote: > Will the mailing list stay active? > > Samuel Marks > http://linkedin.com/in/samuelmarks > > > On Thu, May 30, 2019 at 7:20 AM Tomaz Muraus <[email protected]> wrote: > > > Everyone, > > > > Apache now supports Github as a first class citizen ( > > https://gitbox.apache.org/), so I think it's finally time to drop > support > > for (bloated, non-user friendly and passé) JIRA and move all the project > > development to Github. > > > > We've pretty much done that in a limited fashion (due to Github repos > being > > read-only) for many years now, but we can now also move things such as > > issue tracking and milestone / release management to Github. Not to > mention > > that JIRA hasn't been actively updated and managed for a while now... > > > > All the Github repos are configured so notifications about new PRs, > issues, > > comments, reviews, etc. (including edits) are emailed to our > notifications@ > > mailing list so full audit history is still preserved. > > > > I think this will help a lot with user friendliness and reduce the > barrier > > to contribution. It will also make life easier for committers / reviewers > > since they can merge PRs directly. > > > > If there are no objections to that, next steps will include: > > > > 1. Opening ASF infra ticket to enable issue, milestone and > > release management for our Github repository (we asked for it to be > > disabled in the past when the repo was read-only for us) > > > > 2. Updating all the references to JIRA on our website and documentation. > > This includes documenting new Github flow for contributors and committers > > > > 3. Closing the JIRA project and directing people to our Github repo and > > contribution docs > > >
