Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-pmc] Late update of the Libra contribution to the Indigo update site

As PMC's Planning Council rep (and, luckily enough for WTP, authorized for
quick approvals for aggregation :) I will include this in the 2/16, Noon
Eastern respin ... seems "leaf" enough to have no chance to effect others.

I do think something went wrong with our WTP "scheduling" as printed in
status meeting notes, since it says "2/16 RC4 (final) M build" (and, has
for a while, so you think I would have noticed it was wrong :( ... so, not
sure how that happened, or how to improve ... but, guess if that is our
worst problem then we are not doing too bad.


From:	"Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
To:	David M Williams/Raleigh/IBM@IBMUS,
Cc:	"wtp-pmc@xxxxxxxxxxx" <wtp-pmc@xxxxxxxxxxx>
Date:	02/16/2012 09:29 AM
Subject:	Re: [wtp-pmc] Late update of the Libra contribution to the
            Indigo	update site
Sent by:	wtp-pmc-bounces@xxxxxxxxxxx

Hi David,

No, I can't blame the infrastructure problems :)
I am adding the WTP-PMC list.

Dear WTP PMC members, could you read the mail thread below and vote for
another respin of the Indigo aggregator to include the Libra Indigo SR2

Libra has only few bugfixes [1] for SR2 and they are not critical. However,
it would be nice to release them with the Indigo SR2 train, because they
would help adopters to build on top of the OSGi Enterprise story.

I didn?t realize it would be so complex to trigger another build of the
aggregator. I don?t believe that EPP packages are really affected. Libra is
not included in any EPP package - it is just part of the Common Discovery
Site. AFAIK, there isn't any Eclipse project that depends on Libra.

Patch build is not really an option, especially for adopter's products that
are delivered as Add-On . Actually we have these changes released in Indigo
SR2 compatible p2 repository, but installing the version from there would
be an unintuitive extra effort for users that may happen when they hit the
problem and contact the adopter.



-----Original Message-----
From: David M Williams [mailto:david_williams@xxxxxxxxxx]
Sent: 16 февруари 2012 г. 15:47 ч.
To: Raev, Kaloyan
Subject: Re: Late update of the Libra contribution to the Indigo update

Hi Kaloyan,

Sounds like you can't even blame it on the infrastructure problems
yesterday? :)

Technically, the answer is "yes", but ... this should go though the proper
channels, first to WTP-PMC list, to make sure they agree, then to your PMC
planning council rep (me :) to take forward to planning council, etc. (or,
for me to make a "command decision").

Please read some discussion about a Dali bug where we discussed this

If you do want to request a respin, you should mention the specific bugs
fixed (and try to make them sound blocking or critical (maybe just
collectively?), who/what might need to retest and if effects EPP packages
(which, I know is "yes").  Or, is it possible to include in the patch
build, for Dali?

I personally don't mind .... and I think another project will be requesting
a respin (I am still trying to clarify ... notes might be coming out of
order) I just want to make sure it goes through the right process.


From:		 "Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
To:		 David M Williams/Raleigh/IBM@IBMUS,
Date:		 02/16/2012 05:19 AM
Subject:		 Late update of the Libra contribution to the Indigo
update site

Hi David,

I apologize, but I?ve just realized that the Indigo Build was fixed to the
Indigo SR1 release of Libra. I thought I had put a pointer to the latest
maintenance build, but I was wrong.

I?ve just updated the Indigo Build to point to the Indigo SR2 release of
Libra. Is it possible to trigger a new build of the Indigo Aggregator?

wtp-pmc mailing list

Back to the top