| Re: [tycho-dev] Tycho 2.x.1 release? |
|
I would appreciate a 2.7.1 release which also incorporates cherry-picks of these two commits:
https://github.com/eclipse/tycho/commit/3c46a38700f08829cf4921bf6feaf7237f10e8ff Issue
#719 Performance regression with fragment additons to classpath https://github.com/eclipse/tycho/commit/7216f08bb54feddbcbcaad7170ae9417abbbb34a P2ResolverFactoryImpl:
Improve calculateDependencyFragments performance This is why we have not yet moved to 2.7.0 everywhere. In general, regarding the maintenance strategy: If there are no regressions in the latest stable release then there should be no reason not to update to it. I also do not think a 2.6.1 / 2.5.1 / … release would prevent the issue with the broken metadata. Typically it is not about specifically wanting to use that old 2.6.x / 2.5.x version. More likely you happen to check out a project that has not been touched in a while and just happens to use Tycho 2.6.x/2.6.x/… in its current state. In that case the solution should be to simply be able to upgrade to 2.7.x without any regressions and a 2.6.1 / 2.5.1 should not be necessary. From: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx>
On Behalf Of Aleksandar Kurtakov On Mon, Mar 28, 2022 at 9:53 AM Christoph Läubrich <laeubi@xxxxxxxxxxxxxx> wrote:
What you say it's true. There is just one problem and it's called "expectations" - Why have you done it for X but not for Y? Why not fix my "very important" case while you fixed these "useless" issues? There used to be maintenance fixes
for X years, why not now? and so on and on. Once people get used to certain things happening, changing smth or actually not doing smth (cause you just don't have time!) anymore leads to a great number of complains and discussions that don't create anything
else but anger and disappointment. It might be just me and my Platform experience speaking here. Overall, I'm not against doing maintenance work but I am really cautious to not be thrown in yet another replay of the same story.
Aleksandar Kurtakov Red Hat Eclipse Team |