Roadmap #245
PhillypHenning
started this conversation in
Community
Roadmap
#245
Replies: 3 comments 1 reply
-
Let's discuss it! |
Beta Was this translation helpful? Give feedback.
1 reply
-
Following the #277 (comment), one of the topics to discuss perhaps during the next community meeting (TODO add to the agenda) (#257) and also relevant to the Roadmap in general is how do we want to handle the deprecations, deprecation warnings, do we want to keep the functionality backward-compatible or not and if yes then for how many releases. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Need to decide:
Maybe move the conversation into the first community call. some high level notes:
Next steps
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Eventually we'll need a roadmap to communicate to the users the project plans and direction.
This could be tied into 2 categories:
1 Strategic Roadmap (where we want to go)
A nice looking landing page showcasing a very high level direction of the project.
2 Tactical Roadmap (how to get there)
The other part is a list of major features and functionality. Something developers are expecting to find in the docs, that are planned for the future releases as well as what was done in the previous major releases. This could be as small as 2-3 bullet point per release highlighting the biggest changes, including the breaking ones. This is different from the very detailed CHANGELOG (#222) that's composed and maintained for each PR.
And so we can share the BitOps strategy (where we want to go) on the BitOps website/landing page, Tactics (how to get there and what was done) in the docs Roadmap and provide more granular log of specific code changes per PR in the Changelog (#222).
Beta Was this translation helpful? Give feedback.
All reactions