This issue is meant to lead to the creation of a roadmap and clarification of the existing milestones.

Current milestones

There are 3 milestones so far and one is due the end of the month:

• v0.2.0: https://github.com/WordPress/abilities-api/milestone/3
• WP 6.9 Beta: https://github.com/WordPress/abilities-api/milestone/2
• Later: Anything after WP 6.9 but considered a priorty https://github.com/WordPress/abilities-api/milestone/4

The roadmap to WP 6.9

Initially the roadmap is going to be heavily focused on 6.9, there can is a ‘later’ milestone though to use for anything outside.

Triage and ensuring issues made

Whilst making sure the decisions are made, it’s a good time now to make sure everything to be decided for 6.9 has an issue and also if it doesn’t one is created. Along with this let’s review the milestones to be really sure what we have in them.

Proposal to release to schedule

In order to make this easier for us to manage, I would propose that we have a two-week release cycle going up and during 6.9 or consider if we should release. If there are things to, we ship. This means we can rapidly bug fix in testing, it also means we can set some nice timed milestones and cadence for everyone.

Once WP 6.9 is locked in, we can stop this cadence or review if it indeed is working for everyone.

———————————

Decisions needed

There are two outstanding decisions need discussion within the comments in order to ensure we have a full roadmap within milestones. They are:

• What core abilities to include: WordPress Core Abilities ai#40.
• Client side capabilities. This has a PR: Add client-side package for Abilities API #60. [ Decision: this will be included ]

Once those decisions are made they can be added to the milestones and issues updated if applicable.

Next steps

Pinging a few people for input and then after this should have decisions by mid-week, to move to locking in milestones and focusing on shipping. Anyone is welcome to add input, but particularly pinging anyone that participated in the discussion during weekly sync.

@Jameswlepage @felixarntz @jeffpaul @swissspidy @gziolo @justlevine @galatanovidiu