Re: [cross-project-issues-dev] [epp-dev] Photon M6 is available now

[Frederic Gurr]

Hi,

If nobody raises concerns before Monday, March 26th, I will remove M4
from the composite repository.


Regards,

Fred


-- 
Frederic Gurr

Release Engineer
Eclipse Foundation

On 20.03.2018 12:11, Stephan Herrmann wrote:
> Have you seen https://bugs.eclipse.org/bugs/show_bug.cgi?id=532625 ?
> I don't know if this explains all symptoms you are observing,
> in particular why *expected* updates were *not* proposed.
> 
> Anyway, I think it would be good to remove M4 from the composite sooner,
> rather than later, to effectively test if all problems are indeed
> resolved in M6.
> Any objections?
> 
> Stephan
> 
> On 20.03.2018 09:35, Wim Jongman wrote:
>> Hi,
>>
>> For people also struggling with the upgrade from M5 to M6 with [1]. I
>> resolved my issues by _*removing all update sites*_ except:
>>
>> Photon - http://download.eclipse.org/releases/photon/
>> 
>> Photon Staging - http://download.eclipse.org/staging/photon/
>> 
>> The Eclipse Project Updates -
>> http://download.eclipse.org/eclipse/updates/4.8
>> 
>>
>> Then restart and check for updates finally gave me something else
>> besides "objects team patch for jdt/core"
>>
>> It was probably me and could be a stale cache or something else, but
>> in case you face the same issue you could try what worked for me.
>>
>> Cheers,
>>
>> Wim
>>
>>
>> [1]
>> https://wiki.eclipse.org/FAQ_How_do_I_upgrade_Eclipse_IDE%3F#Beta-testing_milestones_and_release_candidates
>> 
>>
>>
>>
>>
>> On Sat, Mar 17, 2018 at 9:20 AM, Markus Knauer
>> mailto:mkna...@eclipsesource.com>> wrote:
>>
>>     That was a minor error and has been corrected now.
>>
>>     Thanks,
>>     Markus
>>
>>     On 16 March 2018 at 22:50, Mickael Istria > > wrote:
>>
>>     Hi,
>>
>>     EPP site that's composited in SimRel repo (
>> http://download.eclipse.org/technology/epp/packages/photon/
>>     
>> ) seems to miss reference to the M6 release so the "Check for
>>     updates" doesn't work going from M5 to M6.
>>     Is this expected?
>>
>>     Cheers
>>
>>     ___
>>     epp-dev mailing list
>>     epp-...@eclipse.org 
>>     To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>>     https://dev.eclipse.org/mailman/listinfo/epp-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
>>
> 
> ___
> 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] Disk usage report for HIPP/JIPPs

[genie]

Compiled 2018-03-20-13:30:01

Projects exceeding 80G of disk space on HIPP/JIPPs:
===
746G /jobs/genie.packaging
268G /jobs/genie.openj9
182G /jobs/genie.kitalpha
175G /jobs/genie.capella
97G /jobs/genie.platform
92G /jobs/genie.osee
82G /jobs/genie.ice
81G /jobs/genie.xtext
===

If you find your project's name in the above list, please check
your Hudson/Jenkins configuration and try to lower the disk usage.

You can find more information about CI best practices and disk usage
here: https://wiki.eclipse.org/CI_best_practices#Disk_usage.
___
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] Reminder: Oxygen Update 3a (4.7.3a) - Shipping Java 10 (18.3)

[Daniel Megert]

I hope by now projects learned from their Planning Council representative 
or by following the Planning Council mailing list, that very soon after 
Oxygen Update 3 (4.7.3) tomorrow, we will have another update release to 
accommodate Java 10. GA is Wednesday, April 11.

Here is the schedule: 
https://wiki.eclipse.org/Oxygen/Simultaneous_Release_Plan#Oxygen.3a. As 
you can see, for +0 projects RC1 is already this Friday.

Please make sure to test the EPPs (or available downloads) carefully and 
report severe bugs directly on this mailing list with a link to the bug 
report.

NOTE: Only projects providing changes needed for Java 10 (18.3) can 
participate in this release.

Dani

___
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] [epp-dev] Photon M6 is available now

[Stephan Herrmann]

Have you seen https://bugs.eclipse.org/bugs/show_bug.cgi?id=532625 ?
I don't know if this explains all symptoms you are observing,
in particular why *expected* updates were *not* proposed.

Anyway, I think it would be good to remove M4 from the composite sooner,
rather than later, to effectively test if all problems are indeed resolved in 
M6.
Any objections?

Stephan

On 20.03.2018 09:35, Wim Jongman wrote:

Hi,

For people also struggling with the upgrade from M5 to M6 with [1]. I resolved 
my issues by _*removing all update sites*_ except:

Photon - http://download.eclipse.org/releases/photon/ 

Photon Staging - http://download.eclipse.org/staging/photon/ 

The Eclipse Project Updates - http://download.eclipse.org/eclipse/updates/4.8 


Then restart and check for updates finally gave me something else besides "objects 
team patch for jdt/core"

It was probably me and could be a stale cache or something else, but in case 
you face the same issue you could try what worked for me.

Cheers,

Wim


[1] https://wiki.eclipse.org/FAQ_How_do_I_upgrade_Eclipse_IDE%3F#Beta-testing_milestones_and_release_candidates 





On Sat, Mar 17, 2018 at 9:20 AM, Markus Knauer mailto:mkna...@eclipsesource.com>> wrote:

That was a minor error and has been corrected now.

Thanks,
Markus

On 16 March 2018 at 22:50, Mickael Istria mailto:mist...@redhat.com>> wrote:

Hi,

EPP site that's composited in SimRel repo ( 
http://download.eclipse.org/technology/epp/packages/photon/
 ) seems to 
miss reference to the M6 release so the "Check for
updates" doesn't work going from M5 to M6.
Is this expected?

Cheers

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



___
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] Gerrit and Jenkins, tips and news

[Lars Vogel]

Thanks Mikael. Opened: https://bugs.eclipse.org/bugs/show_bug.cgi?id=532646

On Tue, Mar 20, 2018 at 11:05 AM, Mikaël Barbero <
mikael.barb...@eclipse-foundation.org> wrote:

> Simply open a bug against Community > CI Jenkins (
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=
> Community&component=CI-Jenkins) asking for specific plugin to be
> installed. You will have to configure your jobs to use the plugin though.
>
> Cheers,
>
> --
> *Mikaël Barbero - *Eclipse Foundation
> IT Services - Release Engineering
> 📱 (+33) 642 028 039
> 📧 mikael.barb...@eclipse-foundation.org
> 🐦 @mikbarbero
>
> Le 20 mars 2018 à 10:49, Lars Vogel  a écrit :
>
> Hi Mikael,
>
> what is the process if we want additional plug-ins for Jenkins?
>
> For example, the Warnings-Plugin looks useful to me to validate via Gerrit
> verification builds, that the number of compiler warnings do not increase.
>
> References:
> https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin
> https://stackoverflow.com/questions/38308496/how-do-i-
> fail-a-build-in-jenkins-if-the-number-of-compiler-warnings-increases
>
> Best regards, Lars
>
>
>
> On Wed, Mar 14, 2018 at 9:43 AM, Mikaël Barbero  foundation.org> wrote:
>
>>
>> I would argue that the more tedious problem is having tests that
>> sometimes fail. I've been waging a war against intermittent test failures
>> in JBoss Tools for years. Some have been fixed by rewriting, some removed,
>> and some fixed by upgrading the infrastructure (eg., giving slave nodes
>> more RAM or more disk).
>>
>>
>> I can't agree more that flaky tests should be addressed at all costs. But
>> it's a reality today, and having to re-trigger build of gerrit patchsets
>> from Jenkins can be tedious. This is just a little help (that shall not
>> hinder the effort to eradicate flaky tests)
>>
>>
>> Another way to manage this problem is to install the Naginator plugin to
>> your JIPP: "Naginator is a plugin that schedules a new build immediately
>> following a build failure, thereby nagging the project members that the
>> build is failing." Can be configured to define number of rebuilds,
>> frequency of rebuilds, etc.
>>
>>
>> It is probably perfectly reasonable to run this plugin on the RedHat
>> build infra, but I must forbid this plugin on the Eclipse infra for the
>> foreseeable future. Some projects are already experiencing huge variation
>> on their build time during peak hours, such a plugin would just make it
>> worse for everybody.
>>
>> We are working on isolating projects one from each other. Until then,
>> thank you for not using Naginator or similar plugin.
>>
>> Thanks.
>>
>> --
>> *Mikaël Barbero - *Eclipse Foundation
>> IT Services - Release Engineering
>> 📱 (+33) 642 028 039
>> 📧 mikael.barb...@eclipse-foundation.org
>> 🐦 @mikbarbero
>>
>>
>>
>>
>>
>> On Mon, Mar 12, 2018 at 9:25 AM, Mikaël Barbero <
>> mikael.barb...@eclipse-foundation.org> wrote:
>>
>>> Hi,
>>>
>>> For those of you who use a JIPP to build Gerrit patch sets, you may have
>>> noticed that the user "Hudson CI" has been renamed to "CI Bot". This is
>>> purely cosmetic.
>>>
>>> Also, the documentation about how to setup the Gerrit trigger Jenkins
>>> plugin has been revamped and is now available here
>>> https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin
>>>
>>> I would like to draw you attention to the possible triggers you can
>>> setup (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers).
>>> Many of you want to re-trigger a build when it fails (e.g., because of
>>> flaky tests). It can be tedious to have to go to Jenkins just to do that.
>>> The Gerrit trigger Jenkins plugin is not only able to trigger a build on a
>>> new patch set. It lets you define triggers on comment values (e.g., if a
>>> comment contains "run CI"). Have a look at the previous link for an example.
>>>
>>> Cheers,
>>>
>>>
>>> --
>>> *Mikaël Barbero - *Eclipse Foundation
>>> IT Services - Release Engineering
>>> 📱 (+33) 642 028 039
>>> 📧 mikael.barb...@eclipse-foundation.org
>>> 🐦 @mikbarbero
>>>
>>>
>>> ___
>>> 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
>> 
>> 
>>
>>
>> “The Only Thing That Is Constant Is Change” - Heraclitus
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, 

Re: [cross-project-issues-dev] Gerrit and Jenkins, tips and news

[Mikaël Barbero]

Simply open a bug against Community > CI Jenkins 
(https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins)
 asking for specific plugin to be installed. You will have to configure your 
jobs to use the plugin though.

Cheers,

--
Mikaël Barbero - Eclipse Foundation
IT Services - Release Engineering
📱 (+33) 642 028 039
📧 mikael.barb...@eclipse-foundation.org
🐦 @mikbarbero

> Le 20 mars 2018 à 10:49, Lars Vogel  a écrit :
> 
> Hi Mikael,
> 
> what is the process if we want additional plug-ins for Jenkins?
> 
> For example, the Warnings-Plugin looks useful to me to validate via Gerrit 
> verification builds, that the number of compiler warnings do not increase.
> 
> References:
> https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin 
> 
> https://stackoverflow.com/questions/38308496/how-do-i-fail-a-build-in-jenkins-if-the-number-of-compiler-warnings-increases
>  
> 
> 
> Best regards, Lars
> 
> 
> 
> On Wed, Mar 14, 2018 at 9:43 AM, Mikaël Barbero 
>  > wrote:
> 
>> I would argue that the more tedious problem is having tests that sometimes 
>> fail. I've been waging a war against intermittent test failures in JBoss 
>> Tools for years. Some have been fixed by rewriting, some removed, and some 
>> fixed by upgrading the infrastructure (eg., giving slave nodes more RAM or 
>> more disk).
> 
> I can't agree more that flaky tests should be addressed at all costs. But 
> it's a reality today, and having to re-trigger build of gerrit patchsets from 
> Jenkins can be tedious. This is just a little help (that shall not hinder the 
> effort to eradicate flaky tests)
> 
>> 
>> Another way to manage this problem is to install the Naginator plugin to 
>> your JIPP: "Naginator is a plugin that schedules a new build immediately 
>> following a build failure, thereby nagging the project members that the 
>> build is failing." Can be configured to define number of rebuilds, frequency 
>> of rebuilds, etc.
> 
> It is probably perfectly reasonable to run this plugin on the RedHat build 
> infra, but I must forbid this plugin on the Eclipse infra for the foreseeable 
> future. Some projects are already experiencing huge variation on their build 
> time during peak hours, such a plugin would just make it worse for everybody.
> 
> We are working on isolating projects one from each other. Until then, thank 
> you for not using Naginator or similar plugin.
> 
> Thanks.
> 
> --
> Mikaël Barbero - Eclipse Foundation
> IT Services - Release Engineering
> 📱 (+33) 642 028 039
> 📧 mikael.barb...@eclipse-foundation.org 
> 
> 🐦 @mikbarbero
> 
>> 
>> 
>> 
>> 
>> On Mon, Mar 12, 2018 at 9:25 AM, Mikaël Barbero 
>> > > wrote:
>> Hi,
>> 
>> For those of you who use a JIPP to build Gerrit patch sets, you may have 
>> noticed that the user "Hudson CI" has been renamed to "CI Bot". This is 
>> purely cosmetic.
>> 
>> Also, the documentation about how to setup the Gerrit trigger Jenkins plugin 
>> has been revamped and is now available here 
>> https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin 
>> 
>> 
>> I would like to draw you attention to the possible triggers you can setup 
>> (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers 
>> ). Many of 
>> you want to re-trigger a build when it fails (e.g., because of flaky tests). 
>> It can be tedious to have to go to Jenkins just to do that. The Gerrit 
>> trigger Jenkins plugin is not only able to trigger a build on a new patch 
>> set. It lets you define triggers on comment values (e.g., if a comment 
>> contains "run CI"). Have a look at the previous link for an example.
>> 
>> Cheers,
>> 
>> 
>> --
>> Mikaël Barbero - Eclipse Foundation
>> IT Services - Release Engineering
>> 📱 (+33) 642 028 039
>> 📧 mikael.barb...@eclipse-foundation.org 
>> 
>> 🐦 @mikbarbero
>> 
>> 
>> ___
>> 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. 
>> @ 

Re: [cross-project-issues-dev] Gerrit and Jenkins, tips and news

[Lars Vogel]

Hi Mikael,

what is the process if we want additional plug-ins for Jenkins?

For example, the Warnings-Plugin looks useful to me to validate via Gerrit
verification builds, that the number of compiler warnings do not increase.

References:
https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin
https://stackoverflow.com/questions/38308496/how-do-i-fail-a-build-in-jenkins-if-the-number-of-compiler-warnings-increases

Best regards, Lars



On Wed, Mar 14, 2018 at 9:43 AM, Mikaël Barbero <
mikael.barb...@eclipse-foundation.org> wrote:

>
> I would argue that the more tedious problem is having tests that sometimes
> fail. I've been waging a war against intermittent test failures in JBoss
> Tools for years. Some have been fixed by rewriting, some removed, and some
> fixed by upgrading the infrastructure (eg., giving slave nodes more RAM or
> more disk).
>
>
> I can't agree more that flaky tests should be addressed at all costs. But
> it's a reality today, and having to re-trigger build of gerrit patchsets
> from Jenkins can be tedious. This is just a little help (that shall not
> hinder the effort to eradicate flaky tests)
>
>
> Another way to manage this problem is to install the Naginator plugin to
> your JIPP: "Naginator is a plugin that schedules a new build immediately
> following a build failure, thereby nagging the project members that the
> build is failing." Can be configured to define number of rebuilds,
> frequency of rebuilds, etc.
>
>
> It is probably perfectly reasonable to run this plugin on the RedHat build
> infra, but I must forbid this plugin on the Eclipse infra for the
> foreseeable future. Some projects are already experiencing huge variation
> on their build time during peak hours, such a plugin would just make it
> worse for everybody.
>
> We are working on isolating projects one from each other. Until then,
> thank you for not using Naginator or similar plugin.
>
> Thanks.
>
> --
> *Mikaël Barbero - *Eclipse Foundation
> IT Services - Release Engineering
> 📱 (+33) 642 028 039
> 📧 mikael.barb...@eclipse-foundation.org
> 🐦 @mikbarbero
>
>
>
>
>
> On Mon, Mar 12, 2018 at 9:25 AM, Mikaël Barbero  foundation.org> wrote:
>
>> Hi,
>>
>> For those of you who use a JIPP to build Gerrit patch sets, you may have
>> noticed that the user "Hudson CI" has been renamed to "CI Bot". This is
>> purely cosmetic.
>>
>> Also, the documentation about how to setup the Gerrit trigger Jenkins
>> plugin has been revamped and is now available here
>> https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin
>>
>> I would like to draw you attention to the possible triggers you can setup
>> (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers). Many
>> of you want to re-trigger a build when it fails (e.g., because of flaky
>> tests). It can be tedious to have to go to Jenkins just to do that. The
>> Gerrit trigger Jenkins plugin is not only able to trigger a build on a new
>> patch set. It lets you define triggers on comment values (e.g., if a
>> comment contains "run CI"). Have a look at the previous link for an example.
>>
>> Cheers,
>>
>>
>> --
>> *Mikaël Barbero - *Eclipse Foundation
>> IT Services - Release Engineering
>> 📱 (+33) 642 028 039
>> 📧 mikael.barb...@eclipse-foundation.org
>> 🐦 @mikbarbero
>>
>>
>> ___
>> 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
> 
> 
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
> ___
> 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
>



-- 
Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
http://www.vogella.com
___
cross-project-issues-dev mailing list
cross-proje

Re: [cross-project-issues-dev] [epp-dev] Photon M6 is available now

[Wim Jongman]

Hi,

For people also struggling with the upgrade from M5 to M6 with [1]. I
resolved my issues by *removing all update sites* except:

Photon - http://download.eclipse.org/releases/photon/
Photon Staging - http://download.eclipse.org/staging/photon/
The Eclipse Project Updates - http://download.eclipse.org/
eclipse/updates/4.8

Then restart and check for updates finally gave me something else besides
"objects team patch for jdt/core"

It was probably me and could be a stale cache or something else, but in
case you face the same issue you could try what worked for me.

Cheers,

Wim


[1] https://wiki.eclipse.org/FAQ_How_do_I_upgrade_Eclipse_IDE%
3F#Beta-testing_milestones_and_release_candidates



On Sat, Mar 17, 2018 at 9:20 AM, Markus Knauer 
wrote:

> That was a minor error and has been corrected now.
>
> Thanks,
> Markus
>
> On 16 March 2018 at 22:50, Mickael Istria  wrote:
>
>> Hi,
>>
>> EPP site that's composited in SimRel repo (
>> http://download.eclipse.org/technology/epp/packages/photon/ ) seems to
>> miss reference to the M6 release so the "Check for updates" doesn't work
>> going from M5 to M6.
>> Is this expected?
>>
>> Cheers
>>
>> ___
>> epp-dev mailing list
>> epp-...@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/epp-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