Re: (*) No summarized news available (was: GNOME 3.29.1 released)
On Wed, 2018-04-18 at 11:31 +0200, Kalev Lember wrote: > Something that module maintainers can do here as a fix would be to > cherry pick any 3.28.x NEWS entries to the master branch before > releasing first 3.29.x release. Hi, except it's wrong, because then a) the NEWS file doesn't describe changes in the master branch, b) I commit to both master and stable when possible, thus the NEWS file would have contain certain things multiple times. The evolution products branch in time of the 3.x.0 release, then the development happens separately in both branches. Maybe you are right that others branch later, after 3.x.1 release. I think the `ftpadmin install` also claimed the latest release was 3.28.1, which supports your hypotheses. Interestingly it can distinguish between odd and even numbered releases once there is at least one done there. > That's just needed for the first 3.29.x release, after that it should > be fine to not cherry pick news entries any more. Correct, the 3.y.2+ releases work just fine. If it's really about something in the background, then, rather than trying to find some (ugly) workarounds, that thing could be fixed or improved. I hope. I'd file a bug, but I do not know where it belongs and what that 'something in the background' actually is. Thanks and bye, Milan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: (*) No summarized news available (was: GNOME 3.29.1 released)
On 04/18/2018 09:45 AM, Milan Crha wrote: > Hi, > I'm starting a new thread here, just for an opinion on this: > > On Tue, 2018-04-17 at 16:31 -0500, mcatanzaro wrote: >> The list of updated modules and changes is available here: >> >> https://download.gnome.org/core/3.29/3.29.1/NEWS > > I opened above URL and there's "(*) No summarized news available" side- > note for two modules. In case of evolution-data-server, it corresponds > to the ftp-release-list message: > https://mail.gnome.org/archives/ftp-release-list/2018-April/msg00072.html > > But not to what had been done before the release: > https://git.gnome.org/browse/evolution-data-server/commit/?id=a55f5c3dbce3f24d2462c76f555e858ef6df2ccb > > This usually happens with the first release of the series, but not > always. Like the stable 3.28.0 has the NEWS content included: > https://mail.gnome.org/archives/ftp-release-list/2018-March/msg00101.html > > I'm wondering, am I doing anything wrong? Why other modules, like > epiphany, which also switched from 3.28.1 to 3.29.1, has its NEWS > available in Michael's URL? I'd like to improve this, but I'm not sure > whether it's in my hands at all. Could there be a bug in the script > which extracts the NEWS changes? For example, the ChangeLog doesn't > change, it simply references git log for proper branch. Does it have > any influence on this? The ChangeLog file does change with the first > stable release, due to the change of the branch: > https://git.gnome.org/browse/evolution-data-server/commit/?h=gnome-3-28=7f6c16388216840f6bbda0d98383d5c008bc8d45 I believe the way it works is that it takes the previously released module's NEWS (evolution-data-server 3.28.1) and compares it to the newly released module's NEWS (evolution-data-server 3.29.1), and then shows added lines. In this case however, the 3.29.1 NEWS file only had 3.28.0 entries (3.28.1 must have been released off a branch, so its news didn't get added to master) and when diffing those two it presumably gets a bunch of removed lines (3.28.1 entries removed) and a bunch of added lines (3.29.1 added), which confuses it. Something that module maintainers can do here as a fix would be to cherry pick any 3.28.x NEWS entries to the master branch before releasing first 3.29.x release. That's just needed for the first 3.29.x release, after that it should be fine to not cherry pick news entries any more. -- Kalev ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
(*) No summarized news available (was: GNOME 3.29.1 released)
Hi, I'm starting a new thread here, just for an opinion on this: On Tue, 2018-04-17 at 16:31 -0500, mcatanzaro wrote: > The list of updated modules and changes is available here: > > https://download.gnome.org/core/3.29/3.29.1/NEWS I opened above URL and there's "(*) No summarized news available" side- note for two modules. In case of evolution-data-server, it corresponds to the ftp-release-list message: https://mail.gnome.org/archives/ftp-release-list/2018-April/msg00072.html But not to what had been done before the release: https://git.gnome.org/browse/evolution-data-server/commit/?id=a55f5c3dbce3f24d2462c76f555e858ef6df2ccb This usually happens with the first release of the series, but not always. Like the stable 3.28.0 has the NEWS content included: https://mail.gnome.org/archives/ftp-release-list/2018-March/msg00101.html I'm wondering, am I doing anything wrong? Why other modules, like epiphany, which also switched from 3.28.1 to 3.29.1, has its NEWS available in Michael's URL? I'd like to improve this, but I'm not sure whether it's in my hands at all. Could there be a bug in the script which extracts the NEWS changes? For example, the ChangeLog doesn't change, it simply references git log for proper branch. Does it have any influence on this? The ChangeLog file does change with the first stable release, due to the change of the branch: https://git.gnome.org/browse/evolution-data-server/commit/?h=gnome-3-28=7f6c16388216840f6bbda0d98383d5c008bc8d45 Thanks and bye, Milan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.29.1 released
Hi developers, GNOME 3.29.1 is now available. If you want to compile GNOME 3.29.1, you can use the official BuildStream project snapshot. Thanks to BuildStream's build sandbox, it should build reliably for you regardless of the dependencies on your host system: https://download.gnome.org/teams/releng/3.29.1/gnome-3.29.1.tar.xz The list of updated modules and changes is available here: https://download.gnome.org/core/3.29/3.29.1/NEWS The source packages are available here: https://download.gnome.org/core/3.29/3.29.1/sources/ There are actually not very many changes to GNOME modules themselves, because not many maintainers provided updated tarballs, but there are new versions for a few applications and libraries. More frequent tarball releases would be appreciated if you have made changes in your modules, to ensure they receive early testing in development distributions. Notably, GNOME Shell was not updated in this release, which is a bit sad. There have, however, been major changes in the build metadata. Thanks to Abderrahim Kitouni, we've switched the base system used for building GNOME from one based on Debian packages to one based on the freedesktop SDK. This is a major step towards using gnome-build-meta to build our Flatpak runtimes. There is one notable regression: Rust is no longer available, so we had to downgrade librsvg. Help in restoring support for Rust would be most welcome in this issue: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/100 Finally, zenity has been removed from this release, at long last. Please make sure your modules do not use it. WARNING! This release is a snapshot of development code. Although it is buildable and usable, it is primarily intended for testing and hacking purposes. GNOME uses odd minor version numbers to indicate development status. For more information about 3.29, the full schedule, the official module lists and the proposed module lists, please see our 3.29 wiki page: https://www.gnome.org/start/unstable Michael ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
