Le lundi 23 novembre 2015, à 13:17 +0100, Ihar Hrachyshka a écrit : > Vincent Untz <vu...@suse.com> wrote: > > >Hi, > > > >I know 2014.2.4 is (in theory) the last juno release, but I'd still > >expect to see a post-release bump to 2014.2.5 in git, to avoid any > >confusion as to what lives in git. This is especially useful if people > >build new tarballs from git. > > > >Any objection against this, before I send patches? :-) > > > >Cheers, > > > >Vincent > > I probably miss something, but why do we care about what is in the > branch now that we don’t plan to merge anything more there? Is it to > accommodate for downstream consumers that may want to introduce more > patches on top of the upstream tag?
As I said: because people might keep generating tarballs from git, and they'd expect to have a version that is correct. Yes, this is mostly downstreams. (And not necessarily to introduce more patches, but just to reflect the reality). I would also argue that we care because we're leaving git in a state that is kind of wrong (since the version is not correct). Cheers, Vincent -- Les gens heureux ne sont pas pressés. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
