[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-dev] Tycho 3.0 release
|
That's why I'd like to switch master to 3.x right now and let 2.7.x be a
real maintenance of 2.6.x to get latest platform updates in.
One could even argue that we don't even consider to release 2.7.x unless
someone else likes to provide the necessary fixes, it is not really
required to upgrade anyways if there are no new features tycho needs to use.
Am 07.01.22 um 10:07 schrieb Mickael Istria:
On Fri, Jan 7, 2022 at 10:02 AM Christoph Läubrich
<laeubi@xxxxxxxxxxxxxx <mailto:laeubi@xxxxxxxxxxxxxx>> wrote:
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)?
Names do matter as it shows where development and contributions are most
welcome (it's always master)
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...
I don't mind if we start 3.x now, I don't mind about the version
numbers, even breaking API consumers in "minor" versions if there is
substantial value to balance this inconvenience, as long as we don't
start playing with multiple branches. You tried it for the 1st time with
2.6 and it looks like much more trouble and work than what usually
happens when we don't branch, so it we having 2 active branches for 6
months, it's going to be a nightmare while the current flow of
development in Tycho is really fast, we'd end up wasting multiple hours
a week cherry-picking stuff from one branch to the other, I don't have
such time to waste.
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-dev
