Re: [cross-project-issues-dev] Wait ... don't release yet! ... delay one

[Doug Schaefer <dschaefer@xxxxxxx>]

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.

It's a pretty troubling situation. The community shouldn't be taking this lightly.

Sent from my BlackBerry 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 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 fix for bug 391377 that Chuck Bridgham has mentioned.

 

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

 

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Matthias Sohn
Sent: Friday, February 22, 2013 11:34 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 Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx>

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 'required.*git.*2\.3' | less

 

   <unit id='org.eclipse.mylyn.github.core' version='2.3.0.201302130906'>

        <required namespace='java.package' name='org.eclipse.egit.core' range='[2.3.0,2.4.0)'/>

        <required namespace='java.package' name='org.eclipse.egit.github.core' range='[2.3.0,2.4.0)'/>

[…]

<unit id='org.eclipse.mylyn.github.ui' version='2.3.0.201302130906'>

        <required namespace='java.package' name='org.eclipse.egit.core' range='[2.3.0,2.4.0)'/>

        <required namespace='java.package' name='org.eclipse.egit.core.op' range='[2.3.0,2.4.0)'/>

[…]

   <unit id='org.eclipse.egit.mylyn.ui' version='2.3.0.201302130906'>

        <required namespace='java.package' name='org.eclipse.egit.core' range='[2.3.0,2.4.0)'/>

        <required namespace='java.package' name='org.eclipse.egit.core.synchronize' range='[2.3.0,2.4.0)'/>

 

That should be all dependencies onto egit-2.3.

I think that egit.mylyn.ui comes from egit itself, but where does the mylyn github feature actually come from ?

 

yes, egit.mylyn.ui is egit's mylyn integration and comes with egit

 

mylyn github feature is the Mylyn GitHub connector which is part of the EGit contribution since it's

developed in the EGit project. So if the EGit contribution is rolled back to SR1 this would include

rolling back the Mylyn GitHub connector to 2.1, same holds true for 2.2.0 since all these features

come in the same egit.b3aggrcon file.

 

--

Matthias

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev