Hello,
I imagine the following process :
* deprecated on trunk an element and indicate since="$NextReleaseBranch"
(or somethink like that)
* When before create the new release branch like 17.11 :
** run a replaceAll $NextReleaseBranch by 17.11
** update the trunk
* Create the new stable branch
* remove all element contains with a since not on the last stable branch
on trunk
* update trunk
With this we have a new stable branch with the deprecated from the
previous stable branch (keep stability much as possible), and a trunk
cleaned of old deprecated who may introduce a potential instability but
we have the time to correct it.
Nicolas
Le 10/08/2017 à 13:46, Jacques Le Roux a écrit :
Le 10/08/2017 à 13:25, Scott Gray a écrit :
I think we've had these discussions before Jacques, I'd search the
mailing
lists and then perhaps only continue the conversation if you have
concerns
about what was agreed previously.
I'm pretty sure the policy was "remove after the next release is
out", and
actually released, not just when a branch is cut.
Oops, that's what I meant too with "deprecate code when we create the
first release of the last freezed branch".
I tried to be more precise there than in my previous sentence "remove
all deprecated code in trunk when for instance creating a new release."
But I did not notice I misused "deprecate code" for "remove deprecated
code".
I think we are on the same page and don't want to wait loo long
keeping deprecated code, first occasion is best ;)
Jacques
