Re: .92 tarball deadline and hard code freeze
On Fri, Feb 28, 2020 at 10:25 am, Mart Raudsepp wrote: This sounds more like a "problem" with the distribution, not that such releases shouldn't happen. If a minor release upgrade prompts for a full system reboot, then maybe that update shouldn't be packaged up on such distros - it shouldn't mean the translations shouldn't get out the door in general in a tagged release. Fedora will continue to take all GNOME updates. Our update script isn't smart enough to conditionally decide whether a release has interesting changes or not like a human would do. Or they could be gated to all get pushed down all at once, so the reboot is made for many .4 packages, some of which have bug fixes too. That's a good point, but it's certainly also nice to have fewer total packages to update. :) (Of course, don't hesitate to release updates when you actually have bugfixes.) Also so late as .4 often seems to be more like a "oh, I haven't done any work on this module at all this cycle, so there's only translation updates - let me get at least these out for users to benefit from the translators work, but I'll not bump the minor as there have been no code changes" kind of deal too, so distros prompting reboots can include them in their next cycles updates, while others know to take them earlier. Yeah, that's a good point. I have a module in this situation, GNOME Sudoku, with only translation updates since 3.34.1. On the one hand, since there are no changes since 3.34, there's really no need to do a 3.36: I could just call the next release 3.34.2 so that 3.34 users benefit from the translation changes. On the other hand, it's probably better to avoid the extra 3.34 update, so I think I'll call it 3.36.0? Hadn't really given it much thought until now. Michael ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: .92 tarball deadline and hard code freeze
Ühel kenal päeval, N, 27.02.2020 kell 17:06, kirjutas Michael Catanzaro: > I noticed we had some 3.34.4 releases recently with no changes > except > to translations. This churn results in users being prompted to > reboot > to install updates that are not applicable except in select locales. > Since 3.36, we now have a translation deadline baked into the > schedule, > so there's no longer need to roll stable tarballs just for late > translations. (And certainly we should avoid this so late as .4.) This sounds more like a "problem" with the distribution, not that such releases shouldn't happen. If a minor release upgrade prompts for a full system reboot, then maybe that update shouldn't be packaged up on such distros - it shouldn't mean the translations shouldn't get out the door in general in a tagged release. Or they could be gated to all get pushed down all at once, so the reboot is made for many .4 packages, some of which have bug fixes too. Also so late as .4 often seems to be more like a "oh, I haven't done any work on this module at all this cycle, so there's only translation updates - let me get at least these out for users to benefit from the translators work, but I'll not bump the minor as there have been no code changes" kind of deal too, so distros prompting reboots can include them in their next cycles updates, while others know to take them earlier. Mart signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: .92 tarball deadline and hard code freeze
On Wed, Feb 26, 2020 at 3:39 pm, Michael Catanzaro wrote: Schedule: * Saturday, Feb 29: 3.35.92 tarball deadline and hard code freeze * Saturday, March 7: 3.36.0 tarball deadline * Wednesday, March 11: GNOME 3.36.0 release day Another important date is Wednesday, March 4. For the first time, we have a translation deadline, at 23:59 UTC on March 4. Please do not release any 3.36.0 tarballs before March 5 in order to give translators time to finish their work. If you can't release 3.36.0 during the tight window between March 5 and March 7, please let release team know so we can do it for you. I noticed we had some 3.34.4 releases recently with no changes except to translations. This churn results in users being prompted to reboot to install updates that are not applicable except in select locales. Since 3.36, we now have a translation deadline baked into the schedule, so there's no longer need to roll stable tarballs just for late translations. (And certainly we should avoid this so late as .4.) Thanks, Michael ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
.92 tarball deadline and hard code freeze
Hi, Just a reminder that we are getting very close to GNOME 3.36 [1]! The tarball deadline for 3.35.92 is Saturday at midnight (UTC). If you release on weekdays, please be sure to release either Thursday (tomorrow) or Friday. Normally we have a bunch of late releases on Monday and Tuesday; I'd love to see us plan ahead and release early instead of late. Reminder that hard code freeze also begins Saturday at midnight, after which all code changes for 3.36 require release team approval. The hard code freeze will ensure we don't introduce any last-minute mistakes before 3.36. Schedule: * Saturday, Feb 29: 3.35.92 tarball deadline and hard code freeze * Saturday, March 7: 3.36.0 tarball deadline * Wednesday, March 11: GNOME 3.36.0 release day Michael [1] https://wiki.gnome.org/ThreePointThirtyfive ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
