[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today
|
Hi Alexander,
I've enabled the e(fx)clipse runtime contribution from Neon.0. The
tooling contribution stays disabled until WTP is enabled as we use their
XML-Editors.
Tom
On 09.08.16 15:38, Alexander Nyßen wrote:
> I also fear that without enabling the Neon contributions the
> bootstrapping is not to be done. We are virtually postponing it all to
> Wednesday, when we will have to perform a piece-by-piece integration
> (probably on the level of individual features), hoping that all projects
> actually contribute something. GEF for instance depends on e(fx)clipse
> and Xtext, which - if I recollect correctly - have not even stated their
> intention to participate in Oxygen. I am keeping my fingers crossed...
>
> Regards
> Alexander
>
>> Am 09.08.2016 um 14:36 schrieb Ed Willink <ed@xxxxxxxxxxxxx
>> <mailto:ed@xxxxxxxxxxxxx>>:
>>
>> Hi
>>
>> Co-ordination would be good, but we have a new policy whose
>> consequences do not seem to have been appreciated.
>>
>> Indeed it is +2, and I see no successful +1 contributions. Just GEF
>> that enabled a Neon contribution to reduce its small contribution to
>> the overall deadlock.
>>
>> Regards
>>
>> Ed Willink
>>
>> On 09/08/2016 13:27, Kaloyan Raev wrote:
>>> Hi Ed,
>>>
>>> Can't all these projects coordinate and make the necessary
>>> contributions within a short time frame without leaving master broken
>>> for a long time?
>>>
>>> It's already M1 +2 date and the rest of the projects should be able
>>> to do their contributions.
>>>
>>> Kaloyan
>>> ------------------------------------------------------------------------
>>> *From:* cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx> on
>>> behalf of Ed Willink <ed@xxxxxxxxxxxxx>
>>> *Sent:* Tuesday, August 9, 2016 3:20:07 PM
>>> *To:* cross-project-issues-dev@xxxxxxxxxxx
>>> *Subject:* Re: [cross-project-issues-dev] GEF Oxygen M1 contribution
>>> only partially today
>>>
>>> Hi
>>>
>>> Feel free, but we have a policy problem.
>>>
>>> The earlier discussion was on Xtext dependencies.
>>>
>>> The build is currently failing because OCL depends on UML2 which is
>>> missing.
>>>
>>> Once UML2 is fixed, OCL and/or UML2 will fail because EMF and/or
>>> Xtext is missing.
>>>
>>> We therefore have three choices.
>>>
>>> Green all the way: No contribution is enabled till ALL prerequisites
>>> are enabled. This will be very slow because of the recursive
>>> dependencies, because relengs are not super-responsive, because it is
>>> August, because some projects never contribute at M1, and because M1
>>> used to be two rather than one weeks long.
>>>
>>> Red till green: contribute as normal, so that the validator
>>> identifies the missing contributions.
>>>
>>> The old way. Neon contributions are enabled by default.
>>>
>>> I think the old way was better, but given that we are improving, I
>>> see contribution enabling as appropriate so that the missing
>>> contributions are highlighted.
>>>
>>> AFAIAA all OCL's dependencies have declared intent so OCL can be
>>> enabled and that is what I have done.
>>>
>>> Regards
>>>
>>> Ed Willink
>>>
>>> On 09/08/2016 13:09, Kaloyan Raev wrote:
>>>> Hi folks,
>>>>
>>>> I don't want to break the party, but your recent changes, pushed
>>>> directly to master, broke the validation build. Thus, everyone else
>>>> who follow the clean process of contributing via Gerrit is blocked
>>>> at the moment.
>>>>
>>>> I am going to revert the last changes one by one until I get a clean
>>>> validation build.
>>>>
>>>> Please contribute your next changes via Gerrit.
>>>>
>>>> Thanks,
>>>> Kaloyan
>>>> ------------------------------------------------------------------------
>>>> *From:* cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx> on
>>>> behalf of Ed Willink <ed@xxxxxxxxxxxxx>
>>>> *Sent:* Monday, August 8, 2016 8:39:57 PM
>>>> *To:* cross-project-issues-dev@xxxxxxxxxxx
>>>> *Subject:* Re: [cross-project-issues-dev] GEF Oxygen M1 contribution
>>>> only partially today
>>>>
>>>> Hi
>>>> XText has declared intent. XText releases asynchronously, so it is
>>>> very likely that Xtext 2.10 crosses the boundary.
>>>> It seems unhelpful that you have inhibited aggregation contributions
>>>> just because the XText releng has not realized how much trouble your
>>>> enabled=false is causing.
>>>> I'll enable OCL so that things improve as soon as XText and friends
>>>> appear.
>>>> Regards
>>>> Ed Willink
>>>> On 08/08/2016 18:27, David M Williams wrote:
>>>>> > Can we have the Neon contributions available as in previous years?
>>>>>
>>>>> Projects can do that, if they want -- as long as it is still "fits
>>>>> in".
>>>>> But it is up to the project. They need to "declare intent" and
>>>>> provide a release record, AND THEN re-enable what every
>>>>> contribution they want to make.
>>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> From: Ed Willink <ed@xxxxxxxxxxxxx>
>>>>> To: cross-project-issues-dev@xxxxxxxxxxx,
>>>>> Date: 08/08/2016 12:13 PM
>>>>> Subject: Re: [cross-project-issues-dev] GEF Oxygen M1
>>>>> contribution only partially today
>>>>> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> Hi
>>>>> OCL too cannot be enabled until Xtext is enabled.
>>>>> I feel that this attempt to bootstrap from nothing is going to make
>>>>> for some very tight late coordination.
>>>>> Can we have the Neon contributions available as in previous years?
>>>>> If enabled="false" is required to enforce announced participation,
>>>>> surely it would be better to apply it just after M2 to all projects
>>>>> that have made no SimRel commit since Neon?
>>>>> Regards
>>>>> Ed Willink
>>>>>
>>>>> On 08/08/2016 16:34, Alexander Nyßen wrote:
>>>>> Hi all,
>>>>>
>>>>> I have just re-enabled the GEF repository for Oxygen and made
>>>>> available the Neon release version of GEF-legacy (Draw2d/GEF (MVC)
>>>>> 3.x, Zest 1.x) to enable downstream projects that depend on it. The
>>>>> GEF (formerly known as GEF4) contribution to M1 is already prepared
>>>>> as well, but I had to disable it for now because it depends on
>>>>> downstream projects (namely e(fx)clipse and Xtext) that have not
>>>>> updated their contributions yet. GEF will thus not be available
>>>>> today but on Wednesday.
>>>>>
>>>>> Regards,
>>>>> Alexander
>>>>> --
>>>>> Dr. Alexander Nyßen
>>>>> Dipl.-Inform.
>>>>> Principal Engineer
>>>>>
>>>>> Telefon: +49 (0) 231 / 98 60-202
>>>>> Telefax: +49 (0) 231 / 98 60-211
>>>>> Mobil: +49 (0) 151 / 17396743
>>>>> _
>>>>> __http://www.itemis.de_ <http://www.itemis.de/> _
>>>>> __alexander.nyssen@itemis.de_ <mailto:alexander.nyssen@xxxxxxxxx>
>>>>>
>>>>> itemis AG
>>>>> Am Brambusch 15-24
>>>>> 44536 Lünen
>>>>>
>>>>> Rechtlicher Hinweis:
>>>>>
>>>>> Amtsgericht Dortmund, HRB 20621
>>>>>
>>>>> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus
>>>>>
>>>>> Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus,
>>>>> Jennifer Fiorentino
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cross-project-issues-dev mailing list
>>>>> _cross-project-issues-dev@eclipse.org_
>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>> To change your delivery options, retrieve your password, or
>>>>> unsubscribe from this list, visit
>>>>> _https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> This email has been checked for viruses by Avast antivirus software. _
>>>>> __www.avast.com_
>>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>>
>>>>> _______________________________________________
>>>>> cross-project-issues-dev mailing list
>>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>>> To change your delivery options, retrieve your password, or
>>>>> unsubscribe from this list, visit
>>>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cross-project-issues-dev mailing list
>>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>> Avast logo
>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>
>>>> This email has been checked for viruses by Avast antivirus software.
>>>> www.avast.com
>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> cross-project-issues-dev mailing list
>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>> Avast logo
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>
>>> This email has been checked for viruses by Avast antivirus software.
>>> www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>>
>> ------------------------------------------------------------------------
>> Avast logo
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>> This email has been checked for viruses by Avast antivirus software.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>>
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@xxxxxxxxxxx
>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> --
> Dr. Alexander Nyßen
> Dipl.-Inform.
> Principal Engineer
>
> Telefon: +49 (0) 231 / 98 60-202
> Telefax: +49 (0) 231 / 98 60-211
> Mobil: +49 (0) 151 / 17396743
>
> http://www.itemis.de
> alexander.nyssen@xxxxxxxxx <mailto:alexander.nyssen@xxxxxxxxx>
>
> itemis AG
> Am Brambusch 15-24
> 44536 Lünen
>
> Rechtlicher Hinweis:
>
> Amtsgericht Dortmund, HRB 20621
>
> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus
>
> Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus,
> Jennifer Fiorentino
>
>
>
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
--
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
