Read the Xfce Release Model to understand why this cycle is the way it is.
| Dates | Phase/Deadline | Everyone's Tasks | Release Team Tasks | Maintainer Tasks |
|---|---|---|---|---|
| 01.11.24 | Xfce 4.20pre1 (Feature + String Freeze) | Install + Test pre1 when available | Prepare release announcements, release Xfce 4.20pre1 | Make sure the latest development release is in good shape and uploaded. Please no new features or string changes. |
| 01.12.24 | Xfce 4.20pre2 (Code Freeze) | Install + Test pre2 when available | Prepare release announcements, release Xfce 4.20pre2 | Please only bugfixes or release blockers |
| (15.12.24) | Xfce 4.20pre3 (Final Freeze) | Install + Test pre3 when available | This is an optional release (release team decides whether we need or skip it in favor of the final release) | |
| 15.12.24 (~29.12.24 with pre3) | Xfce 4.20 (Final Release) | Celebrate | Prepare release announcements, release Xfce 4.20, branch for stable release, merge ELS branches into master | Make sure to upload a new release of own components before this deadline |
xfce_titled_dialog_new_with_buttons() or xfce_spawn_on_screen())Please don't take the issues listed on the milestone pages as obligatory. Keep in mind that they may or may not make it into the 4.20 release, depending on the time the individual developers have.
Sumup GitLab Milestone for 4.20
For quick access, open 4.20 issues by component:
www and cdn, reuse pictures and text from the blog (Skunnyk will create www-new.xfce.org + 4.20 branches for testing). Hint: update this date in order to force a cache update for cdn + don't forget to clear your browser cache. Use php -l $file to validate php code.