Skip to content

Move up the "how you can help" section on release roadmap pages #2275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Move up the "how you can help" section on release roadmap pages #2275

Changes from 5 commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
84bcfe5
Move up the "how you can help" section on release roadmap pages
garybadwal Oct 19, 2025
bf00a50
Merge branch 'main' into relase-roadmap-fix
garybadwal Oct 25, 2025
c243d18
Included moving the "Process" section to be a subsection of "Schedule…
garybadwal Oct 25, 2025
007c4be
Merge branch 'relase-roadmap-fix' of https://github.com/garybadwal/dj…
garybadwal Oct 25, 2025
517a24e
"Feature freeze / Alpha 1", "Beta 1", "RC 1", and "Final" has been up…
garybadwal Oct 26, 2025
a13a677
Fixed the H4 closing tags
garybadwal Oct 26, 2025
6c17705
Move up the "how you can help" section on release roadmap pages
garybadwal Oct 19, 2025
facc15d
Merge branch 'relase-roadmap-fix' of https://github.com/garybadwal/dj…
garybadwal Oct 27, 2025
acc4a63
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] Oct 27, 2025
45a2e3f
loaded the fundraising template tag
garybadwal Oct 27, 2025
296fd2f
Merge branch 'relase-roadmap-fix' of https://github.com/garybadwal/dj…
garybadwal Oct 27, 2025
3e0f7d4
updated roadmap.html
garybadwal Oct 27, 2025
6c92a09
Merge branch 'main' into relase-roadmap-fix
garybadwal Nov 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
89 changes: 44 additions & 45 deletions djangoproject/templates/releases/roadmap.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,19 @@ <h2>What features will be in Django {{ series }}?</h2>
by mergers.</p>
</section>

<section id="how-to-help">
<h2>How you can help</h2>
<p>Community effort is key. You can help by:</p>
<ul>
<li>Reading the <a href="http://docs.djangoproject.com/en/dev/internals/contributing/">guide to contributing</a>
and <a href="http://docs.djangoproject.com/en/dev/internals/release-process/">Django's release process</a>.</li>
<li>Working on patches and <a href="https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/">triaging tickets</a>.</li>
<li>Attending sprints.</li>
<li>Testing release snapshots (alphas, betas) against your code and reporting bugs.</li>
<li>Providing as many testers as possible to ensure a bug-free release.</li>
</ul>
</section>

<section id="schedule">
<h2>Schedule</h2>
<p>
Expand Down Expand Up @@ -65,55 +78,41 @@ <h2>Schedule</h2>
</tbody>
</table>
</div>
</section>
<section id="process">
<h3>Process</h3>
<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
routing of issues and reminders for deadlines.</p>

<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
routing of issues and reminders for deadlines.</p>
<section id="feature-freeze-alpha-1">
<h4>Feature freeze / Alpha 1</h3>
Copy link
Contributor

@sarahboyce sarahboyce Oct 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<h4>Feature freeze / Alpha 1</h3>
<h4>Feature freeze / Alpha 1</h4>

(For all)

Copy link
Author

@garybadwal garybadwal Oct 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sarahboyce Sorry I missed it 😅, was a bit excited. Updated this in new commit.

<p>All major and minor features must be merged by the Alpha 1 deadline. Any
features not done by this point will be deferred or dropped. At this time, we
will fork <code>stable/{{ series }}.x</code> from <code>main</code>.</p>
<p>After the alpha, non-release blocking bug fixes may be backported at the
mergers' discretion.</p>
</section>

<section id="feature-freeze-alpha-1">
<h3>Feature freeze / Alpha 1</h3>
<p>All major and minor features must be merged by the Alpha 1 deadline. Any
features not done by this point will be deferred or dropped. At this time, we
will fork <code>stable/{{ series }}.x</code> from <code>main</code>.</p>
<p>After the alpha, non-release blocking bug fixes may be backported at the
mergers' discretion.</p>
</section>
<section id="beta-1">
<h4>Beta 1</h3>
<p>Beta 1 marks the end of changes that aren't release blocking bugs. Only release
blocking bug fixes will be allowed to be backported after the beta.</p>
</section>

<section id="beta-1">
<h3>Beta 1</h3>
<p>Beta 1 marks the end of changes that aren't release blocking bugs. Only release
blocking bug fixes will be allowed to be backported after the beta.</p>
</section>

<section id="rc-1">
<h3>RC 1</h3>
<p>If release blockers are still coming in at the planned release candidate date,
we'll release beta 2 to encourage further testing. RC 1 marks the freeze for
translation strings; translators will have two weeks to submit updates. Release
blocking bug fixes may continue to be backported.</p>
</section>

<section id="final">
<h3>Final</h3>
<p>Django {{ series }} final will ideally ship two weeks after the last RC. If no major bugs
are found by then, {{ series }} final will be issued; otherwise, the timeline will be
adjusted as needed.</p>
</section>
<section id="rc-1">
<h4>RC 1</h3>
<p>If release blockers are still coming in at the planned release candidate date,
we'll release beta 2 to encourage further testing. RC 1 marks the freeze for
translation strings; translators will have two weeks to submit updates. Release
blocking bug fixes may continue to be backported.</p>
</section>

<section id="how-to-help">
<h3>How you can help</h3>
<p>Community effort is key. You can help by:</p>
<ul>
<li>Reading the <a href="http://docs.djangoproject.com/en/dev/internals/contributing/">guide to contributing</a>
and <a href="http://docs.djangoproject.com/en/dev/internals/release-process/">Django's release process</a>.</li>
<li>Working on patches and <a href="https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/">triaging tickets</a>.</li>
<li>Attending sprints.</li>
<li>Testing release snapshots (alphas, betas) against your code and reporting bugs.</li>
<li>Providing as many testers as possible to ensure a bug-free release.</li>
</ul>
<section id="final">
<h4>Final</h3>
<p>Django {{ series }} final will ideally ship two weeks after the last RC. If no major bugs
are found by then, {{ series }} final will be issued; otherwise, the timeline will be
adjusted as needed.</p>
</section>
</section>
</section>

Expand Down