|
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
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
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
|
This
email has been checked for viruses by Avast
antivirus software.
www.avast.com |
_______________________________________________
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]()
|
This email has been checked for viruses by Avast
antivirus software.
www.avast.com
|
_______________________________________________
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]()
|
This email has been checked for viruses by Avast antivirus software.
www.avast.com
|
|
