Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-21 Thread Nick Boldt
Just to follow up on this thread, here's an update on the RSE builds.

I've done some refactoring of the existing Hudson jobs, which are now back
to green on the new JIPP:

https://ci.eclipse.org/tm/view/rse/

Here is the latest build's results (as update site zip or folder):

https://ci.eclipse.org/tm/view/rse/job/rse_master/
lastSuccessfulBuild/artifact/rse/site/target/

If someone on this list would like to try installing it and see if
anything's not working, that's be awesome. If EMO and Planning Council
folks approve, I'd be happy to re-contribute RSE into the simrel for
Photon.0.M6.

Nick


On Tue, Feb 13, 2018 at 11:31 AM, Greg Watson <g.wat...@computer.org> wrote:

> I used your gmail address. The redhat one worked.
>
> Regards,
> Greg
>
>
> On Feb 13, 2018, at 11:07 AM, Nick Boldt <nickbo...@gmail.com> wrote:
>
> Which address did you use? If nickbo...@gmail.com, that's the problem. If
> nbo...@redhat.com, then a possible bug in the portal/nom process.
>
> Nick
>
> On Tue, Feb 13, 2018 at 10:19 AM, Greg Watson <g.wat...@computer.org>
> wrote:
>
>> Nick,
>>
>> I merged the change you indicated, thanks.
>>
>> I also tried to nominate you, but for some reason it says your email
>> address is not valid. The actual message is "The nominee field contains an
>> invalid user." I don't know if this is a bug in the nomination form, or you
>> need to be registered somewhere with Eclipse. Does anyone know?
>>
>> Regards,
>> Greg
>>
>>
>> On Feb 12, 2018, at 6:11 PM, Nick Boldt <nickbo...@gmail.com> wrote:
>>
>> Considering the list of open TM/RSE gerrits [1] include one that's a
>> 1-line fix for JDK 9 support, and is 2 weeks old without feedback (I just
>> posted a +1 on it)... Doug's right, there may be no one to receive my PRs
>> to updated RSE to work with Photon.
>>
>> [1] https://git.eclipse.org/r/p/tm/org.eclipse.tm
>>
>> I also commented on one that's over 5 years old and unmerged. That one
>> and all those older I suspect should be abandoned as they can't (or
>> shouldn't) be merged.
>>
>> If Kaloyan, Lars or any past TM committers [2] want to vote me in, I'll
>> clean up the open gerrits and get RSE building again in JIPP.
>>
>> [2] https://projects.eclipse.org/projects/tools.tm/who
>>
>> So... Who'd like to nominate me? :)
>>
>> --
>>
>> Nick Boldt :: http://nick.divbyzero.com
>> FB, IG, Twitter, G+, LinkedIn, Freenode: @nickboldt
>> WhatsApp: +57 311 530 2074 or +1 647 899 9879 <(647)%20899-9879>
>>
>>
>> On Feb 12, 2018 10:16 AM, "Lars Vogel" <lars.vo...@vogella.com> wrote:
>>
>> I suggest to nominate Nick as TM committer
>>
>> Am 12.02.2018 16:06 schrieb "Doug Schaefer" <dschae...@blackberry.com>:
>>
>>> Nick, who specifically on that “team” do you think should get those
>>> changes in for you? To help, here is the commit log from the git repo.
>>>
>>>
>>>
>>> http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/
>>>
>>>
>>>
>>> Kaloyan Raev is the only active committer and from his note earlier in
>>> this chain, he has removed the dependency from the projects he works on.
>>>
>>>
>>>
>>> We really need to be crystal clear at this point what the plan is.
>>>
>>>
>>>
>>> Doug.
>>>
>>>
>>>
>>> *From:* cross-project-issues-dev-boun...@eclipse.org [mailto:
>>> cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Nick Boldt
>>> *Sent:* Monday, February 12, 2018 9:49 AM
>>> *To:* issues, Cross project <cross-project-issues-dev@eclipse.org>
>>> *Subject:* Re: [cross-project-issues-dev] SimRel - TM contribution has
>>> been disabled
>>>
>>>
>>>
>>> AFAIK it's out.
>>>
>>>
>>>
>>> But if I find time to submit the changes from my/Rob's github fork as
>>> gerrit review(s) back to the master fork on git.eclipse.org, that team
>>> can evaluate it, merge it, and maybe decide they want to be included for
>>> M6. Then it'll be up to the Planning Council to approve the late addition.
>>>
>>>
>>>
>>> At least that's my interpretation of the rules. EMO might have a
>>> different view. :)
>>>
>>>
>>>
>>> Nick
>>>
>>> --
>>>
>>> Nick Boldt
>>> Senior Software Engineer, RHCSA
>>> Pro

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-13 Thread Greg Watson
I used your gmail address. The redhat one worked.

Regards,
Greg

