What ever seems fit then :-)
I just think we should start wit 3.x ASAP to get rid of the old stuff
and have enough time to find real regressions/problems and also some of
the refactoring will take some time.
Having 3.0 stream earlier is OK with me. We will have to get 2.x release with p2/ecj/etc. from 2022-03 release for bugfixes and/or PGP enhancements. So probably 3.0 branch as soon as someone wants to land smth in it and merge that branch to master in April once we get 2.x release based on 2022-03 would be best of both worlds.
Am 07.01.22 um 10:33 schrieb Mickael Istria:
>
>
> On Fri, Jan 7, 2022 at 10:30 AM Christoph Läubrich
> <laeubi@xxxxxxxxxxxxxx <mailto:laeubi@xxxxxxxxxxxxxx>> wrote:
>
> We have a planned release for 2.6.x at end of month is it good idea to
> have two parallel releases?
>
>
> That's why I wasn't so enthusiast about doing a 2.6.x release, there was
> too much value to be delivered soon.
> Let's complete 2.6 and I'll start 2.7 soon after, no strong emergency.
>
> Would it not be better to have it in snapshots (platform uses tycho
> snapshots afaik)
>
>
> It's already in Snapshots and Platform will start using those snapshots
> ASAP.
>
> or is there any immediate reason to have an official
> release?
>
>
> There are critical changes for PGP adoption story and your patch
> allowing to integrate with other non-Tycho modules is extremely
> valuable. Such value should be "unleashed" to the wider world ASAP.
>
> _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-dev
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-dev
