Back to the original question in the thread - I think a critical pass through open issues is warranted -
What hasn’t been triaged? What is slated for 4.0 but unassigned ? What is patch available but needs more engineering ? What is ready to commit and uncommitted? You’ve got the context to understand what’s critical and what justifies sending to someone as a potentially concerning bug even without a repro, where a lot of others wouldn’t / don’t. So I’d suggest starting there and trying to make sure there aren’t any critical bug reports around that slipped through past triage attempts. > On Jan 10, 2020, at 8:18 AM, Joshua McKenzie <jmcken...@apache.org> wrote: > > Hey all, > > I've recently had some cycles free up I can dedicate to the open-source > project. My intuition is that I can add the most value right now by > engaging in some simple project management type work (help get assignees > and reviewers for things critical path for 4.0, help stimulate and > facilitate discussions about scope for the upcoming release and subsequent > releases, general triage and test board health, etc). > > Before I wade into the project and start poking and prodding us all, does > anyone have any concerns with me stepping (back ;) ) into this role, or > have any feedback or recommendations before doing so? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