> On Feb 13, 2018, at 11:07 AM, Nick Boldt <nickbo...@gmail.com> wrote:
> 
> Which address did you use? If nickbo...@gmail.com 
> <mailto:nickbo...@gmail.com>, that's the problem. If nbo...@redhat.com 
> <mailto:nbo...@redhat.com>, then a possible bug in the portal/nom process.
> 
> Nick
> 
> On Tue, Feb 13, 2018 at 10:19 AM, Greg Watson <g.wat...@computer.org 
> <mailto:g.wat...@computer.org>> wrote:
> Nick,
> 
> I merged the change you indicated, thanks.
> 
> I also tried to nominate you, but for some reason it says your email address 
> is not valid. The actual message is "The nominee field contains an invalid 
> user." I don't know if this is a bug in the nomination form, or you need to 
> be registered somewhere with Eclipse. Does anyone know?
> 
> Regards,
> Greg
> 
> 
>> On Feb 12, 2018, at 6:11 PM, Nick Boldt <nickbo...@gmail.com 
>> <mailto:nickbo...@gmail.com>> wrote:
>> 
>> Considering the list of open TM/RSE gerrits [1] include one that's a 1-line 
>> fix for JDK 9 support, and is 2 weeks old without feedback (I just posted a 
>> +1 on it)... Doug's right, there may be no one to receive my PRs to updated 
>> RSE to work with Photon.
>> 
>> [1] https://git.eclipse.org/r/p/tm/org.eclipse.tm 
>> <https://git.eclipse.org/r/p/tm/org.eclipse.tm>
>> 
>> I also commented on one that's over 5 years old and unmerged. That one and 
>> all those older I suspect should be abandoned as they can't (or shouldn't) 
>> be merged.
>> 
>> If Kaloyan, Lars or any past TM committers [2] want to vote me in, I'll 
>> clean up the open gerrits and get RSE building again in JIPP.
>> 
>> [2] https://projects.eclipse.org/projects/tools.tm/who 
>> <https://projects.eclipse.org/projects/tools.tm/who>
>> 
>> So... Who'd like to nominate me? :)
>> 
>> -- 
>> 
>> Nick Boldt :: http://nick.divbyzero.com <http://nick.divbyzero.com/>
>> FB, IG, Twitter, G+, LinkedIn, Freenode: @nickboldt 
>> WhatsApp: +57 311 530 2074 or +1 647 899 9879 <tel:(647)%20899-9879>
>> 
>> On Feb 12, 2018 10:16 AM, "Lars Vogel" <lars.vo...@vogella.com 
>> <mailto:lars.vo...@vogella.com>> wrote:
>> I suggest to nominate Nick as TM committer 
>> 
>> Am 12.02.2018 16:06 schrieb "Doug Schaefer" <dschae...@blackberry.com 
>> <mailto:dschae...@blackberry.com>>:
>> Nick, who specifically on that “team” do you think should get those changes 
>> in for you? To help, here is the commit log from the git repo.
>> 
>>  
>> 
>> http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/ 
>> <http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/>
>>  
>> 
>> Kaloyan Raev is the only active committer and from his note earlier in this 
>> chain, he has removed the dependency from the projects he works on.
>> 
>>  
>> 
>> We really need to be crystal clear at this point what the plan is.
>> 
>>  
>> 
>> Doug.
>> 
>>  
>> 
>> From: cross-project-issues-dev-boun...@eclipse.org 
>> <mailto:cross-project-issues-dev-boun...@eclipse.org> 
>> [mailto:cross-project-issues-dev-boun...@eclipse.org 
>> <mailto:cross-project-issues-dev-boun...@eclipse.org>] On Behalf Of Nick 
>> Boldt
>> Sent: Monday, February 12, 2018 9:49 AM
>> To: issues, Cross project <cross-project-issues-dev@eclipse.org 
>> <mailto:cross-project-issues-dev@eclipse.org>>
>> Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been 
>> disabled
>> 
>>  
>> 
>> AFAIK it's out.
>> 
>>  
>> 
>> But if I find time to submit the changes from my/Rob's github fork as gerrit 
>> review(s) back to the master fork on git.eclipse.org 
>> <http://git.eclipse.org/>, that team can evaluate it, merge it, and maybe 
>> decide they want to be included for M6. Then it'll be up to the Planning 
>> Council to approve the late addition.
>> 
>>  
>> 
>> At least that's my interpretation of the rules. EMO might have a different 
>> view. :)
>> 
>>  
>> 
>> Nick
>> 
>> -- 
>> 
>> Nick Boldt
>> Senior Software Engineer, RHCSA
>> Productization Lead :: JBoss Tools & Dev Studio
>> IM: @nickboldt / @nboldt / http://nick.divbyzero.com 
>> <http://nick.divbyzero.com/>
>> Sent from my Android phone
>> 
>>  
>> 
>> On Feb 8, 2018 11:29 AM, &quo

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-13 Thread Nick Boldt
Which address did you use? If nickbo...@gmail.com, that's the problem. If
nbo...@redhat.com, then a possible bug in the portal/nom process.

Nick

On Tue, Feb 13, 2018 at 10:19 AM, Greg Watson <g.wat...@computer.org> wrote:

> Nick,
>
> I merged the change you indicated, thanks.
>
> I also tried to nominate you, but for some reason it says your email
> address is not valid. The actual message is "The nominee field contains an
> invalid user." I don't know if this is a bug in the nomination form, or you
> need to be registered somewhere with Eclipse. Does anyone know?
>
> Regards,
> Greg
>
>
> On Feb 12, 2018, at 6:11 PM, Nick Boldt <nickbo...@gmail.com> wrote:
>
> Considering the list of open TM/RSE gerrits [1] include one that's a
> 1-line fix for JDK 9 support, and is 2 weeks old without feedback (I just
> posted a +1 on it)... Doug's right, there may be no one to receive my PRs
> to updated RSE to work with Photon.
>
> [1] https://git.eclipse.org/r/p/tm/org.eclipse.tm
>
> I also commented on one that's over 5 years old and unmerged. That one and
> all those older I suspect should be abandoned as they can't (or shouldn't)
> be merged.
>
> If Kaloyan, Lars or any past TM committers [2] want to vote me in, I'll
> clean up the open gerrits and get RSE building again in JIPP.
>
> [2] https://projects.eclipse.org/projects/tools.tm/who
>
> So... Who'd like to nominate me? :)
>
> --
>
> Nick Boldt :: http://nick.divbyzero.com
> FB, IG, Twitter, G+, LinkedIn, Freenode: @nickboldt
> WhatsApp: +57 311 530 2074 or +1 647 899 9879 <(647)%20899-9879>
>
>
> On Feb 12, 2018 10:16 AM, "Lars Vogel" <lars.vo...@vogella.com> wrote:
>
> I suggest to nominate Nick as TM committer
>
> Am 12.02.2018 16:06 schrieb "Doug Schaefer" <dschae...@blackberry.com>:
>
>> Nick, who specifically on that “team” do you think should get those
>> changes in for you? To help, here is the commit log from the git repo.
>>
>>
>>
>> http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/
>>
>>
>>
>> Kaloyan Raev is the only active committer and from his note earlier in
>> this chain, he has removed the dependency from the projects he works on.
>>
>>
>>
>> We really need to be crystal clear at this point what the plan is.
>>
>>
>>
>> Doug.
>>
>>
>>
>> *From:* cross-project-issues-dev-boun...@eclipse.org [mailto:
>> cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Nick Boldt
>> *Sent:* Monday, February 12, 2018 9:49 AM
>> *To:* issues, Cross project <cross-project-issues-dev@eclipse.org>
>> *Subject:* Re: [cross-project-issues-dev] SimRel - TM contribution has
>> been disabled
>>
>>
>>
>> AFAIK it's out.
>>
>>
>>
>> But if I find time to submit the changes from my/Rob's github fork as
>> gerrit review(s) back to the master fork on git.eclipse.org, that team
>> can evaluate it, merge it, and maybe decide they want to be included for
>> M6. Then it'll be up to the Planning Council to approve the late addition.
>>
>>
>>
>> At least that's my interpretation of the rules. EMO might have a
>> different view. :)
>>
>>
>>
>> Nick
>>
>> --
>>
>> Nick Boldt
>> Senior Software Engineer, RHCSA
>> Productization Lead :: JBoss Tools & Dev Studio
>> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>> Sent from my Android phone
>>
>>
>>
>> On Feb 8, 2018 11:29 AM, "Simon Bernard" <sbern...@sierrawireless.com>
>> wrote:
>>
>> Hi,
>>
>> Sry for the delay, I re-enabled LDT removing ldt.remote feature which
>> depends on RSE.
>> So this should be ok for photon M6.
>>
>> I'm a bit confuse. Will RSE be reintegrated or is  it officially and
>> definitely not part of Photon ?
>>
>> Thx,
>>
>> Simon
>>
>>
>> Le 01/02/2018 à 12:22, Frederic Gurr a écrit :
>>
>> Hi,
>>
>> Thanks to Kaloyan, Dawid and Eugene for fixing and re-enabling the
>> contributions of DLTK, PDT and TCF.
>>
>> The only contribution missing is LDT.
>> Since it's already past the +3 window, LDT will miss Photon M5.
>> Hopefully they can rejoin for M6.
>>
>> Regards,
>>
>> Fred
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this li

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-13 Thread Greg Watson
Nick,

