[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-dev] Tycho 3.0 release
|
Maybe I'm getting your idea wrong but Is't it the same as I have
described jsut the other way round (having a 3.x branch and master is
2.7. versus having 2.7. branch and master is 3.x)?
I won't expect much development effort on the 2.7.x if we actually
decide to prepare for 3.x ... we even can omit 2.7. and start with 3.x
right now, I just thought Alex would have a version with 2022-06 included...
If that's true we can even do:
- branch from 2.6.x release the 2.7.x branch
- switch master to 3.x now
- if 2022-06 is out update 2.7.x and cherry pick this to master (should
only be some version updates)
> No, we shouldn't, unless it's a breaking change. Anything that's not a
> "too breaking change" should go to master ASAP, as usual.
It does not break anything for me or any integration test but just in
case we want to be sure and start with 3.x soon...
Am 07.01.22 um 09:49 schrieb Mickael Istria:
On Fri, Jan 7, 2022 at 9:43 AM Christoph Läubrich <laeubi@xxxxxxxxxxxxxx
<mailto:laeubi@xxxxxxxxxxxxxx>> wrote:
Should we delay https://github.com/eclipse/tycho/pull/470
<https://github.com/eclipse/tycho/pull/470> to 3.x?
No, we shouldn't, unless it's a breaking change. Anything that's not a
"too breaking change" should go to master ASAP, as usual.
I think we can instantly start with a 3.x on master and create a 2.7.x
branch that we only use for bugfixes and final update for 2022-06
(these
should be easily cherry picked to the 3.x branch then or even
irrelevant
for it).
-100 for starting some branching workflow with cherry-pick and so on
here. It's a pain to maintain, build, release... A linear history and
single development branch scales much better and we should stick to it
unless we really have very strong reasons not to. We can prepare patches
for 3.x as pull requests, keep master targeting next release (2.7.0 now,
maybe then 2.8, 2.9...) and when we're ready to switch to 3.x, then
master becomes 3.x and the only maintained branch. Support for 2.x could
still happen -if someone cares about it which I hope won't be the case-
on a 2.x branch.
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-dev
