Final Beta Freeze/Release rescheduled for Raring
A fair while back, there was a concensus reached among various flavour leads that the two-week/four-week spacing from Beta1 to Beta2 to Final Release was suboptimal, and it was agreed that we would move Beta2 a week later to make it less objectionable. Unfortunately, while we all agreed this was a stellar idea, and one of us even agreed to update the schedule, I suspect that among debates about various strawman rolling release proposals, it slipped through the cracks. So, without further ado, I've corrected the schedule and Final Beta (or Beta2, for flavours that did a Beta1 and like to count with small integers) will now happen on April 4th, with its freeze landing on March 28th. Please adjust your calendars as appropriate. If you have any questions, note that I'm the Release Engineering contact for Final Beta, so feel free to talk to me. ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Raring frozen for Final Beta, and continuing on to Release
Just a quick heads-up, the queue for raring(-proposed) is now frozen for the preparation of the Final Beta, and all uploads now go through a manual review process before being accepted or rejected. As always, unseeded universe packages will be let through with a minimum of fuss (though we may try to talk people out of doing silly things like starting a new transition this late in the cycle), and seeded packages will recieve a fair bit of attention to detail to make sure people aren't breaking Feature Freeze or, frankly, just breaking things in general. As with the last few releases, the freeze will remain in effect until raring releases, to add an extra level of review and avoid obvious regressions or feature freeze circumvention. If you need to make an upload that you feel might get rejected, please contact the release team first. Bugfixes, of course, are greatly appreciated, and will be reviewed and accepted promptly. Please help us make this another smooth and polished Ubuntu release, and thanks in advance for all the hard work in that direction. On behalf of the Ubuntu Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Final Freeze for Ubuntu 13.04 (Raring) now in effect
For the timezone challenged, as of 2100UTC today, the archive is officially fozen in preparation of release candidates and the final release of Raring Ringtail in a week. Uploads from here on in should fall into the following bins: 1) Installer/release-critical bugs that absolutely MUST get fixed lest we risk shipping a broken image that turns computers pink or sets them on fire: Please contact the release team about these bugs and upload (well-tested) solutions ASAP. 2) Non-release-critical-but-nice-to-have bugfixes: These are fixes that you would absolutely feel comfortably about doing as an SRU but not necessarily destabilising the release process for. Again, contact the release team, and we may slip some of these in, while asking you to defer the rest to SRUs. 3) Feature additions, massive code refactoring, user interface changes, non-typo string changes: Just don't upload these, or ask about them. The time for them came and went long ago. 4) Updates to non-seeded packages: Technically, unseeded packages don't freeze until pretty much right before release. While this is true, we may still try to talk you out of pushing some huge new upstream version of something, or start a library transition at the zero hour. We're only a week away from opening the next release, a bit of patience (or prepping in a PPA, etc) might be a decent plan. Here's hoping everyone gets on board with testing images, helping to fix absolutely critical bugs, donating spare creative cycles to the release notes, and any other way we can all contribute to yet another great Ubuntu release. ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Saucy Salamander now open for development
Most cycles, we have a week of breathing room where we can flip all the switches in a coordinated fashion and open everything at exactly the same time, but this archive opening sees various members of the release, archive, and toolchain teams in transit all over the globe, so we'll stagger things a bit. In the next day or two, you should see a followup to this email from Matthias Klose doing his usual announcement of what has changed in the default toolchain, and Colin Watson turning on autosyncs from Debian. Rather than wait until we're all awake at the same time, however, I'm unfreezing the archive this morning and declaring Saucy open for active development. Happy merging. On behalf of the Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Final Freeze for Ubuntu 13.10 (Saucy) at 2100UTC today
[ This is a shameless copy-and-paste from last year ] For the timezone challenged, as of 2100UTC today, the archive is officially fozen in preparation of release candidates and the final release of Saucy Salamander in a week. This is three hours from the time I hit send on this email. Uploads from here on in should fall into the following 4 bins: 1) Installer/release-critical bugs that absolutely MUST get fixed lest we risk shipping a broken image that turns computers pink or sets them on fire: Please contact the release team about these bugs and upload (well-tested) solutions ASAP. Last minute hardware enablement fixes, and pretty much anything installer related that is auditable and testable also falls in to this category, as our best installer testing comes in the next few days, historically. Some people may have noticed that we're also in the process of spinning up a new port right now (our timing is impeccable, is it not?), so uploads with clear and targetted FTBFS fixes for arm64 will continue to be accepted for seeded packages until Sunday night, and for unseeded pretty much right up to release. 2) Non-release-critical-but-nice-to-have bugfixes: These are fixes that you would absolutely feel comfortably about doing as an SRU but not necessarily destabilising the release process for. Again, contact the release team, and we may slip some of these in, while asking you to defer the rest to SRUs. 3) Feature additions, massive code refactoring, user interface changes, non-typo string changes: Just don't upload these, or ask about them. The time for them came and went long ago. 4) Updates to non-seeded packages: Technically, unseeded packages don't freeze until pretty much right before release. While this is true, we may still try to talk you out of pushing some huge new upstream version of something, or start a library transition at the zero hour. We're only a week away from opening the next release, a bit of patience (or prepping in a PPA, etc) might be a decent plan. Here's hoping everyone gets on board with testing images, helping to fix absolutely critical bugs, donating spare creative cycles to the release notes, and any other way we can all contribute to yet another great Ubuntu release. ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Trusty Tahr Final Beta Freeze
As of nowish, the archive is frozen for 14.04 Final Beta preparation, and will continue to be frozen from here until Final release next month. As with the previous release, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. Happy bughunting on our push from here to the final release, and please do help out your favourite flavour(s) with ISO testing and feedback. On behalf of the Ubuntu Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Final Freeze for Ubuntu 14.04 LTS (trusty) at 2100UTC today
[ Another cycle, another shameless copy and paste email... ] For the timezone challenged, as of 2100UTC today, the archive is officially frozen in preparation of release candidates and the final release of Saucy^WTrusty Tahr in a week. This is one hour from the time I hit send on this email. Uploads from here on in should fall into the following 4 bins: 1) Installer/release-critical bugs that absolutely MUST get fixed lest we risk shipping a broken image that turns computers mauve or sets them on fire: Please contact the release team about these bugs and upload (well-tested) solutions ASAP. Last minute hardware enablement fixes, and pretty much anything installer related that is auditable and testable also falls in to this category, as our best installer testing comes in the next few days, historically. Much like last cycle, this one also had some new porting going on (we do enjoy our fun toys), and like last cycle, we'll gladly take FTBFS fixes pretty close to the wire, as long as they're clear and easily reviewable. 2) Non-release-critical-but-nice-to-have bugfixes: These are fixes that you would absolutely feel comfortably about doing as an SRU but not necessarily destabilising the release process for. Again, contact the release team, and we may slip some of these in, while asking you to defer the rest to SRUs. 3) Feature additions, massive code refactoring, user interface changes, non-typo string changes: Just don't upload these, or ask about them. The time for them came and went long ago. 4) Updates to non-seeded packages: Technically, unseeded packages don't freeze until pretty much right before release. While this is true, we may still try to talk you out of pushing some huge new upstream version of something, or start a library transition at the zero hour. We're only a week away from opening the next release, a bit of patience (or prepping in a PPA, etc) might be a decent plan. Here's hoping everyone gets on board with testing images, helping to fix absolutely critical bugs, donating spare creative cycles to the release notes, and any other way we can all contribute to yet another great Ubuntu release. And don't forget kids, this one's an LTS. It's the release you'll install for your friends, family, and work networks and then promptly forget about for two years because it's just that awesome. At least, it should be. So, if it's not, let's make sure we sort that out. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Utopic Unicorn (14.10) is Open for Business
That's right. Business, with a capital B. It's too late for me to write anything coherent, so here's a quick list of things we did pre-opening to make your life more painful^Winteresting: - ruby-defaults updated to 2.1 - boost-defaults updated to 1.55 - new binutils snapshot - tiny unicorns in every package The first autosync with Debian is running right now, so don't get overexcited and sync something by hand that the automated machinery will get to in the next hour. The buildds will be very, very angry with us for a couple of days due to the above autosync. Have some patience. Upload your merges, and don't babysit the queues. You'll thank me for it. You might even want to go out for a walk, get some fresh air, feed a duck, that sort of thing. I know post-LTS releases are always an exciting barrage of tossing in all the things you didn't think you could land in an LTS without the release team glaring at you, and I'm sure this one will be no exception. So, have fun, happy uploading, and do try to fix two bugs for every one you upload. Ish. ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Feature Freeze in effect for 14.10
As of nowish, Feature Freeze is in effect for utopic (14.10), leading up to the release in October. Don't fret if you have One Last Feature to get uploaded, and don't panic and upload it untested today just to try to beat the clock. We would rather see a feature freeze exception bug and a well-tested upload than something rushed to beat a deadline. That said, the vast majority of people should be winding down new feature development now and focusing on bug fixes and polish to make 14.10 yet another great release come October. On behalf of the Ubuntu Release Team, ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Utopic Unicorn (14.10) Final Beta Freeze
[ NOTE: Recycled email from six months ago, you're not going crazy ] As of nowish, the archive is frozen for 14.10 Final Beta preparation, and will continue to be frozen from here until Final release next month. As with the previous release, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. Happy bughunting on our push from here to the final release, and please do help out your favourite flavour(s) with ISO testing and feedback. On behalf of the Ubuntu Release Team, Adam Conrad PS: If you find something being hung up in the queue that you feel should be auto-accepted, let us know, we might need to tweak the bot a bit. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Final Freeze for Ubuntu 14.10 (utopic) in effect
Sending the email announce a bit late, but those who pay attention to release schedules should already know that the utopic Final Freeze is now in effect. The following will be yet another copy and paste from previous releases: Uploads from here on in should fall into the following 4 bins: 1) Installer/release-critical bugs that absolutely MUST get fixed lest we risk shipping a broken image that turns computers puce or sets them on fire: Please contact the release team about these bugs and upload (well-tested) solutions ASAP. Last minute hardware enablement fixes, and pretty much anything installer related that is auditable and testable also falls in to this category, as our best installer testing comes in the next few days, historically. Much like last cycle, this one also had some new porting going on (we do enjoy our fun toys), and like last cycle, we'll gladly take FTBFS fixes pretty close to the wire, as long as they're clear and easily reviewable. 2) Non-release-critical-but-nice-to-have bugfixes: These are fixes that you would absolutely feel comfortably about doing as an SRU but not necessarily destabilising the release process for. Again, contact the release team, and we may slip some of these in, while asking you to defer the rest to SRUs. 3) Feature additions, massive code refactoring, user interface changes, non-typo string changes: Just don't upload these, or ask about them. The time for them came and went long ago. 4) Updates to non-seeded packages: Technically, unseeded packages don't freeze until pretty much right before release. While this is true, we may still try to talk you out of pushing some huge new upstream version of something, or start a library transition at the zero hour. We're only a week away from opening the next release, a bit of patience (or prepping in a PPA, etc) might be a decent plan. Here's hoping everyone gets on board with testing images, helping to fix absolutely critical bugs, donating spare creative cycles to the release notes, and any other way we can all contribute to yet another great Ubuntu release. Later tonight, we will be turning off the daily cron jobs and will spin up a set of RC images. As much as I'd love for them to be the final images, I'm not that optimistic, and I'm sure there will be reasons to respin, but please do get to testing, so we have a better handle on the state of the world as it is today. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Vivid Vervet (15.04) now open for business
After a short period of wrangling things from utopic-proposed to vivid-proposed and a few small merges and uploads to prime the archive, vivid is now open for development. In theory, this shouldn't change much, but the arch-indep build architecture has been changed from i386 to amd64, which more closely matches what (most) developers test on, and also what Debian will be doing when they implement their source upload strategy. Nothing else major is happening on opening day, however there are some things to look out for in the coming months: - A switch from C to C.UTF-8 on the builders and the default locale when none is selected in the installer. - A move to glibc 2.20 or 2.21, timing dependent. - Steady progress on the systemd transition, with a goal to switch over in the first half of the cycle. Autosyncs will be running shortly, so give a little patience to the buildd network as they work through the queue, and no need to rush to sync your favourite package, it'll get there. Lots of reports still point to utopic, and ISO builds aren't on yet, but we'll sort both of those out in the coming days. Happy hacking, happy uploading, and may all your vervets be vivid. Whatever a vervet is. ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Vivid Vervet (15.04) Final Beta Freeze
After I get some sleep, I will be freezing the archive later today, at around midnight UTC, and it will continue to be frozen from here until final release next month. After this nap and freezing business, I will be massaging some last uploads through the proposed-migration machinery and building a full set of candidate ISOs for Final Beta. As with the previous release, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. Happy bughunting on our push from here to the final release, and please do help out your favourite flavour(s) with ISO testing and feedback. On behalf of the Ubuntu Release Team, Adam Conrad PS: If you find something being hung up in the queue that you feel should be auto-accepted, let us know, we might need to tweak the bot a bit. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Wily Werewolf (15.10) now open for development
After a few procedural hiccups, Wascally Wabbit^W^WWily Werewolf is now open for development. Very little has changed in the opening base system and toolchain, however do note that due to jessie releasing only a couple of days after vivid, many Debian developers have awoken from hibernation and auto-syncs and merges should be full of new shiny to look at. This is fairly good timing, as we'll have a bunch of new shiny in 15.10, and some time to polish all of that for 16.04, so get to merging and let's make this another awesome release! Also of note, the systemd transition went quite smoothly last cycle, thanks in large part to the amazing efforts of Martin Pitt (thanks pitti!), but there are still rough edges, lots of packages without native systemd units, etc. Keep an eye out for merges from Debian with systemd fixed/additions and pull those in when you can, and of course, don't be afraid to scratch your own itches when you spot a bit of buggy behaviour. I'll stop babbling now and let people get on to what they're best at, which is making the best[1] Linux distribution in the world! ... Adam [1] I might be slightly biased here, but can you really blame me? -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Wily Werewolf Alpha 1 Released
"I'm getting really sick of being misquoted in release announcements." - Oscar Wilde, probably. The first alpha of the Wily Werewolf (to become 15.10) has now been released! This alpha features images for Kubuntu, Lubuntu, Ubuntu MATE, UbuntuKylin and the Ubuntu Cloud images. Pre-releases of the Wily Werewolf are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu flavor developers and those who want to help in testing, reporting and fixing bugs as we work towards getting this release ready. Alpha 1 includes a number of software updates that are ready for wider testing. This is quite an early set of images, so you should expect some bugs. While these Alpha 1 images have been tested and work, except as noted in the release notes, Ubuntu developers are continuing to improve the Wily Werewolf. In particular, once newer daily images are available, system installation bugs identified in the Alpha 1 installer should be verified against the current daily image before being reported in Launchpad. Using an obsolete image to re-report bugs that have already been fixed wastes your time and the time of developers who are busy trying to make 15.10 the best Ubuntu release yet. Always ensure your system is up to date before reporting bugs. Kubuntu: Kubuntu uses KDE software and now features the new Plasma 5 desktop. The Alpha-1 images can be downloaded at: http://cdimage.ubuntu.com/kubuntu/releases/wily/alpha-1/ More information on Kubuntu Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/Kubuntu Lubuntu: Lubuntu is a flavour of Ubuntu based on LXDE and focused on providing a very lightweight distribution. The Alpha 1 images can be downloaded at: http://cdimage.ubuntu.com/lubuntu/releases/wily/alpha-1/ More information on Lubuntu Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/Lubuntu Ubuntu MATE: Ubuntu MATE is a flavour of Ubuntu featuring the MATE desktop environment. The Alpha-1 images can be downloaded at: http://cdimage.ubuntu.com/ubuntu-mate/releases/wily/alpha-1/ More information on Ubuntu MATE Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/UbuntuMATE UbuntuKylin: UbuntuKylin is a flavour of Ubuntu that is more suitable for Chinese users. The Alpha-1 images can be downloaded at: http://cdimage.ubuntu.com/ubuntukylin/releases/wily/alpha-1/ More information on UbuntuKylin Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/UbuntuKylin Ubuntu Cloud Ubuntu Cloud images can be run on Amazon EC2, Openstack, SmartOS and many other clouds. http://cloud-images.ubuntu.com/releases/wily/alpha-1/ Regular daily images for Ubuntu can be found at: http://cdimage.ubuntu.com If you're interested in following the changes as we further develop Wily, we suggest that you subscribe to the ubuntu-devel-announce list. This is a low-traffic list (a few posts a week) carrying announcements of approved specifications, policy changes, alpha releases and other interesting events. http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce A big thank you to the developers and testers for their efforts to pull together this Alpha release! On behalf of the Ubuntu Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Wily Werewolf (15.10) Final Beta Freeze
As of about ten minutes ago, wily has entered the final beta freeze, with a goal of releasing Final Beta images sometime late Thursday. The queue freeze will last from now until final release in October, which means that all seeded packages will now need a spot-check and review in the queue from a release team member before they are let into the archive. As with the previous releases, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. If you find the bot is blocking an upload that you think should have been auto-accepted, let us know and we'll sort it out. I will be spinning a set of beta candidates right now which I encourage people to get to testing ASAP for their favourite flavour(s), but do expect at least one respin tomorrow for the newer kernel and gcc, at the very least. Happy bughunting from now until the final release, and please do help out and test ISOs, netboot, etc, where you can and let us know what's broken in your environment(s). On behalf of the Ubuntu Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Wily Werewolf (15.10) Final Freeze
As of nowish, wily has entered the Final Freeze period in preparation for the final release of Ubuntu 15.10 next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-base basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Feature Freeze in effect for Xenial Xerus (16.04 LTS)
As of about 3 hours ago, Feature Freeze is in effect for Xenial, leading up to the release in April. Don't fret if you have One Last Feature to get uploaded, and don't panic and upload it untested today just to try to beat the clock. We would rather see a feature freeze exception bug and a well-tested upload than something rushed to beat a deadline. That said, the vast majority of people should be winding down new feature development now and focusing on bug fixes and polish to make 16.04 yet another great release come April. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Xenial Xerus (16.04 LTS) Final Beta Freeze
As of about two minutes ago, xenial has entered the final beta freeze, with a goal of releasing Final Beta images sometime late Thursday. The queue freeze will last from now until final release in April, which means that all seeded packages will now need a spot-check and review in the queue from a release team member before they are let into the archive. As with the previous releases, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. If you find the bot is blocking an upload that you think should have been auto-accepted, let us know and we'll sort it out. I will be spinning a set of beta candidates right now which I encourage people to get to testing ASAP for their favourite flavour(s) as they come off the line. Happy bug-hunting from now until the final release, and please do help out and test ISOs, netboot, etc, where you can and let us know what's broken in your environment(s). On behalf of the Ubuntu Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Xenial Xerus (16.04 LTS) Final Freeze
As of nowish, xenial has entered the Final Freeze period in preparation for the final release of Ubuntu 16.04 LTS next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-base basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Yakkety Yak (16.10) Final Beta Freeze
As of about two minutes ago, yakkety has entered the final beta freeze, with a goal of releasing Final Beta images sometime late Thursday. Due to a rocky start on this beta with landing a last-minute kernel and a few other hiccups, it's possible the actual release will happen on Friday morning instead of Thursday night, but let's aim for the Thursday release and see how we do. The queue freeze will last from now until final release in October, which means that all seeded packages will now need a spot-check and review in the queue from a release team member before they are let into the archive. As with the previous releases, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. If you find the bot is blocking an upload that you think should have been auto-accepted, let us know and we'll sort it out. I will be spinning a set of beta candidates right now which I encourage people to get to testing ASAP for their favourite flavour(s) as they come off the line. Happy bug-hunting from now until the final release, and please do help out and test ISOs, netboot, etc, where you can and let us know what's broken in your environment(s). On behalf of the Ubuntu Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Yakkety Yak (16.10) Final Freeze
As of now, yakkety has entered the Final Freeze period in preparation for the final release of Ubuntu 16.10 next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-base basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Zesty Zapus (17.04) Final Beta Freeze
As of about two minutes ago, zesty has entered the final beta freeze, with a goal of releasing Final Beta images sometime late Thursday. The queue freeze will last from now until final release in April, which means that all seeded packages will now need a spot-check and review in the queue from a release team member before they are let into the archive. As with the previous releases, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. If you find the bot is blocking an upload that you think should have been auto-accepted, let us know and we'll sort it out. I will be spinning a set of beta candidates after proposed-migration has settled later tonight which I encourage people to get to testing ASAP for their favourite flavour(s) as they come off the line. Happy bug-hunting from now until the final release, and please do help out and test ISOs, netboot, etc, where you can and let us know what's broken in your environment(s). On behalf of the Ubuntu Release Team, Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Zesty Zapus (17.04) Final Freeze
As of now, zesty has entered the Final Freeze period in preparation for the final release of Ubuntu 17.04 next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-base basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Anticipating abundant anonymous aardvarks in the Ubuntu archive.
The opening of the next release will begin sometime next week, with various changes to the packaging toolchain, notably a large dpkg merge with some buildflags and buildinfo bits, and a move to the upstream implementation of ddebs in debhelper. Currently, however, we are, by decree of our sabdfl (who might be having too much fun reading the dictionary's entire A section), taking a much-needed and well-deserved long weekend. So, if you're super keen to get working, by all means, you can prep your merges locally or in PPAs, and be ready to blat it all at the archive, but I would suggest that we all take some time to go hang out outside, remind ourselves that there are things other than Linux distributions and Free Software and aruging^Wdebating on IRC. Mark told me to make this email clever and include lots of "A" words, so the remainder of this email is dedicated to that: A AA AAA A AA Actually, I've got nothing. Have a good weekend, everyone, and we can all look forward to an exciting and productive AA/17.10 cycle. ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Artful Aardvark open for development
Artful Aardvark has been open since Friday, but it's been noted that since doko's on vacation, and I passed out after opening the archive, no one got around to sending the announcement email. Artful opened with two major packaging toolchain changes, both of which should be mostly transparent: - ddebs are now generated using the upstream debhelper code, and you'll notice that pkg-create-dbgsym gets punted out of your build chroots on upgrade. If you run into any ddeb issues that arise from this, please file bugs and/or poke me directly. - dpkg now produces .buildinfo files by default for all uploads, including source builds. This should, again, be mostly a no-op for you, but there is one gotcha, which is that multiple '-nc' runs of dpkg-buildpackage -S will produce a debian/files in your source that shouldn't be there. We've been discussing how to eradicate that upstream, but if you care deeply about cruft, watch out for that. Of future note, we will be evaluating enabling PIE by default on all of our architectures (which will affect i386, armhf, and arm64), and assuming those discussions go as planned, this should happen in a month or two. This will bring us in line with Debian in that regard, which should make life a little bit easier for evaluating FTBFS bugs between the two distros. autosyncs will be turned on shortly, and the buildd queues will fill up and take a few days (probably) to drain, so do be slightly patient while waiting to see what needs sorting out in proposed-migration. Also, of note, we ended last cycle with all our "problem" reports completely empty. That means the archive had no out of date binaries, and everything was installable. This is not a situation we intend to regress, so before asking a release team member to "force" anything in to artful, understand that forcing implies breaking this state, and there has to be a better way. Please, find the better way. Happy merging, everyone, and may the Aardvarks be ever in your favour. ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Artful Aardvark (17.10) Final Freeze
As of now, artful has entered the Final Freeze period in preparation for the final release of Ubuntu 17.10 next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-base basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Bionic Beaver (18.04 LTS) Final Freeze
As of nowish, bionic has entered the Final Freeze period in preparation for the final release of Ubuntu 18.04 LTS next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-base basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Cosmic Cuttlefish (18.10) Beta Freeze
As of about two minutes ago, cosmic has entered the beta[1] freeze, with a goal of releasing Beta[1] images sometime late Thursday. The queue freeze will last from now until final release in October, which means that all seeded packages will now need a spot-check and review in the queue from a release team member before they are let into the archive. As with the previous releases, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. If you find the bot is blocking an upload that you think should have been auto-accepted, let us know and we'll sort it out. I will be spinning a set of beta candidates after proposed-migration has settled later tonight which I encourage people to get to testing ASAP for their favourite flavour(s) as they come off the line. Happy bug-hunting from now until the final release, and please do help out and test ISOs, netboot, etc, where you can and let us know what's broken in your environment(s). On behalf of the Ubuntu Release Team, Adam Conrad [1] Formerly known as Final Beta, but we now only have one beta per cycle, having removed the opt-in beta from the schedule. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Cosmic Cuttlefish (18.10) Final Freeze
As of nowish, cosmic has entered the Final Freeze period in preparation for the final release of Ubuntu 18.10 next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-base basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Disco Dingo (to be 19.04) Feature Freeze
As per the release schedule, Disco Dingo is now in Feature Freeze. Ideally, you will all now be focusing on bug fixing and not on getting new features into the release however, if necessary, please follow the process for freeze exceptions: https://wiki.ubuntu.com/FreezeExceptionProcess As is the custom, packages that have been uploaded to cosmic-roposed prior to the feature freeze deadline, but have gotten stuck there, remain candidates for fixing between now and release. Remember that version strings don't matter for Feature Freeze. If you upload a new upstream release and it has no new features than you don't need an exception. If you add a debian/patch that adds a new feature, or enable one via build flags then you do. We care about the content of the archive, not about precisely how things got there. Happy bugfixing, ... Adam -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Disco Dingo (19.04) Beta Freeze
As of about two minutes ago, disco has entered the beta[1] freeze, with a goal of releasing Beta[1] images sometime late Thursday. The queue freeze will last from now until final release in April, which means that all seeded packages will now need a spot-check and review in the queue from a release team member before they are let into the archive. As with the previous releases, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. If you find the bot is blocking an upload that you think should have been auto-accepted, let us know and we'll sort it out. I will be spinning a set of beta candidates after proposed-migration has settled this afternoon which I encourage people to get to testing ASAP for their favourite flavour(s) as they come off the line. Happy bug-hunting from now until the final release, and please do help out and test ISOs, netboot, etc, where you can and let us know what's broken in your environment(s). On behalf of the Ubuntu Release Team, Adam Conrad [1] Formerly known as Final Beta, but we now only have one beta per cycle, having removed the opt-in beta from the schedule. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Disco Dingo (19.04) Final Freeze
As of seventeen seconds ago, disco has entered the Final Freeze period in preparation for the final release of Ubuntu 19.04 next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-case basis. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Eoan Ermine (19.10) Beta Freeze
As of several minutes ago, eoan has entered the beta[1] freeze, with a goal of releasing Beta[1] images sometime late Thursday. The queue freeze will last from now until final release in October, which means that all seeded packages will now need a spot-check and review in the queue from a release team member before they are let into the archive. As with the previous releases, we have a bot in place that will accept uploads that are unseeded and don't affect images. Don't take this as an open invitation to break Feature Freeze on those components, this is just to reduce the burden on the release team, so we only review the uploads that need very serious consideration. If you find the bot is blocking an upload that you think should have been auto-accepted, let us know and we'll sort it out. I will be spinning a set of beta candidates after proposed-migration has settled this evening which I encourage people to get to testing ASAP for their favourite flavour(s) as they come off the line. Happy bug-hunting from now until the final release, and please do help out and test ISOs, netboot, etc, where you can and let us know what's broken in your environment(s). On behalf of the Ubuntu Release Team, Adam Conrad [1] Formerly known as Final Beta, but we now only have one beta per cycle, having removed the opt-in beta from the schedule. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Eoan Ermine (19.10) Final Freeze
Sometime in the last 24 hours, our internal alarms should have all gone off and told us that Eoan final freeze is upon us[1], and we're headed into the final stretch toward the Ubuntu 19.10 release next week. The current uploads in the queue will be reviewed and either accepted or rejected as appropriate by pre-freeze standards, but anything from here on should fit two broad categories: 1) Release critical bugs that affect ISOs, installers, or otherwise can't be fixed easily post-release. 2) Bug fixes that would be suitable for post-release SRUs, which we may choose to accept, reject, or shunt to -updates for 0-day SRUs on a case-by-case basis. This second case should have SRU-style bugs filed with the appropriate template, referenced in changelog. For unseeded packages that aren't on any media or in any supported sets, it's still more or less a free-for-all, but do take care not to upload changes that you can't readily validate before release. That is, ask yourself if the current state is "good enough", compared to the burden of trying to fix all the bugs you might accidentally be introducing with your shiny new upload. We will shut down cronjobs and spin some RC images late Friday or early Saturday once the archive and proposed-migration have settled a bit, and we expect everyone with a vested interest in a flavour (or two) and a few spare hours here and there to get to testing to make sure we have another uneventful release next week. Last minute panic is never fun. On behalf of the Ubuntu Release Team, ... Adam Conrad [1] What? No alarm for you? Yeah, me neither. I suggest we complain. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
