On Wed, Dec 19, 2018 at 12:19 AM Christophe JAILLET < christophe.jail...@wanadoo.fr> wrote:
> > I thought that now that 2.5.0 has been tagged, the history of 2.5.0+ > should not be axed when backported (i.e. this change would be in 2.5.1, > but is not in 2.5.0, which is tagged, so "does exist") > You are correct in spirit, but in practice, 2.5.0 was not released, and therefore does not "exist". If the release vote for 2.5.1-alpha (or -beta) does pass, then the 2.5 clock will truly start.
