uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.31.4. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
probably be too late to get in 3.31.90. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
New APIs must be fully documented
Writing of release notes be
late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
No string changes may be made without confirmation from the i18n team
and notification to release team, translation team, and documentation
team. From this point, developers can concentrate on sta
late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
This is a late freeze to avoids sudden last-minute accidents which
could risk the stability that should have been reached at this point.
No source code changes are allowed without approval from the re
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.32.0. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.32.1. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.33.1. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.32.2. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.33.2. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.33.3. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.33.4. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
probably be too late to get in 3.33.90. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
New APIs must be fully documented
Writing of release notes be
late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
No string changes may be made without confirmation from the i18n team
and notification to release team, translation team, and documentation
team. From this point, developers can concentrate on sta
late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
This is a late freeze to avoids sudden last-minute accidents which
could risk the stability that should have been reached at this point.
No source code changes are allowed without approval from the re
you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!
Hard Code Freeze ends, but other freezes remain in effect for the
stable branch.
For more information about 3.33, the full schedule, the official
module lists and the proposed mo
: tarballs uploaded later than that will probably be too late to
get in 3.34.1. If you are not able to make a tarball before this
deadline or if you think you'll be late, please send a mail to the
release team and we'll find someone to roll the tarball for you!
For more information about
: tarballs uploaded later than that will probably be too late
to get in 3.35.1. If you are not able to make a tarball before this
deadline or if you think you'll be late, please send a mail to the
release team and we'll find someone to roll the tarball for you!
For more information about
lease send a mail to the
release team and we'll find someone to roll the tarball for you!
Tarballs are due on 2019-11-23 before 23:59 UTC for the GNOME 3.34.2
stable release, which will be delivered next week. Core modules should
try to follow the unstable schedule so everyone can test them. P
lease send a mail to the
release team and we'll find someone to roll the tarball for you!
Tarballs are due on 2020-01-04 before 23:59 UTC for the GNOME 3.34.3
stable release, which will be delivered next week. Core modules should
try to follow the unstable schedule so everyone can test them. P
3.35.90. If you are not able to make a tarball before this
deadline or if you think you'll be late, please send a mail to the
release team and we'll find someone to roll the tarball for you!
New APIs must be fully documented
Writing of release notes begins
For more information
ll be late, please send a mail to the
release team and we'll find someone to roll the tarball for you!
Tarballs are due on 2020-02-15 before 23:59 UTC for the GNOME 3.34.4
stable release, which will be delivered next week. Core modules should
try to follow the unstable schedule so everyone can
mail to the
release team and we'll find someone to roll the tarball for you!
Hard Code Freeze ends, but other freezes remain in effect for the
stable branch.
For more information about 3.35, the full schedule, the official
module lists and the proposed module lists, please see our colorful
mail to the
release team and we'll find someone to roll the tarball for you!
Hard Code Freeze ends, but other freezes remain in effect for the
stable branch.
For more information about 3.35, the full schedule, the official
module lists and the proposed module lists, please see our colorful
mail to the
release team and we'll find someone to roll the tarball for you!
Hard Code Freeze ends, but other freezes remain in effect for the
stable branch.
For more information about 3.35, the full schedule, the official
module lists and the proposed module lists, please see our colorful
if you think you'll be late, please send a mail to the
release team and we'll find someone to roll the tarball for you!
Tarballs are due on 2020-04-25 before 23:59 UTC for the GNOME 3.36.2
stable release, which will be delivered next week. Core modules should
try to follow the unstable s
Hello all,
We would like to inform you about the following:
* GNOME 3.37.2 unstable tarballs due
* GNOME 3.36.3 stable tarballs due
* GNOME 3.34.7 oldstable tarballs due
Tarballs are due on 2020-05-30 before 23:59 UTC for the GNOME 3.37.2
unstable release, which will be delivered next week. In o
Hello all,
We would like to inform you about the following:
* GNOME 3.37.3 unstable tarballs due
* GNOME 3.36.4 stable tarballs due
* GNOME 3.34.8 oldstable tarballs due
Tarballs are due on 2020-07-04 before 23:59 UTC for the GNOME 3.37.3
unstable release, which will be delivered next week. In o
Hello all,
We would like to inform you about the following:
* GNOME 3.37.90 beta tarballs due
* GNOME 3.36.5 stable tarballs due
* GNOME 3.34.9 oldstable tarballs due
* API/ABI, UI and Feature Addition Freeze; String Change Announcement Period
* New APIs must be fully documented
* Writing of relea
Hello all,
We would like to inform you about the following:
* GNOME 3.37.91 beta tarballs due
* String Freeze
Tarballs are due on 2020-08-22 before 23:59 UTC for the GNOME 3.37.91
beta release, which will be delivered next week. In order to ensure
adequate testing, core modules should try to rel
of the GNOME runtime.
This is a late freeze to avoids sudden last-minute accidents which
could risk the stability that should have been reached at this point.
No source code changes are allowed without approval from the release
team, but translation and documentation should continue. Simple build
Hello all,
Soft translation deadline
For more information about 3.37, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.37
page:
http://www.gnome.org/start/unstable
For a quick overview of the GNOME schedule, please see:
https://wiki.gno
, please contact the
release team and we'll find someone to handle the release for you.
Hard Code Freeze ends, but other freezes remain in effect for the
stable branch.
For more information about 3.37, the full schedule, the official
module lists and the proposed module lists, please see our col
Hello all,
We would like to inform you about the following:
* GNOME 3.38.1 stable tarballs due
* GNOME 3.36.7 oldstable tarballs due
Tarballs are due on 2020-10-03 before 23:59 UTC for the GNOME 3.38.1
stable release, which will be delivered next week. Core modules are
not expected to follow the
Hello all,
We would like to inform you about the following:
* GNOME 3.38.2 stable tarballs due
* GNOME 3.36.8 oldstable tarballs due
Tarballs are due on 2020-11-21 before 23:59 UTC for the GNOME 3.38.2
stable release, which will be delivered next week. Core modules are
not expected to follow the
Hello all,
We would like to inform you about the following:
* GNOME 40.alpha newstable tarballs due
* GNOME 3.38.3 stable tarballs due
* GNOME 3.36.9 oldstable tarballs due
Tarballs are due on 2021-01-09 before 23:59 UTC for the GNOME 40.alpha
newstable release, which will be delivered next week
Hello all,
We would like to inform you about the following:
* GNOME 40.beta newstable tarballs due
* GNOME 3.38.4 stable tarballs due
* GNOME 3.36.10 oldstable tarballs due
* API/ABI, UI and Feature Addition Freeze; String Change Announcement Period
* New APIs must be fully documented
* Writing of
Hello all,
No string changes may be made without confirmation from the i18n team.
>From this point, developers can concentrate on stability and
bugfixing. Translators can work without worrying that the original
English strings will change, and documentation writers can take
accurate screenshots. F
risk the stability that should have been reached at this point.
No source code changes are allowed without approval from the release
team, but translation and documentation should continue. Simple build
fixes are, of course, allowed without asking.
For more information about the schedule for
Hello all,
Soft translation deadline is 2021-03-17 at 23:59 UTC. Translations
committed after this point may be too late to be included. Maintainers
should not release stable tarballs until after this day.
For more information about the schedule for GNOME 40,
please see:
https://wiki.gnome.or
too late. If you need help, please contact the
release team and we'll find someone to handle the release for you.
Tarballs are due on 2021-03-20 before 23:59 UTC for the GNOME 3.38.5
stable release, which will be delivered next week. Core modules are
not expected to follow the schedule for s
Hello all,
We would like to inform you about the following:
* GNOME 40.1 stable tarballs due
* GNOME 3.38.6 oldstable tarballs due
Tarballs are due on 2021-05-01 before 23:59 UTC for the GNOME 40.1
stable release, which will be delivered next week. Core modules are
not expected to follow the sch
Hello all,
We would like to inform you about the following:
* GNOME 40.2 stable tarballs due
* GNOME 3.38.7 oldstable tarballs due
Tarballs are due on 2021-06-05 before 23:59 UTC for the GNOME 40.2
stable release, which will be delivered next week. Core modules are
not expected to follow the sch
Hello all,
We would like to inform you about the following:
* GNOME 41.alpha newstable tarballs due
* GNOME 40.3 stable tarballs due
* GNOME 3.38.8 oldstable tarballs due
Tarballs are due on 2021-07-10 before 23:59 UTC for the GNOME 41.alpha
newstable release, which will be delivered next week.
Hello all,
We would like to inform you about the following:
* GNOME 41.beta newstable tarballs due
* GNOME 40.4 stable tarballs due
* GNOME 3.38.9 oldstable tarballs due
* API/ABI, UI and Feature Addition Freeze; String Change Announcement Period
* New APIs must be fully documented
* Writing of re
Hello all,
No string changes may be made without confirmation from the i18n team.
>From this point, developers can concentrate on stability and
bugfixing. Translators can work without worrying that the original
English strings will change, and documentation writers can take
accurate screenshots. F
risk the stability that should have been reached at this point.
No source code changes are allowed without approval from the release
team, but translation and documentation should continue. Simple build
fixes are, of course, allowed without asking.
For more information about the schedule for
Hello all,
We would like to inform you about the following:
* GNOME 41.1 stable tarballs due
* GNOME 40.6 oldstable tarballs due
Tarballs are due on 2021-10-30 before 23:59 UTC for the GNOME 41.1
stable release, which will be delivered next week. Core modules are
not expected to follow the sched
Hello all,
We would like to inform you about the following:
* GNOME 41.2 stable tarballs due
* GNOME 40.7 oldstable tarballs due
Tarballs are due on 2021-12-04 before 23:59 UTC for the GNOME 41.2
stable release, which will be delivered next week. Core modules are
not expected to follow the sched
Hello all,
We would like to inform you about the following:
* GNOME 42.alpha newstable tarballs due
* GNOME 41.3 stable tarballs due
* GNOME 40.8 oldstable tarballs due
Tarballs are due on 2022-01-08 before 23:59 UTC for the GNOME 42.alpha
newstable release, which will be delivered next week. In
Hello all,
We would like to inform you about the following:
* GNOME 42.beta newstable tarballs due
* GNOME 41.4 stable tarballs due
* GNOME 40.9 oldstable tarballs due
* API/ABI, UI and Feature Addition Freeze; String Change Announcement Period
* New APIs must be fully documented
* Writing of rele
Hello all,
No string changes may be made without confirmation from the i18n team.
>From this point, developers can concentrate on stability and
bugfixing. Translators can work without worrying that the original
English strings will change, and documentation writers can take
accurate screenshots. F
risk the stability that should have been reached at this point.
No source code changes are allowed without approval from the release
team, but translation and documentation should continue. Simple build
fixes are, of course, allowed without asking.
For more information about the schedule for
Hello all,
Soft translation deadline is 2022-03-16 at 23:59 UTC. Translations
committed after this point may be too late to be included. Maintainers
should not release stable tarballs until after this day.
For more information about the schedule for GNOME 42,
please see:
https://wiki.gnome.or
later than
that will probably be too late. If you need help, please contact the
release team and we'll find someone to handle the release for you.
Tarballs are due on 2022-03-19 before 23:59 UTC for the GNOME 41.5
stable release, which will be delivered next week. Core modules are
not expect
Hello all,
We would like to inform you about the following:
* GNOME 42.1 stable tarballs due
* GNOME 41.6 oldstable tarballs due
Tarballs are due on 2022-04-23 before 23:59 UTC for the GNOME 42.1
stable release, which will be delivered next week. Core modules are
not expected to follow the sched
Hello all,
We would like to inform you about the following:
* GNOME 42.2 stable tarballs due
* GNOME 41.7 oldstable tarballs due
Tarballs are due on 2022-05-28 before 23:59 UTC for the GNOME 42.2
stable release, which will be delivered next week. Core modules are
not expected to follow the sched
Hello all,
We would like to inform you about the following:
* GNOME 43.alpha newstable tarballs due
* GNOME 42.3 stable tarballs due
* GNOME 41.8 oldstable tarballs due
Tarballs are due on 2022-07-02 before 23:59 UTC for the GNOME 43.alpha
newstable release, which will be delivered next week. In
features are
not affected. This allows developers to concentrate on refining the
new features instead of adding yet more functionality. UI freeze
begins on 2022-08-06 at 23:59 UTC. No major UI changes may be made
without confirmation from the release team. Small fixes do not require
permission.
New APIs
101 - 158 of 158 matches
Mail list logo
