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
