Automatically generate Django series roadmaps from Release data #2233
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Screenshots for the dark theme follows: |
|
Screenshots for the light theme follows: |
|
Small screens: |
nessita
force-pushed
the
django-roadmaps
branch
from
3438158 to
897f696
Compare
This branch adds a new view that replaces the Roadmap wiki pages, e.g.: * https://code.djangoproject.com/wiki/Version5.2Roadmap * https://code.djangoproject.com/wiki/Version6.0Roadmap * https://code.djangoproject.com/wiki/Version6.1Roadmap The wiki pages were almost identical except for version-specific details and target dates. This information is now generated dynamically from the Release model in the database. The supported and future Roadmap tables were reorganized so they follow a more intuitive timeline (from older to newer versions).
nessita
force-pushed
the
django-roadmaps
branch
from
897f696 to
eb3a69a
Compare
| <section id="process"> | ||
| <h2>Process</h2> | ||
| <p>Any features not completed by the feature freeze date won't make it into {{ series }}.</p> | ||
| <p>The release manager will keep the schedule updated and ensure efficient |
There was a problem hiding this comment.
I see we're no longer documenting the release manager anywhere, yes?
There was a problem hiding this comment.
For now, we are not. When we merge the checklist generator in djangoproject.com, we could make use of the "releaser" info from a release (the final one, for example) and include that here perhaps? What do you think?
There was a problem hiding this comment.
Oh I didn't realize that would be blocked on ingesting the checklist generator. Sounds good!
There was a problem hiding this comment.
Right, my point is that "release manager" info is not stored anywhere AFAIK.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch adds a new view that replaces the Roadmap wiki pages, e.g.:
The wiki pages were almost identical except for version-specific details and target dates. This information is now generated dynamically from the Release model in the database.
The supported and future Roadmap tables were reorganized so they follow a more intuitive timeline (from older to newer versions).