Re: [cross-project-issues-dev] Ready for Mars.2 ?

["David M Williams" <david_williams@xxxxxxxxxx>]

Thanks to all to pointing out that I was
making an incorrect statement about "all files changed". 
I made two errors: First, I forgot that
we did a special rebuild, for someone, so the "very last build"
had a set of URL's that were not original, but pointed to "what we
had already", while we rebuilt for that one project. 
If I correct for that, there were about
45 files that changed -- really, 35 projects did not change at all? Lucky
you! But that is a lot of "sleepers". :) 
Just kidding about project's sleeping.
What I was *trying* to do was see if any projects were basically "defunct"
... or had really "lost communication" with the Train's dates
... but turns out that I can not do that by looking at the files. 

My second mistake (sort of) was counting
"any change" as a change, whereas some them, such as GEF, were
simply to change their URL to their permanent one, but no actual change
in content. So, that might mean even fewer than 45 did, but, as some used
to remind me, some project's have their b3aggrcon files specified so loose,
they could change their content a lot, and never change the file, so looking
at the file is a bad idea all the way around. [That is, one reason why
we "changed the rule" so that the files need to be more specific
for Neon]. 

Apologies for the noise that minor comment
made -- but I learned (or, was reminded) of a lot. 





From:      
 Alexander Nyßen <nyssen@xxxxxxxxx>
To:      
 Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>, 
Date:      
 02/04/2016 02:29 AM
Subject:    
   Re: [cross-project-issues-dev]
Ready for Mars.2 ?
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Hi David,

I was wondering about your first statement also, as GEF
is not contributing something new to Mars.2 either (we are fully concentrating
on our 4.0.0 release for Neon). Our contribution to Mars.2 should be the
same as that to Mars, and as far as I can see that is indeed the case.

Regards
Alexander

Am 04.02.2016 um 07:08 schrieb Ed Willink <ed@xxxxxxxxxxxxx>:

Hi David

On 03/02/2016 22:29, David M Williams wrote:
- Every contribution file has changed
since Mars.1. Also good. (i.e. no projects are just sleeping and forgot
to update :) 

You might want to review your query. qvtd.b3aggrcon was
last changed by me on 26 June, and by you on 14 July.

We are certainly not sleeping, and did not forget to update. Just working
very hard to support the functionality required for graduation to 1.0.0.
And ... worst of all, IMHO, some "old"
third party jars are still being used, which implies to me someone is not
using the latest version of Orbit (R20151221205849). 
But if a project has no maintenance to contribute, I thought
no rebuild/contribution was required and so of course an old Orbit would
be in use. (I don't think that QVTd imposes tight bounds on Orbit contributions.)

    Regards

        Ed Willink
_______________________________________________
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

--
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, Dr. Georg Pietrek, Jens
Trompeter, Sebastian Neus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer
Fiorentino


[attachment "signature.asc"
deleted by David M Williams/Raleigh/IBM] _______________________________________________
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