Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > You could also use `next` instead of `master`, which would make intuitive > sense because the commits that make it into that branch are slated to be > part of the next major Git version. > > And a relatively obvious name for the current `next` might be `cooking`. > > I refrained from proposing this earlier, thinking that this would be too > disruptive, but since `pu` was renamed to `seen`... Renaming 'pu' away from two-letter has a positive technical and social effect. Using 'next' for anything but what it currently means does not have any such upside and only the downside of confusing people. As to 'cooking', I am not sure. Personally I consider that the topics that are in 'next' plus those that are soon to be in 'next' are all 'cooking'. But I do not think anybody's dying to rename 'next', so...