I merged the change you indicated, thanks.

I also tried to nominate you, but for some reason it says your email address is 
not valid. The actual message is "The nominee field contains an invalid user." 
I don't know if this is a bug in the nomination form, or you need to be 
registered somewhere with Eclipse. Does anyone know?

Regards,
Greg

> On Feb 12, 2018, at 6:11 PM, Nick Boldt <nickbo...@gmail.com> wrote:
> 
> Considering the list of open TM/RSE gerrits [1] include one that's a 1-line 
> fix for JDK 9 support, and is 2 weeks old without feedback (I just posted a 
> +1 on it)... Doug's right, there may be no one to receive my PRs to updated 
> RSE to work with Photon.
> 
> [1] https://git.eclipse.org/r/p/tm/org.eclipse.tm 
> <https://git.eclipse.org/r/p/tm/org.eclipse.tm>
> 
> I also commented on one that's over 5 years old and unmerged. That one and 
> all those older I suspect should be abandoned as they can't (or shouldn't) be 
> merged.
> 
> If Kaloyan, Lars or any past TM committers [2] want to vote me in, I'll clean 
> up the open gerrits and get RSE building again in JIPP.
> 
> [2] https://projects.eclipse.org/projects/tools.tm/who 
> <https://projects.eclipse.org/projects/tools.tm/who>
> 
> So... Who'd like to nominate me? :)
> 
> -- 
> 
> Nick Boldt :: http://nick.divbyzero.com <http://nick.divbyzero.com/>
> FB, IG, Twitter, G+, LinkedIn, Freenode: @nickboldt 
> WhatsApp: +57 311 530 2074 or +1 647 899 9879
> 
> 
> On Feb 12, 2018 10:16 AM, "Lars Vogel" <lars.vo...@vogella.com 
> <mailto:lars.vo...@vogella.com>> wrote:
> I suggest to nominate Nick as TM committer 
> 
> Am 12.02.2018 16:06 schrieb "Doug Schaefer" <dschae...@blackberry.com 
> <mailto:dschae...@blackberry.com>>:
> Nick, who specifically on that “team” do you think should get those changes 
> in for you? To help, here is the commit log from the git repo.
> 
>  
> 
> http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/ 
> <http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/>
>  
> 
> Kaloyan Raev is the only active committer and from his note earlier in this 
> chain, he has removed the dependency from the projects he works on.
> 
>  
> 
> We really need to be crystal clear at this point what the plan is.
> 
>  
> 
> Doug.
> 
>  
> 
> From: cross-project-issues-dev-boun...@eclipse.org 
> <mailto:cross-project-issues-dev-boun...@eclipse.org> 
> [mailto:cross-project-issues-dev-boun...@eclipse.org 
> <mailto:cross-project-issues-dev-boun...@eclipse.org>] On Behalf Of Nick Boldt
> Sent: Monday, February 12, 2018 9:49 AM
> To: issues, Cross project <cross-project-issues-dev@eclipse.org 
> <mailto:cross-project-issues-dev@eclipse.org>>
> Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been 
> disabled
> 
>  
> 
> AFAIK it's out.
> 
>  
> 
> But if I find time to submit the changes from my/Rob's github fork as gerrit 
> review(s) back to the master fork on git.eclipse.org 
> <http://git.eclipse.org/>, that team can evaluate it, merge it, and maybe 
> decide they want to be included for M6. Then it'll be up to the Planning 
> Council to approve the late addition.
> 
>  
> 
> At least that's my interpretation of the rules. EMO might have a different 
> view. :)
> 
>  
> 
> Nick
> 
> -- 
> 
> Nick Boldt
> Senior Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com 
> <http://nick.divbyzero.com/>
> Sent from my Android phone
> 
>  
> 
> On Feb 8, 2018 11:29 AM, "Simon Bernard" <sbern...@sierrawireless.com 
> <mailto:sbern...@sierrawireless.com>> wrote:
> 
> Hi,
> 
> Sry for the delay, I re-enabled LDT removing ldt.remote feature which depends 
> on RSE.
> So this should be ok for photon M6.
> 
> I'm a bit confuse. Will RSE be reintegrated or is  it officially and 
> definitely not part of Photon ?
> 
> Thx,
> 
> Simon
> 
> 
> Le 01/02/2018 à 12:22, Frederic Gurr a écrit :
> 
> Hi,
> 
> Thanks to Kaloyan, Dawid and Eugene for fixing and re-enabling the
> contributions of DLTK, PDT and TCF.
> 
> The only contribution missing is LDT.
> Since it's already past the +3 window, LDT will miss Photon M5.
> Hopefully they can rejoin for M6.
> 
> Regards,
> 
> Fred
> 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> <mailto:cross-project-issues-dev@eclipse.org>
> To change your delivery options, retrieve you

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-13 Thread Doug Schaefer
Again, this discussion needs to happen on the tm-dev list.

Doug.

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Wayne Beaton
Sent: Tuesday, February 13, 2018 9:26 AM
To: Cross project issues <cross-project-issues-dev@eclipse.org>
Cc: Kaloyan Raev <kaloya...@zend.com>
Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been 
disabled

Strictkly speaking, the "leadership chain" can decide to add or remove 
committers if the project is determined to be dysfunctional. The leadership 
chain includes the PMC. They'd have to ask me to initiate this exceptional 
process...

Wayne

On Tue, Feb 13, 2018 at 7:00 AM, Lars Vogel 
<lars.vo...@vogella.com<mailto:lars.vo...@vogella.com>> wrote:
> So... Who'd like to nominate me? :)

I'm not a TM committer. Doug, or Kaloyan, can you start the nomination?

Otherwise, I think EMO could give you access if TM is considered as an
abandoned project.

