I agree that deleting EOM branches is the best approach (with tags).
Having a branch for an EOM line doesn't make sense since a branch signifies
(and/or promotes) active development.
Having a tag signifies that this line is static and is a point-in-time
pointer to the branch. In the worst case scen
I think delete EOM branches and keeping only tags sounds reasonable, but
ain't much experienced on releases management, honestly. Do we know what's
the standard among most apache projects? Maybe we could follow those?
Em seg, 15 de jul de 2019 às 15:27, Josh Elser escreveu:
> (Sending this note
(Sending this note for Busbey as he's chasing other stuff)
He had sent a note to private asking what had happened to branch-1.2. In
my cleanup of old branches to try to reduce our Jenkins usage at the
request of Infra, I created a git tag instead of the branch: branch-1.2
was deleted remotely,
