| 15-Apr-24 |
30-Apr-24 |
Voting on existing entries |
Everyone, wide community push |
Improve, enhance, formulate new ideas and bring new emerging threats into the fold |
| 01-May-24 |
08-May-24 |
Voting collation and publication |
Core team project management |
|
| 15-May-24 |
15-Jun-24 |
Call for new entries |
Community, current entry leads |
What have we learned since v1.1 and what are our gaps |
| 16-Jun-24 |
30-Jun-24 |
Entry voting |
Everyone, wide community push |
Make v2.0 relevant to the current landscape |
| 01-Jul-24 |
15-Jul-24 |
Voting collation and publication |
Core team leaders & data gathering team |
Ensure v2.0 is accurate from the community input and data |
| 15-Jul-24 |
01-Aug-24 |
Merging down and selection |
Core team leaders & data gathering team |
Coalesce current entries into existing and introduction of new entries |
| 01-Aug-24 |
01-Sep-24 |
Data analysis and voting for ranking |
Everyone, wide community push - New entry leads opportunities |
|
| 01-Sep-24 |
15-Sep-24 |
Entry clean up |
Entry vulnerability leads, community raised issues into triage |
Work through the GitHub issue triage to tune vulnerabilities, prior to publication |
| 15-Sep-24 |
30-Sep-24 |
Layout, pre-announcement work |
Core team design, social and project leads |
Make v2.0 our best version yet |
| 01-Oct-24 |
|
Publish 2.0 |
Social and project leads |
Increase our community and stakeholders! |