On Tue, Feb 13, 2018 at 12:11 AM, Nick Boldt 
<nickbo...@gmail.com<mailto:nickbo...@gmail.com>> wrote:
> Considering the list of open TM/RSE gerrits [1] include one that's a 1-line
> fix for JDK 9 support, and is 2 weeks old without feedback (I just posted a
> +1 on it)... Doug's right, there may be no one to receive my PRs to updated
> RSE to work with Photon.
>
> [1] https://git.eclipse.org/r/p/tm/org.eclipse.tm
>
> I also commented on one that's over 5 years old and unmerged. That one and
> all those older I suspect should be abandoned as they can't (or shouldn't)
> be merged.
>
> If Kaloyan, Lars or any past TM committers [2] want to vote me in, I'll
> clean up the open gerrits and get RSE building again in JIPP.
>
> [2] https://projects.eclipse.org/projects/tools.tm/who
>
> So... Who'd like to nominate me? :)
>
> --
>
> Nick Boldt :: http://nick.divbyzero.com
> FB, IG, Twitter, G+, LinkedIn, Freenode: @nickboldt
> WhatsApp: +57 311 530 2074<tel:%2B57%20311%20530%202074> or +1 647 899 
> 9879<tel:%2B1%20647%20899%209879>
>
>
> On Feb 12, 2018 10:16 AM, "Lars Vogel" 
> <lars.vo...@vogella.com<mailto:lars.vo...@vogella.com>> wrote:
>
> I suggest to nominate Nick as TM committer
>
> Am 12.02.2018 16:06 schrieb "Doug Schaefer" 
> <dschae...@blackberry.com<mailto:dschae...@blackberry.com>>:
>>
>> Nick, who specifically on that “team” do you think should get those
>> changes in for you? To help, here is the commit log from the git repo.
>>
>>
>>
>> http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/
>>
>>
>>
>> Kaloyan Raev is the only active committer and from his note earlier in
>> this chain, he has removed the dependency from the projects he works on.
>>
>>
>>
>> We really need to be crystal clear at this point what the plan is.
>>
>>
>>
>> Doug.
>>
>>
>>
>> From: 
>> cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org>
>> [mailto:cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org>]
>>  On Behalf Of Nick
>> Boldt
>> Sent: Monday, February 12, 2018 9:49 AM
>> To: issues, Cross project 
>> <cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>>
>> Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been
>> disabled
>>
>>
>>
>> AFAIK it's out.
>>
>>
>>
>> But if I find time to submit the changes from my/Rob's github fork as
>> gerrit review(s) back to the master fork on 
>> git.eclipse.org<http://git.eclipse.org>, that team can
>> evaluate it, merge it, and maybe decide they want to be included for M6.
>> Then it'll be up to the Planning Council to approve the late addition.
>>
>>
>>
>> At least that's my interpretation of the rules. EMO might have a different
>> view. :)
>>
>>
>>
>> Nick
>>
>> --
>>
>> Nick Boldt
>> Senior Software Engineer, RHCSA
>> Productization Lead :: JBoss Tools & Dev Studio
>> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>> Sent from my Android phone
>>
>>
>>
>> On Feb 8, 2018 11:29 AM, "Simon Bernard" 
>> <sbern...@sierrawireless.com<mailto:sbern...@sierrawireless.com>>
>> wrote:
>>
>> Hi,
>>
>> Sry for the delay, I re-enabled LDT removing ldt.remote feature which
>> depends on RSE.
>> So this should be ok for photon M6.
>>
>> I'm a bit confuse. Will RSE be reintegrated o

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-12 Thread Lars Vogel
I suggest to nominate Nick as TM committer

Am 12.02.2018 16:06 schrieb "Doug Schaefer" <dschae...@blackberry.com>:

> Nick, who specifically on that “team” do you think should get those
> changes in for you? To help, here is the commit log from the git repo.
>
>
>
> http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/
>
>
>
> Kaloyan Raev is the only active committer and from his note earlier in
> this chain, he has removed the dependency from the projects he works on.
>
>
>
> We really need to be crystal clear at this point what the plan is.
>
>
>
> Doug.
>
>
>
> *From:* cross-project-issues-dev-boun...@eclipse.org [mailto:
> cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Nick Boldt
> *Sent:* Monday, February 12, 2018 9:49 AM
> *To:* issues, Cross project <cross-project-issues-dev@eclipse.org>
> *Subject:* Re: [cross-project-issues-dev] SimRel - TM contribution has
> been disabled
>
>
>
> AFAIK it's out.
>
>
>
> But if I find time to submit the changes from my/Rob's github fork as
> gerrit review(s) back to the master fork on git.eclipse.org, that team
> can evaluate it, merge it, and maybe decide they want to be included for
> M6. Then it'll be up to the Planning Council to approve the late addition.
>
>
>
> At least that's my interpretation of the rules. EMO might have a different
> view. :)
>
>
>
> Nick
>
> --
>
> Nick Boldt
> Senior Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> Sent from my Android phone
>
>
>
> On Feb 8, 2018 11:29 AM, "Simon Bernard" <sbern...@sierrawireless.com>
> wrote:
>
> Hi,
>
> Sry for the delay, I re-enabled LDT removing ldt.remote feature which
> depends on RSE.
> So this should be ok for photon M6.
>
> I'm a bit confuse. Will RSE be reintegrated or is  it officially and
> definitely not part of Photon ?
>
> Thx,
>
> Simon
>
>
> Le 01/02/2018 à 12:22, Frederic Gurr a écrit :
>
> Hi,
>
> Thanks to Kaloyan, Dawid and Eugene for fixing and re-enabling the
> contributions of DLTK, PDT and TCF.
>
> The only contribution missing is LDT.
> Since it's already past the +3 window, LDT will miss Photon M5.
> Hopefully they can rejoin for M6.
>
> Regards,
>
> Fred
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> 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@eclipse.org
> 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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-12 Thread Doug Schaefer
Nick, who specifically on that “team” do you think should get those changes in 
for you? To help, here is the commit log from the git repo.

http://git.eclipse.org/c/tm/org.eclipse.tm.git/log/

Kaloyan Raev is the only active committer and from his note earlier in this 
chain, he has removed the dependency from the projects he works on.

We really need to be crystal clear at this point what the plan is.

Doug.

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Nick Boldt
Sent: Monday, February 12, 2018 9:49 AM
To: issues, Cross project <cross-project-issues-dev@eclipse.org>
Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been 
disabled

AFAIK it's out.

But if I find time to submit the changes from my/Rob's github fork as gerrit 
review(s) back to the master fork on git.eclipse.org<http://git.eclipse.org>, 
that team can evaluate it, merge it, and maybe decide they want to be included 
for M6. Then it'll be up to the Planning Council to approve the late addition.

At least that's my interpretation of the rules. EMO might have a different 
view. :)

Nick
--

Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
Sent from my Android phone

On Feb 8, 2018 11:29 AM, "Simon Bernard" 
<sbern...@sierrawireless.com<mailto:sbern...@sierrawireless.com>> wrote:
Hi,

Sry for the delay, I re-enabled LDT removing ldt.remote feature which depends 
on RSE.
So this should be ok for photon M6.

I'm a bit confuse. Will RSE be reintegrated or is  it officially and definitely 
not part of Photon ?

Thx,

Simon


Le 01/02/2018 à 12:22, Frederic Gurr a écrit :
Hi,

Thanks to Kaloyan, Dawid and Eugene for fixing and re-enabling the
contributions of DLTK, PDT and TCF.

The only contribution missing is LDT.
Since it's already past the +3 window, LDT will miss Photon M5.
Hopefully they can rejoin for M6.

Regards,

Fred

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>
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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-12 Thread Nick Boldt
AFAIK it's out.

But if I find time to submit the changes from my/Rob's github fork as
gerrit review(s) back to the master fork on git.eclipse.org, that team can
evaluate it, merge it, and maybe decide they want to be included for M6.
Then it'll be up to the Planning Council to approve the late addition.

At least that's my interpretation of the rules. EMO might have a different
view. :)

Nick

-- 

Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
Sent from my Android phone

On Feb 8, 2018 11:29 AM, "Simon Bernard" 
wrote:

