Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] Fwd: [Bug 371680] incomplete p2 metadata for projects with RELEASE version

we have several internal projects waiting to do a release which uses tycho 0.14.

My proposal is to stage 0.14.1 on Friday and release it on Monday.
As of now only the fix for 371680 would go into 0.14.1.
Let me know up to Friday morning CET which other fixes (if any) you want downported.

Objections?

Regards,
Jan

-----Original Message-----
From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
Sent: Montag, 20. Februar 2012 15:44
To: Tycho developers list; Tycho developers list
Subject: Re: [tycho-dev] Fwd: [Bug 371680] incomplete p2 metadata for projects with RELEASE version

That's my point. Lets give people more time to try 0.14 before we decide what fixes should go in 0.14.1. 

I also think majority of users wait for an 'official' release of a new version, so the real 0.14 testing started when the artifacts hit Central.
-- 
Sent from my SGS

"Sievers, Jan" <jan.sievers@xxxxxxx> wrote:

>I think the staging tests for 0.14.0 were as thorough as we could make
>them for a staging period of one week (CDT, jboss tools, sigasi
>reported no regressions).
>
>Unfortunately we missed
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=371680 , probably because
>everyone tested with  -SNAPSHOT versions
>and nobody tested a release scenario.
>
>To summarize, tycho 0.14.0 will work just fine as long as you develop,
>but when you try to release, the build produces different/incomplete
>metadata (and you may notice too late after you released already).
>AFAICT there is no workaround, so basically I can't release a project
>when using tycho 0.14.0.
>
>From my point of view this justifies a 0.14.1 patch release.
>
>For now I don't see other regressions in 0.14.0 worth downporting a
>fix.
>
>Jan
>
>-----Original Message-----
>From: tycho-dev-bounces@xxxxxxxxxxx
>[mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
>Sent: Freitag, 17. Februar 2012 18:32
>To: Tycho developers list
>Subject: [tycho-dev] Fwd: [Bug 371680] incomplete p2 metadata for
>projects with RELEASE version
>
>Lets wait another week or two to give users the chance to actually test
>0.14 (I doubt many have tried 0.14.0-SNAPSHOT, to be honest). Then we
>can decide if we need 0.14.1 and what changes we need to backport from
>0.15.
>
>--
>Regards,
>Igor
>
>-------- Original Message --------
>Subject: [Bug 371680] incomplete p2 metadata for projects with RELEASE 
>version
>Date: Fri, 17 Feb 2012 17:26:36 +0000
>From: bugzilla-daemon@xxxxxxxxxxx
>To: igor@xxxxxxxxxxxxxx
>
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=371680
>Product/Component: Tycho / Core
>
>Tobias Oberlies <tobias.oberlies@xxxxxxx> changed:
>
>            What    |Removed                     |Added
>----------------------------------------------------------------------------
>            Severity|normal                      |critical
>
>--- Comment #3 from Tobias Oberlies <tobias.oberlies@xxxxxxx>
>2012-02-17 
>12:26:36 EST ---
>As far as I understand this problem, this is a pretty severe problem
>and 
>will
>lead to problems in many projects once they try to release with 0.14.0.
>It
>seems that we should release an 0.14.1 with a back-port of this fix.
>
>@Igor: What's your opinion on this (given that we do the release)?
>
>-- 
>Configure bugmail:
>https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
>------- You are receiving this mail because: -------
>You are the assignee for the bug.
>You reported the bug.
>_______________________________________________
>tycho-dev mailing list
>tycho-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/tycho-dev
>_______________________________________________
>tycho-dev mailing list
>tycho-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/tycho-dev

_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-dev


Back to the top