Am 05.11.26 um 12:14 schrieb Jim Jagielski:
Since the focus is on getting AOO5 out, we should assume that anything added to
`trunk` is a candidate for backport to `AOO50X`.
If there are long-term, "experimental" work efforts, then we don't want to stop
them, but, IMO at least, maybe they should be done in branches off of `trunk` and not
folded _into_ trunk. One reason why work on 4.2.X stagnated was because of that exact
reason: that trunk and AOO42X just diverged way, way too much.
Does that make sense?
in theory yes. It would work good when every dev thinks / remember
always and in every situation this role - also in 12 month.
To support this, maybe it be better when we have a role that takes care
of the release management in general.
One task is to keep an eye on the commits of every branch inkl. trunk.
As an increase, every dev has to ask if committing / merging in a branch
is ok, before doing so.
My 2 ct.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