> Hi,
>
> Sry for the delay, I re-enabled LDT removing ldt.remote feature which
> depends on RSE.
> So this should be ok for photon M6.
>
> I'm a bit confuse. Will RSE be reintegrated or is  it officially and
> definitely not part of Photon ?
>
> Thx,
>
> Simon
>
>
> Le 01/02/2018 à 12:22, Frederic Gurr a écrit :
>
>> Hi,
>>
>> Thanks to Kaloyan, Dawid and Eugene for fixing and re-enabling the
>> contributions of DLTK, PDT and TCF.
>>
>> The only contribution missing is LDT.
>> Since it's already past the +3 window, LDT will miss Photon M5.
>> Hopefully they can rejoin for M6.
>>
>> Regards,
>>
>> Fred
>>
>>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> 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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-05 Thread Nick Boldt
FYI, I've pushed an update to DTP into the Photon.0 simrel. Too late for
M5, but it'll be there for M6.

If anyone has time to take a look at the failing DTP tests, please do. You
can throw me a gerrit request, now that DTP is gerrit-enabled.

More info about this new DTP 1.14.100-SNAPSHOT build here:

https://dev.eclipse.org/mhonarc/lists/dtp-dev/msg02381.html

Thanks,

Nick

(Coming up next, a series of gerrits submissions for TM/RSE... once WTP is
fixed.)


On Thu, Feb 1, 2018 at 6:22 AM, Frederic Gurr <
frederic.g...@eclipse-foundation.org> wrote:

> Hi,
>
> Thanks to Kaloyan, Dawid and Eugene for fixing and re-enabling the
> contributions of DLTK, PDT and TCF.
>
> The only contribution missing is LDT.
> Since it's already past the +3 window, LDT will miss Photon M5.
> Hopefully they can rejoin for M6.
>
> Regards,
>
> Fred
>
> --
> Frederic Gurr
>
> Release Engineer
> Eclipse Foundation
>
> On 30.01.2018 22:13, Frederic Gurr wrote:
> > Hi,
> >
> > As announced before, the Target Management (TM) contribution has been
> > disabled.
> >
> > Even though some code has been moved to CDT (see
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=527575), there are still
> > two features remaining (org.eclipse.rse and org.eclipse.rse.useractions).
> >
> > Since disabling the TM contribution caused issues, I had to disable the
> > following contributions:
> >
> > * TCF
> > * PDT
> > * LDT
> > * DLTK
> >
> > Please fix the dependencies (it might only require changes in TCF, but I
> > did not dig deeper) and re-enable the contributions. Project leads of
> > affected projects have been added in CC.
> >
> >
> > Regards,
> >
> > Fred
> >
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat,
Inc.
http://nick.divbyzero.com
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-02-01 Thread Frederic Gurr
Hi,

Thanks to Kaloyan, Dawid and Eugene for fixing and re-enabling the
contributions of DLTK, PDT and TCF.

The only contribution missing is LDT.
Since it's already past the +3 window, LDT will miss Photon M5.
Hopefully they can rejoin for M6.

Regards,

Fred

-- 
Frederic Gurr

Release Engineer
Eclipse Foundation

On 30.01.2018 22:13, Frederic Gurr wrote:
> Hi,
> 
> As announced before, the Target Management (TM) contribution has been
> disabled.
> 
> Even though some code has been moved to CDT (see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=527575), there are still
> two features remaining (org.eclipse.rse and org.eclipse.rse.useractions).
> 
> Since disabling the TM contribution caused issues, I had to disable the
> following contributions:
> 
> * TCF
> * PDT
> * LDT
> * DLTK
> 
> Please fix the dependencies (it might only require changes in TCF, but I
> did not dig deeper) and re-enable the contributions. Project leads of
> affected projects have been added in CC.
> 
> 
> Regards,
> 
> Fred
> 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Aleksandar Kurtakov
On Thu, Feb 1, 2018 at 1:24 AM, Doug Schaefer <dschae...@blackberry.com>
wrote:

> You're right, I'll leave it to the active committers to decide. And this
> discussion should be happening on the tm-dev list so they see it.
>

If there are really no active committes to take the patches or nominate new
committers and Nick/Rob still want to keep it on. The issue should be
brought to Tools PMC so nomination can come up from the PMC.


>
> Sent from my BlackBerry - the most secure mobile device - via the Rogers
> Network
> *From:* mist...@redhat.com
> *Sent:* January 31, 2018 5:33 PM
> *To:* cross-project-issues-dev@eclipse.org
> *Reply-to:* cross-project-issues-dev@eclipse.org
> *Subject:* Re: [cross-project-issues-dev] SimRel - TM contribution has
> been disabled
>
>
>
> On Wed, Jan 31, 2018 at 11:14 PM, Doug Schaefer <dschae...@blackberry.com>
> wrote:
>
>> Does anyone want these contributions to keep RSE alive?
>>
>
> I don't think the opinion of others should be used as a criterion here.
> The thing is that if Nick, Rob or whoever have authored good patches, it's
> still better to contribute them into the project, independently of what
> others want to do or not with RSE. No-one is allowed to claim that a
> project is dead if it still has contributors/contributions. If the patches
> are proposed and seem good but don't get merged for other non-technical
> reason and contributors are still interested in getting those patches
> merged, then it's worth an escalation plan to turn contributors into
> committers.
> In general, having people authoring commits can be seen as a sign that at
> least those who did the work probably have interest in authoring the
> commits, ie keeping RSE alive in that case. So to me, whenever there is a
> contribution, it shows that the project can still be perceived as alive and
> that no other discussion is necessary before applying the typical EDP
> processes to make sure project can be as successful as contributors can
> make it.
> To sum up, we don't need to discuss RSE state any more, the patches
> authored by Rob and Nick can be a sufficient sign that RSE is still alive
> and we just have to make sure the efforts stored on a GitHub branch can be
> turned into activity in the origin code base if committers want it.
>
> Cheers,
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
Alexander Kurtakov
Red Hat Eclipse Team
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Doug Schaefer
You're right, I'll leave it to the active committers to decide. And this 
discussion should be happening on the tm-dev list so they see it.

Sent from my BlackBerry - the most secure mobile device - via the Rogers Network
From: mist...@redhat.com
Sent: January 31, 2018 5:33 PM
To: cross-project-issues-dev@eclipse.org
Reply-to: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been 
disabled




On Wed, Jan 31, 2018 at 11:14 PM, Doug Schaefer 
<dschae...@blackberry.com<mailto:dschae...@blackberry.com>> wrote:
Does anyone want these contributions to keep RSE alive?

I don't think the opinion of others should be used as a criterion here. The 
thing is that if Nick, Rob or whoever have authored good patches, it's still 
better to contribute them into the project, independently of what others want 
to do or not with RSE. No-one is allowed to claim that a project is dead if it 
still has contributors/contributions. If the patches are proposed and seem good 
but don't get merged for other non-technical reason and contributors are still 
interested in getting those patches merged, then it's worth an escalation plan 
to turn contributors into committers.
In general, having people authoring commits can be seen as a sign that at least 
those who did the work probably have interest in authoring the commits, ie 
keeping RSE alive in that case. So to me, whenever there is a contribution, it 
shows that the project can still be perceived as alive and that no other 
discussion is necessary before applying the typical EDP processes to make sure 
project can be as successful as contributors can make it.
To sum up, we don't need to discuss RSE state any more, the patches authored by 
Rob and Nick can be a sufficient sign that RSE is still alive and we just have 
to make sure the efforts stored on a GitHub branch can be turned into activity 
in the origin code base if committers want it.

