After some painful conversation with the Planning Council members, the
conclusion was to delay the release 1 week, but not do a full respin, to
only revert the EGit contribution.
The plan is to redo the common repository and EPP packages, with the EGit
contribution reverted to what it was in
Of Matthias Sohn
Sent: Friday, February 22, 2013 12:15 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay
one week, Friday 3/1
2013/2/22 David M Williams david_willi...@us.ibm.com
After some painful conversation with the Planning Council
Subject:Re: [cross-project-issues-dev] Wait ... don't release yet!
... delay one week, Friday 3/1
Sent by:cross-project-issues-dev-boun...@eclipse.org
I hate to throw a stick in the spokes, but what happens if another project
in the aggregate repository already has a min
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of John
Arthorne
Sent: Friday, February 22, 2013 1:44 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ...
delay one week, Friday 3/1
Since the new version of EGit was only introduced
The GEF and M2E bugs were also discussed. The M2E bug was perceived as a bug
that could be addressed by the project's own update repo and hot fix
process. The GEF issue is more complicated, can not be fixed by their own
update site, exactly, since part of the damage already exists in SR1.
-issues-dev-boun...@eclipse.org] On Behalf Of Konstantin
Komissarchik
Sent: Friday, February 22, 2013 9:24 PM
To: 'Cross project issues'
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay
one week, Friday 3/1
I hate to throw a stick in the spokes, but what happens
2013/2/22 Oberhuber, Martin martin.oberhu...@windriver.com
Kosta has a very good point here:
** **
moberhuber@build:/home/data/httpd/download.eclipse.org/releases/juno/201302220900
unzip -p content.jar | egrep 'unit id=|required.*eclipse..git' | grep -B
10
project issues
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay
one week, Friday 3/1
2013/2/22 Oberhuber, Martin
martin.oberhu...@windriver.commailto:martin.oberhu...@windriver.com
Kosta has a very good point here:
moberhuber@build:/home/data/httpd/download.eclipse.org
2013/2/22 Oberhuber, Martin martin.oberhu...@windriver.com
Thanks Matthias –
** **
So then in my understanding there is no contribution in Simrel outside
egit itself, that would require egit-2.3 and thus the rollback should be
fine.
Using 2.2 seems preferable to me, to get the
10 smartphone.
From: Oberhuber, Martin
Sent: Friday, February 22, 2013 5:40 PM
To: Cross project issues
Reply To: Cross project issues
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay
one week, Friday 3/1
Thanks Matthias –
So then in my understanding
2013/2/23 Doug Schaefer dschae...@qnx.com
David can correct if I'm wrong here. But the decision was to actually
remove Egit from the SR2 repo resulting in the Egit from SR1 getting picked
up instead. Egit 2.2 wasn't considered.
I didn't know that it was decided to remove egit from SR2 and
11 matches
Mail list logo