Cheers,
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Mickael Istria
On Wed, Jan 31, 2018 at 11:14 PM, Doug Schaefer 
wrote:

> Does anyone want these contributions to keep RSE alive?
>

I don't think the opinion of others should be used as a criterion here. The
thing is that if Nick, Rob or whoever have authored good patches, it's
still better to contribute them into the project, independently of what
others want to do or not with RSE. No-one is allowed to claim that a
project is dead if it still has contributors/contributions. If the patches
are proposed and seem good but don't get merged for other non-technical
reason and contributors are still interested in getting those patches
merged, then it's worth an escalation plan to turn contributors into
committers.
In general, having people authoring commits can be seen as a sign that at
least those who did the work probably have interest in authoring the
commits, ie keeping RSE alive in that case. So to me, whenever there is a
contribution, it shows that the project can still be perceived as alive and
that no other discussion is necessary before applying the typical EDP
processes to make sure project can be as successful as contributors can
make it.
To sum up, we don't need to discuss RSE state any more, the patches
authored by Rob and Nick can be a sufficient sign that RSE is still alive
and we just have to make sure the efforts stored on a GitHub branch can be
turned into activity in the origin code base if committers want it.

Cheers,
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Dawid Pakuła
Hi,

I enabled DLTK and PDT, validation passed.

-- 
Dawid Pakuła

From: Kaloyan Raev <kalo...@raev.name> <kalo...@raev.name>
Reply: Cross project issues <cross-project-issues-dev@eclipse.org>
<cross-project-issues-dev@eclipse.org>
Date: 31 January 2018 at 17:32:14
To: Cross project issues <cross-project-issues-dev@eclipse.org>
<cross-project-issues-dev@eclipse.org>
Subject:  Re: [cross-project-issues-dev] SimRel - TM contribution has been
disabled

Hi,

I removed the DLTK integration with RSE from SimRel:
https://git.eclipse.org/r/116449/

With this change it should be possible to re-enable DLTK and PDT.

Thanks,
Kaloyan

On Tue, Jan 30, 2018 at 11:13 PM, Frederic Gurr <
frederic.g...@eclipse-foundation.org> wrote:

> Hi,
>
> As announced before, the Target Management (TM) contribution has been
> disabled.
>
> Even though some code has been moved to CDT (see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=527575), there are still
> two features remaining (org.eclipse.rse and org.eclipse.rse.useractions).
>
> Since disabling the TM contribution caused issues, I had to disable the
> following contributions:
>
> * TCF
> * PDT
> * LDT
> * DLTK
>
> Please fix the dependencies (it might only require changes in TCF, but I
> did not dig deeper) and re-enable the contributions. Project leads of
> affected projects have been added in CC.
>
>
> Regards,
>
> Fred
>
> --
> Frederic Gurr
>
> Release Engineer
> Eclipse Foundation
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> 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@eclipse.org
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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Doug Schaefer
Yes. That was the point of all this. TM is dead. It will need to be rebooted or 
archived.

I'm not sure Nick's question has been answered though. Does anyone want these 
contributions to keep RSE alive? It seems existing projects have adapted to its 
removal.

Doug.

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Greg Watson
Sent: Wednesday, January 31, 2018 3:30 PM
To: Cross project issues <cross-project-issues-dev@eclipse.org>
Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been 
disabled

The last commit was by Kaloyan Raev in April last year, so it is pretty much 
inactive at this point.

Are your fixes to the code base or to the build? If the latter, then I can 
probably take a look. If the former, then it might be better to take Wayne up 
on his suggestion.

Regards,
Greg


On Jan 31, 2018, at 12:38 PM, Nick Boldt 
<nbo...@redhat.com<mailto:nbo...@redhat.com>> wrote:

OK, but what happens if the project is dead, no longer being developed, and was 
kicked off the simrel train for its inactivity / failure to declare intent on 
time?

I'll happily contribute the fixes, but if no one reviews them or if they're 
bigger than the 1000 LOC limit, we're going to have a bad time. :)

Cheers,

Nick

On Wed, Jan 31, 2018 at 12:29 PM, Wayne Beaton 
<wayne.bea...@eclipse-foundation.org<mailto:wayne.bea...@eclipse-foundation.org>>
 wrote:
You don't need to be a committer to make a contribution. In fact, that's the 
exact opposite of how it's supposed to happen.

Make the contribution.

The existing committers can then choose to nominate you as a committer to 
support that contribution.

In exceptional circumstances, the PMC can declare a project dysfunctional and 
ask me to just appoint committers, but that is only if we believe that the 
circumstances are indeed exceptional.

HTH,

Wayne

On Wed, Jan 31, 2018 at 12:16 PM, Nick Boldt 
<nbo...@redhat.com<mailto:nbo...@redhat.com>> wrote:
Yes, that's what I was suggesting. We contribute the handful of fixes in Rob's 
fork back to the master repo on git.eclipse.org<http://git.eclipse.org/>, build 
it on a HIPP, and contribute it into Photon.0.M6.

If someone nominates me as a committer to TM/RSE, I'll make this happen.

On Wed, Jan 31, 2018 at 12:13 PM, Mickael Istria 
<mist...@redhat.com<mailto:mist...@redhat.com>> wrote:


On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt 
<nbo...@redhat.com<mailto:nbo...@redhat.com>> wrote:
Should we want to re-include RSE in Photon, we could do so for M6 if someone 
grants me a place to publish it & permission to do so. We've got a fork [1] 
that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and it currently 
builds against Photon.0.M4. This could easily be moved to an Eclipse HIPP, such 
as this one [2], if I can get permission to edit jobs there & publish to 
download.eclipse.org<http://download.eclipse.org/>.

It's not much allowed to build and publish external 
(non-Eclipse.org<http://non-Eclipse.org>) sources on 
Eclipse.org<http://Eclipse.org> infrastructre.
The only way forward, should we want to re-include RSE in Photon, would be that 
Rob and you get the patches you authored merged in the actual TM/RSE repository 
at Eclipse.org<http://Eclipse.org>.

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com<http://nick.divbyzero.com/>
[https://www.redhat.com/files/brand/email/sig-redhat.png]<https://red.ht/sig>

TRIED. TESTED. TRUSTED.<https://redhat.com/trusted>

@ @redhatnews<https://twitter.com/redhatnews>  Red Hat
<https://www.facebook.com/RedHatInc>

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss 

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Greg Watson
The last commit was by Kaloyan Raev in April last year, so it is pretty much 
inactive at this point.

Are your fixes to the code base or to the build? If the latter, then I can 
probably take a look. If the former, then it might be better to take Wayne up 
on his suggestion.

Regards,
Greg

> On Jan 31, 2018, at 12:38 PM, Nick Boldt  wrote:
> 
> OK, but what happens if the project is dead, no longer being developed, and 
> was kicked off the simrel train for its inactivity / failure to declare 
> intent on time? 
> 
> I'll happily contribute the fixes, but if no one reviews them or if they're 
> bigger than the 1000 LOC limit, we're going to have a bad time. :)
> 
> Cheers,
> 
> Nick
> 
> On Wed, Jan 31, 2018 at 12:29 PM, Wayne Beaton 
>  > wrote:
> You don't need to be a committer to make a contribution. In fact, that's the 
> exact opposite of how it's supposed to happen.
> 
> Make the contribution. 
> 
> The existing committers can then choose to nominate you as a committer to 
> support that contribution.
> 
> In exceptional circumstances, the PMC can declare a project dysfunctional and 
> ask me to just appoint committers, but that is only if we believe that the 
> circumstances are indeed exceptional.
> 
> HTH,
> 
> Wayne
> 
> On Wed, Jan 31, 2018 at 12:16 PM, Nick Boldt  > wrote:
> Yes, that's what I was suggesting. We contribute the handful of fixes in 
> Rob's fork back to the master repo on git.eclipse.org 
> , build it on a HIPP, and contribute it into 
> Photon.0.M6.
> 
> If someone nominates me as a committer to TM/RSE, I'll make this happen.
> 
> On Wed, Jan 31, 2018 at 12:13 PM, Mickael Istria  > wrote:
> 
> 
> On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt  > wrote:
> Should we want to re-include RSE in Photon, we could do so for M6 if someone 
> grants me a place to publish it & permission to do so. We've got a fork [1] 
> that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and it currently 
> builds against Photon.0.M4. This could easily be moved to an Eclipse HIPP, 
> such as this one [2], if I can get permission to edit jobs there & publish to 
> download.eclipse.org . 
> 
> It's not much allowed to build and publish external (non-Eclipse.org) sources 
> on Eclipse.org infrastructre.
> The only way forward, should we want to re-include RSE in Photon, would be 
> that Rob and you get the patches you authored merged in the actual TM/RSE 
> repository at Eclipse.org.
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> 
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> 
> 
> 
> 
> -- 
> Nick Boldt
> Senior Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com 
> 
>   
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews       Red Hat
>  
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> 
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> 
> 
> 
> 
> -- 
> Wayne Beaton
> Director of Open Source Projects
> The Eclipse Foundation
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> 
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> 
> 
> 
> 
> -- 
> Nick Boldt
> Senior Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com 
> 
>   
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews       Red Hat
>  
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery 

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Aleksandar Kurtakov
On Wed, Jan 31, 2018 at 7:38 PM, Nick Boldt  wrote:

> OK, but what happens if the project is dead, no longer being developed,
> and was kicked off the simrel train for its inactivity / failure to declare
> intent on time?
>
> I'll happily contribute the fixes, but if no one reviews them or if
> they're bigger than the 1000 LOC limit, we're going to have a bad time. :)
>

Let's not go into "if"s. Start with small contributions to just check how
alive is the project. If not bring it to the respective PMC for action.


>
> Cheers,
>
> Nick
>
> On Wed, Jan 31, 2018 at 12:29 PM, Wayne Beaton  foundation.org> wrote:
>
>> You don't need to be a committer to make a contribution. In fact, that's
>> the exact opposite of how it's supposed to happen.
>>
>> Make the contribution.
>>
>> The existing committers can then choose to nominate you as a committer to
>> support that contribution.
>>
>> In exceptional circumstances, the PMC can declare a project dysfunctional
>> and ask me to just appoint committers, but that is only if we believe that
>> the circumstances are indeed exceptional.
>>
>> HTH,
>>
>> Wayne
>>
>> On Wed, Jan 31, 2018 at 12:16 PM, Nick Boldt  wrote:
>>
>>> Yes, that's what I was suggesting. We contribute the handful of fixes in
>>> Rob's fork back to the master repo on git.eclipse.org, build it on a
>>> HIPP, and contribute it into Photon.0.M6.
>>>
>>> If someone nominates me as a committer to TM/RSE, I'll make this happen.
>>>
>>> On Wed, Jan 31, 2018 at 12:13 PM, Mickael Istria 
>>> wrote:
>>>


 On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt  wrote:

> Should we want to re-include RSE in Photon, we could do so for M6 if
> someone grants me a place to publish it & permission to do so. We've got a
> fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and
> it currently builds against Photon.0.M4. This could easily be moved to an
> Eclipse HIPP, such as this one [2], if I can get permission to edit jobs
> there & publish to download.eclipse.org.
>

 It's not much allowed to build and publish external (non-Eclipse.org)
 sources on Eclipse.org infrastructre.
 The only way forward, should we want to re-include RSE in Photon, would
 be that Rob and you get the patches you authored merged in the actual
 TM/RSE repository at Eclipse.org.

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

>>>
>>>
>>>
>>> --
>>>
>>> Nick Boldt
>>>
>>> Senior Software Engineer, RHCSA
>>>
>>> Productization Lead :: JBoss Tools & Dev Studio
>>>
>>> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>>> 
>>> TRIED. TESTED. TRUSTED. 
>>> @ @redhatnews   Red Hat
>>> 
>>>
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>
>>
>>
>> --
>> Wayne Beaton
>> Director of Open Source Projects
>> The Eclipse Foundation
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> --
>
> Nick Boldt
>
> Senior Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> 
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews   Red Hat
> 
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
Alexander Kurtakov
Red Hat Eclipse Team
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Nick Boldt
OK, but what happens if the project is dead, no longer being developed, and
was kicked off the simrel train for its inactivity / failure to declare
intent on time?

I'll happily contribute the fixes, but if no one reviews them or if they're
bigger than the 1000 LOC limit, we're going to have a bad time. :)

Cheers,

Nick

On Wed, Jan 31, 2018 at 12:29 PM, Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> You don't need to be a committer to make a contribution. In fact, that's
> the exact opposite of how it's supposed to happen.
>
> Make the contribution.
>
> The existing committers can then choose to nominate you as a committer to
> support that contribution.
>
> In exceptional circumstances, the PMC can declare a project dysfunctional
> and ask me to just appoint committers, but that is only if we believe that
> the circumstances are indeed exceptional.
>
> HTH,
>
> Wayne
>
> On Wed, Jan 31, 2018 at 12:16 PM, Nick Boldt  wrote:
>
>> Yes, that's what I was suggesting. We contribute the handful of fixes in
>> Rob's fork back to the master repo on git.eclipse.org, build it on a
>> HIPP, and contribute it into Photon.0.M6.
>>
>> If someone nominates me as a committer to TM/RSE, I'll make this happen.
>>
>> On Wed, Jan 31, 2018 at 12:13 PM, Mickael Istria 
>> wrote:
>>
>>>
>>>
>>> On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt  wrote:
>>>
 Should we want to re-include RSE in Photon, we could do so for M6 if
 someone grants me a place to publish it & permission to do so. We've got a
 fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and
 it currently builds against Photon.0.M4. This could easily be moved to an
 Eclipse HIPP, such as this one [2], if I can get permission to edit jobs
 there & publish to download.eclipse.org.

>>>
>>> It's not much allowed to build and publish external (non-Eclipse.org)
>>> sources on Eclipse.org infrastructre.
>>> The only way forward, should we want to re-include RSE in Photon, would
>>> be that Rob and you get the patches you authored merged in the actual
>>> TM/RSE repository at Eclipse.org.
>>>
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>
>>
>>
>> --
>>
>> Nick Boldt
>>
>> Senior Software Engineer, RHCSA
>>
>> Productization Lead :: JBoss Tools & Dev Studio
>>
>> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>> 
>> TRIED. TESTED. TRUSTED. 
>> @ @redhatnews   Red Hat
>> 
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> --
> Wayne Beaton
> Director of Open Source Projects
> The Eclipse Foundation
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED. 
@ @redhatnews   Red Hat

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Wayne Beaton
You don't need to be a committer to make a contribution. In fact, that's
the exact opposite of how it's supposed to happen.

Make the contribution.

The existing committers can then choose to nominate you as a committer to
support that contribution.

In exceptional circumstances, the PMC can declare a project dysfunctional
and ask me to just appoint committers, but that is only if we believe that
the circumstances are indeed exceptional.

HTH,

Wayne

On Wed, Jan 31, 2018 at 12:16 PM, Nick Boldt  wrote:

> Yes, that's what I was suggesting. We contribute the handful of fixes in
> Rob's fork back to the master repo on git.eclipse.org, build it on a
> HIPP, and contribute it into Photon.0.M6.
>
> If someone nominates me as a committer to TM/RSE, I'll make this happen.
>
> On Wed, Jan 31, 2018 at 12:13 PM, Mickael Istria 
> wrote:
>
>>
>>
>> On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt  wrote:
>>
>>> Should we want to re-include RSE in Photon, we could do so for M6 if
>>> someone grants me a place to publish it & permission to do so. We've got a
>>> fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and
>>> it currently builds against Photon.0.M4. This could easily be moved to an
>>> Eclipse HIPP, such as this one [2], if I can get permission to edit jobs
>>> there & publish to download.eclipse.org.
>>>
>>
>> It's not much allowed to build and publish external (non-Eclipse.org)
>> sources on Eclipse.org infrastructre.
>> The only way forward, should we want to re-include RSE in Photon, would
>> be that Rob and you get the patches you authored merged in the actual
>> TM/RSE repository at Eclipse.org.
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> --
>
> Nick Boldt
>
> Senior Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> 
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews   Red Hat
> 
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Nick Boldt
Yes, that's what I was suggesting. We contribute the handful of fixes in
Rob's fork back to the master repo on git.eclipse.org, build it on a HIPP,
and contribute it into Photon.0.M6.

If someone nominates me as a committer to TM/RSE, I'll make this happen.

On Wed, Jan 31, 2018 at 12:13 PM, Mickael Istria  wrote:

>
>
> On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt  wrote:
>
>> Should we want to re-include RSE in Photon, we could do so for M6 if
>> someone grants me a place to publish it & permission to do so. We've got a
>> fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and
>> it currently builds against Photon.0.M4. This could easily be moved to an
>> Eclipse HIPP, such as this one [2], if I can get permission to edit jobs
>> there & publish to download.eclipse.org.
>>
>
> It's not much allowed to build and publish external (non-Eclipse.org)
> sources on Eclipse.org infrastructre.
> The only way forward, should we want to re-include RSE in Photon, would be
> that Rob and you get the patches you authored merged in the actual TM/RSE
> repository at Eclipse.org.
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED. 
@ @redhatnews   Red Hat

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Mickael Istria
On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt  wrote:

> Should we want to re-include RSE in Photon, we could do so for M6 if
> someone grants me a place to publish it & permission to do so. We've got a
> fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and
> it currently builds against Photon.0.M4. This could easily be moved to an
> Eclipse HIPP, such as this one [2], if I can get permission to edit jobs
> there & publish to download.eclipse.org.
>

It's not much allowed to build and publish external (non-Eclipse.org)
sources on Eclipse.org infrastructre.
The only way forward, should we want to re-include RSE in Photon, would be
that Rob and you get the patches you authored merged in the actual TM/RSE
repository at Eclipse.org.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Eugene Tarassov
Hi,

TCF is re-enabled after removing TCF/RSE integration from SimRel.

Thanks,
Eugene

-Original Message-
From: Frederic Gurr [mailto:frederic.g...@eclipse-foundation.org] 
Sent: Tuesday, January 30, 2018 1:13 PM
To: Cross project issues 
Cc: Eugene Tarassov ; zu...@w3des.net; 
sbern...@sierrawireless.com; and...@xored.com
Subject: SimRel - TM contribution has been disabled

Hi,

As announced before, the Target Management (TM) contribution has been
disabled.

Even though some code has been moved to CDT (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=527575), there are still
two features remaining (org.eclipse.rse and org.eclipse.rse.useractions).

Since disabling the TM contribution caused issues, I had to disable the
following contributions:

* TCF
* PDT
* LDT
* DLTK

Please fix the dependencies (it might only require changes in TCF, but I
did not dig deeper) and re-enable the contributions. Project leads of
affected projects have been added in CC.


Regards,

Fred

-- 
Frederic Gurr

Release Engineer
Eclipse Foundation
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

2018-01-31 Thread Nick Boldt
Should we want to re-include RSE in Photon, we could do so for M6 if
someone grants me a place to publish it & permission to do so. We've got a
fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and
it currently builds against Photon.0.M4. This could easily be moved to an
Eclipse HIPP, such as this one [2], if I can get permission to edit jobs
there & publish to download.eclipse.org.

[1] https://github.com/robstryker/org.eclipse.tm
[2] https://hudson.eclipse.org/tm/



On Wed, Jan 31, 2018 at 11:31 AM, Kaloyan Raev  wrote:

> Hi,
>
> I removed the DLTK integration with RSE from SimRel:
> https://git.eclipse.org/r/116449/
>
> With this change it should be possible to re-enable DLTK and PDT.
>
> Thanks,
> Kaloyan
>
> On Tue, Jan 30, 2018 at 11:13 PM, Frederic Gurr  foundation.org> wrote:
>
>> Hi,
>>
>> As announced before, the Target Management (TM) contribution has been
>> disabled.
>>
>> Even though some code has been moved to CDT (see
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=527575), there are still
>> two features remaining (org.eclipse.rse and org.eclipse.rse.useractions).
>>
>> Since disabling the TM contribution caused issues, I had to disable the
>> following contributions:
>>
>> * TCF
>> * PDT
>> * LDT
>> * DLTK
>>
>> Please fix the dependencies (it might only require changes in TCF, but I
>> did not dig deeper) and re-enable the contributions. Project leads of
>> affected projects have been added in CC.
>>
>>
>> Regards,
>>
>> Fred
>>
>> --
>> Frederic Gurr
>>
>> Release Engineer
>> Eclipse Foundation
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> 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@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED. 
@ @redhatnews   Red Hat

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev