Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

[Ed Merks]

+++1

Anyone feeling the need to add XML comments please use the "Show 
Properties" from the context menu and put this content in the 
Description property instead.  And in general, you should expect that if 
you don't normalize the contents of your file, someone else will do so 
in the future *without asking*.


I ran into this "a great many files changed" issue again when I tried to 
disable XWT.  That exercise failed because Papyrus depends on XWT.  
Unfortunately the XWT team is entirely unresponsive:


  https://bugs.eclipse.org/bugs/show_bug.cgi?id=553883

Perhaps a notification issue (in addition to not monitoring this mailing 
list) so I've just now tried adding to the CC list someone who appears 
to actually do commits:


https://git.eclipse.org/c/xwt/org.eclipse.xwt.git/log/

Regards,
Ed

On 09.01.2020 20:17, Jonah Graham wrote:
> So there isn't really a good excuse not to use the aggregation 
editor.  Admitted I too typically just edit my *.aggrcon files 
actually, but mostly because saving creates such a big delta.  But the 
editor does have advantages, i.e., I can see if I pasted the URL 
incorrectly and that the  IUs resolve correctly.   More importantly, 
as I mentioned previously, if you're adding a feature that needs to be 
in a category or removing a feature when it or any other feature after 
it are in a category, you will break the model if you do this 
textually.  And there were many such broken links as a result...


I always do my edits in the editor and normally try to ignore all the 
diffs that don't apply.


However I have upcoming a number of changes to CDT that will affect 
features and possibly categories. To make this feasible I propose we 
normalize the *.aggrcon files. As such I posted a gerrit for just 
that. https://git.eclipse.org/r/#/c/155571/


Any objections to pushing? If timing is bad, I can redo this just 
after M1 is done next week.


Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com 


On Tue, 10 Dec 2019 at 06:12, Ed Merks > wrote:


Hi,

On a more positive note, for the 2019-12 release, the installer
exploits the platform's cool "link handler" support that was
implemented by Matthias Becker; thanks Lars Vogel for drawing my
attention to this gem.

As an example, this means that clicking the following link can
automatically launch the installer, in this case, initializing it
in order to provision a specialized IDE for contributing to SimRel.


eclipse+installer:https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/interim/SimultaneousReleaseTrainConfiguration.setup

It's kind of a chicken-and-egg problem that you must first
download and register the installer once.  To make this step more 
self-documenting, I've created a "help" page that describes how to
exploit this feature:


https://www.eclipse.org/setups/installer/?url=https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/interim/SimultaneousReleaseTrainConfiguration.setup=true

This page uses the documentation extracted from the configuration
(specified in the query parameter) so that it's contextually
tailored, including all its links.

I've updated the simrel wiki to describe this automated approach
to set up an environment for contributing to simrel:


https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#Get_the_simrel.build_project

So there isn't really a good excuse not to use the aggregation
editor.  Admitted I too typically just edit my *.aggrcon files
actually, but mostly because saving creates such a big delta.  But
the editor does have advantages, i.e., I can see if I pasted the
URL incorrectly and that the  IUs resolve correctly.   More
importantly, as I mentioned previously, if you're adding a feature
that needs to be in a category or removing a feature when it or
any other feature after it are in a category, you will break the
model if you do this textually.  And there were many such broken
links as a result...

This same mechanism can be used to provision a development
environment with the source for the full Platform SDK:


https://www.eclipse.org/setups/installer/?url=https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/interim/PlatformSDKConfiguration.setup=true

You can do this for your own projects too.  One-click
contributions from your community are at you finger tips.

In addition, this same mechanism can also be used to install
marketplace listings, e.g.,


https://www.eclipse.org/setups/installer/?url=https://marketplace.eclipse.org/content/wild-web-developer-html-css-javascript-typescript-nodejs-angular-json-yaml-kubernetes-xml=true

So the installer now allows users to create an installation that
includes one more additional marketplace listings as well.

To help make the marketplace listings 

Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

[Jonah Graham]

> So there isn't really a good excuse not to use the aggregation editor.
Admitted I too typically just edit my *.aggrcon files actually, but mostly
because saving creates such a big delta.  But the editor does have
advantages, i.e., I can see if I pasted the URL incorrectly and that the
IUs resolve correctly.   More importantly, as I mentioned previously, if
you're adding a feature that needs to be in a category or removing a
feature when it or any other feature after it are in a category, you will
break the model if you do this textually.  And there were many such broken
links as a result...

I always do my edits in the editor and normally try to ignore all the diffs
that don't apply.

However I have upcoming a number of changes to CDT that will affect
features and possibly categories. To make this feasible I propose we
normalize the *.aggrcon files. As such I posted a gerrit for just that.
https://git.eclipse.org/r/#/c/155571/

Any objections to pushing? If timing is bad, I can redo this just after M1
is done next week.

Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Tue, 10 Dec 2019 at 06:12, Ed Merks  wrote:

> Hi,
>
> On a more positive note, for the 2019-12 release, the installer exploits
> the platform's cool "link handler" support that was implemented by Matthias
> Becker; thanks Lars Vogel for drawing my attention to this gem.
>
> As an example, this means that clicking the following link can
> automatically launch the installer, in this case, initializing it in order
> to provision a specialized IDE for contributing to SimRel.
>
>
> eclipse+installer:https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/interim/SimultaneousReleaseTrainConfiguration.setup
>
> It's kind of a chicken-and-egg problem that you must first download and
> register the installer once.  To make this step more  self-documenting,
> I've created a "help" page that describes how to exploit this feature:
>
>
> https://www.eclipse.org/setups/installer/?url=https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/interim/SimultaneousReleaseTrainConfiguration.setup=true
>
> This page uses the documentation extracted from the configuration
> (specified in the query parameter) so that it's contextually tailored,
> including all its links.
>
> I've updated the simrel wiki to describe this automated approach to set up
> an environment for contributing to simrel:
>
>
> https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#Get_the_simrel.build_project
>
> So there isn't really a good excuse not to use the aggregation editor.
> Admitted I too typically just edit my *.aggrcon files actually, but mostly
> because saving creates such a big delta.  But the editor does have
> advantages, i.e., I can see if I pasted the URL incorrectly and that the
> IUs resolve correctly.   More importantly, as I mentioned previously, if
> you're adding a feature that needs to be in a category or removing a
> feature when it or any other feature after it are in a category, you will
> break the model if you do this textually.  And there were many such broken
> links as a result...
>
> This same mechanism can be used to provision a development environment
> with the source for the full Platform SDK:
>
>
> https://www.eclipse.org/setups/installer/?url=https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/interim/PlatformSDKConfiguration.setup=true
>
> You can do this for your own projects too.  One-click contributions from
> your community are at you finger tips.
>
> In addition, this same mechanism can also be used to install marketplace
> listings, e.g.,
>
>
> https://www.eclipse.org/setups/installer/?url=https://marketplace.eclipse.org/content/wild-web-developer-html-css-javascript-typescript-nodejs-angular-json-yaml-kubernetes-xml=true
>
> So the installer now allows users to create an installation that includes
> one more additional marketplace listings as well.
>
> To help make the marketplace listings great again, the listings are now
> tested daily.  Bad listings give a bad impression of Eclipse, especially
> when we provide them ourselves.
>
> Currently there are 1316 marketplace listings that specify update sites.
> Of those, 541 have problems; some have minor problems, e.g.,  it can't be
> installed in the versions of Eclipse with which it's specified to be
> compatible, but many have major problems, i.e., the p2 site doesn't exist
> or doesn't contain the bundles/features that are required by the listing.
> The user perception is that anything they get from marketplace is "Eclipse"
> and any problem with those are "Eclipse" problems...
>
> If you maintain a listing, you can review the test results for your
> listing as follows:
>
>
> https://www.eclipse.org/setups/marketplace/?url=https://marketplace.eclipse.org/content/wild-web-developer-html-css-javascript-typescript-nodejs-angular-json-yaml-kubernetes-xml
>
> For the above listing, we can see that it doesn't actually 

Re: [cross-project-issues-dev] Info centers

[Lars Vogel]

Thanks Fred, latest will be great compared to fine before ;-)

Current solution (redirect to root) is not fine. :-)

Frederic Gurr  schrieb am Do., 9.
Jan. 2020, 17:13:

> Hi,
> I wouldn't call this a fine link or good coverage. The link efers to an
> Neon infocenter from 2016/2017. So it's completely outdated.
> As stated in the bug, the goal is to have the /latest/ links in the Google
> index and not content from random old versions.
>
> We will try to put redirects in place to avoid confusion and "dead ends".
>
> Regards,
>
> Fred
>
> On Thu, 9 Jan 2020, 16:05 Lars Vogel,  wrote:
>
>> Just Googled for the Oomph Git setup tasks which resulted in this fine
>> link:
>>
>>
>> https://help.eclipse.org/neon/topic/org.eclipse.oomph.setup.doc/javadoc/org/eclipse/oomph/setup/git/GitCloneTask.html
>>
>> Clicking on it, brings me to:
>>
>> https://www.eclipse.org/documentation/
>>
>> So currently it looks like we lost our good Google coverage of Eclipse
>> help.
>>
>> Best regards, Lars
>>
>> P.S. will also add this to the bug
>>
>> On Fri, Dec 13, 2019 at 3:57 PM Jonah Graham 
>> wrote:
>> >
>> > Done https://bugs.eclipse.org/bugs/show_bug.cgi?id=558301
>> >
>> > Probably needs better component, please change component as you see fit.
>> > ~~~
>> > Jonah Graham
>> > Kichwa Coders
>> > www.kichwacoders.com
>> >
>> >
>> > On Fri, 13 Dec 2019 at 09:49, Denis Roy <
>> denis@eclipse-foundation.org> wrote:
>> >>
>> >> Jonah,
>> >>
>> >> That's a great point.  I think we can do something smart here:
>> >>
>> >> When a user hits https://eclipse.org/documentation/ we could examine
>> the referer, and add some text at the top of the page to indicate the user
>> has requested older docs, with a suggested link to the same doc on the
>> latest install.
>> >>
>> >> That will help newer docs rank on search engines, help de-list older
>> docs, and still provide service to the user.
>> >>
>> >> We should also verify that we are sending a 301 Permanent redirect,
>> not a 302 Temporary one.
>> >>
>> >> If you think this makes sense, I think next step is a bug.
>> >>
>> >>
>> >> Denis
>> >>
>> >>
>> >> On 2019-12-13 9:25 a.m., Jonah Graham wrote:
>> >>
>> >> Hi Fred,
>> >>
>> >> I think it is great to get rid of the old documentation - indeed the
>> other day I did a google search and didn't realize I was looking at an old
>> version of the documentation.
>> >>
>> >> That leads me to my issue with removing - and I don't have a solution,
>> just a concern. Googling or duckduckgoing many eclipse topics have
>> help.eclipse.org/kepler in the results (some have neon). What is the
>> effect on SEO of just removing kepler? Will all relevant search results
>> from google just disappear making it harder to find information until
>> google and the like re-rank the results higher?
>> >>
>> >>  Almost all the results work if kepler is just replaced with 2019-09
>> (or 2019-12 or latest presumably).
>> >>
>> >> I see in the time that I have been writing the email that
>> help.eclipse.org/kepler has disappeared - the effect that it is harder
>> to find the results because the search within infocenter is not as good as
>> google.
>> >>
>> >> Thanks
>> >> Jonah
>> >>
>> >>
>> >>
>> >>
>> >> ~~~
>> >> Jonah Graham
>> >> Kichwa Coders
>> >> www.kichwacoders.com
>> >>
>> >>
>> >> On Fri, 13 Dec 2019 at 08:22, Frederic Gurr <
>> frederic.g...@eclipse-foundation.org> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> To further streamline our services and reduce maintenance overhead we
>> >>> will no longer host info centers at https://help.eclipse.org that are
>> >>> older than two years (or 8 quarterly releases).
>> >>>
>> >>> For older releases people will be advised to run the infocenters
>> locally
>> >>> by downloading the corresponding Eclipse IDE (Eclipse SDK or EPP
>> >>> package) from
>> >>> * https://archive.eclipse.org/eclipse/downloads/ or
>> >>> * https://www.eclipse.org/downloads/packages/release/
>> >>>
>> >>> How to start or stop information center from command line:
>> >>> *
>> >>>
>> https://help.eclipse.org/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fua_help_setup_infocenter.htm
>> >>>
>> >>> People trying to access old infocenter URLs will be forwarded to
>> >>> https://www.eclipse.org/documentation
>> >>>
>> >>> Please let me know if you have any questions or concerns.
>> >>>
>> >>> Regards,
>> >>>
>> >>> Fred
>> >>>
>> >>> --
>> >>> Frederic Gurr
>> >>> Release Engineer | Eclipse Foundation Europe GmbH
>> >>>
>> >>> Annastr. 46, D-64673 Zwingenberg
>> >>> Handelsregister: Darmstadt HRB 92821
>> >>> Managing Directors: Ralph Mueller, Mike Milinkovich, Gaël Blondelle
>> >>> ___
>> >>> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> >>
>> >>
>> >> 

Re: [cross-project-issues-dev] Info centers

[Frederic Gurr]

Hi,
I wouldn't call this a fine link or good coverage. The link efers to an
Neon infocenter from 2016/2017. So it's completely outdated.
As stated in the bug, the goal is to have the /latest/ links in the Google
index and not content from random old versions.

We will try to put redirects in place to avoid confusion and "dead ends".

Regards,

Fred

On Thu, 9 Jan 2020, 16:05 Lars Vogel,  wrote:

> Just Googled for the Oomph Git setup tasks which resulted in this fine
> link:
>
>
> https://help.eclipse.org/neon/topic/org.eclipse.oomph.setup.doc/javadoc/org/eclipse/oomph/setup/git/GitCloneTask.html
>
> Clicking on it, brings me to:
>
> https://www.eclipse.org/documentation/
>
> So currently it looks like we lost our good Google coverage of Eclipse
> help.
>
> Best regards, Lars
>
> P.S. will also add this to the bug
>
> On Fri, Dec 13, 2019 at 3:57 PM Jonah Graham 
> wrote:
> >
> > Done https://bugs.eclipse.org/bugs/show_bug.cgi?id=558301
> >
> > Probably needs better component, please change component as you see fit.
> > ~~~
> > Jonah Graham
> > Kichwa Coders
> > www.kichwacoders.com
> >
> >
> > On Fri, 13 Dec 2019 at 09:49, Denis Roy <
> denis@eclipse-foundation.org> wrote:
> >>
> >> Jonah,
> >>
> >> That's a great point.  I think we can do something smart here:
> >>
> >> When a user hits https://eclipse.org/documentation/ we could examine
> the referer, and add some text at the top of the page to indicate the user
> has requested older docs, with a suggested link to the same doc on the
> latest install.
> >>
> >> That will help newer docs rank on search engines, help de-list older
> docs, and still provide service to the user.
> >>
> >> We should also verify that we are sending a 301 Permanent redirect, not
> a 302 Temporary one.
> >>
> >> If you think this makes sense, I think next step is a bug.
> >>
> >>
> >> Denis
> >>
> >>
> >> On 2019-12-13 9:25 a.m., Jonah Graham wrote:
> >>
> >> Hi Fred,
> >>
> >> I think it is great to get rid of the old documentation - indeed the
> other day I did a google search and didn't realize I was looking at an old
> version of the documentation.
> >>
> >> That leads me to my issue with removing - and I don't have a solution,
> just a concern. Googling or duckduckgoing many eclipse topics have
> help.eclipse.org/kepler in the results (some have neon). What is the
> effect on SEO of just removing kepler? Will all relevant search results
> from google just disappear making it harder to find information until
> google and the like re-rank the results higher?
> >>
> >>  Almost all the results work if kepler is just replaced with 2019-09
> (or 2019-12 or latest presumably).
> >>
> >> I see in the time that I have been writing the email that
> help.eclipse.org/kepler has disappeared - the effect that it is harder to
> find the results because the search within infocenter is not as good as
> google.
> >>
> >> Thanks
> >> Jonah
> >>
> >>
> >>
> >>
> >> ~~~
> >> Jonah Graham
> >> Kichwa Coders
> >> www.kichwacoders.com
> >>
> >>
> >> On Fri, 13 Dec 2019 at 08:22, Frederic Gurr <
> frederic.g...@eclipse-foundation.org> wrote:
> >>>
> >>> Hi,
> >>>
> >>> To further streamline our services and reduce maintenance overhead we
> >>> will no longer host info centers at https://help.eclipse.org that are
> >>> older than two years (or 8 quarterly releases).
> >>>
> >>> For older releases people will be advised to run the infocenters
> locally
> >>> by downloading the corresponding Eclipse IDE (Eclipse SDK or EPP
> >>> package) from
> >>> * https://archive.eclipse.org/eclipse/downloads/ or
> >>> * https://www.eclipse.org/downloads/packages/release/
> >>>
> >>> How to start or stop information center from command line:
> >>> *
> >>>
> https://help.eclipse.org/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fua_help_setup_infocenter.htm
> >>>
> >>> People trying to access old infocenter URLs will be forwarded to
> >>> https://www.eclipse.org/documentation
> >>>
> >>> Please let me know if you have any questions or concerns.
> >>>
> >>> Regards,
> >>>
> >>> Fred
> >>>
> >>> --
> >>> Frederic Gurr
> >>> Release Engineer | Eclipse Foundation Europe GmbH
> >>>
> >>> Annastr. 46, D-64673 Zwingenberg
> >>> Handelsregister: Darmstadt HRB 92821
> >>> Managing Directors: Ralph Mueller, Mike Milinkovich, Gaël Blondelle
> >>> ___
> >>> 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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >>
> >> 

Re: [cross-project-issues-dev] Info centers

[Lars Vogel]

Just Googled for the Oomph Git setup tasks which resulted in this fine link:

https://help.eclipse.org/neon/topic/org.eclipse.oomph.setup.doc/javadoc/org/eclipse/oomph/setup/git/GitCloneTask.html

Clicking on it, brings me to:

https://www.eclipse.org/documentation/

So currently it looks like we lost our good Google coverage of Eclipse help.

Best regards, Lars

P.S. will also add this to the bug

On Fri, Dec 13, 2019 at 3:57 PM Jonah Graham  wrote:
>
> Done https://bugs.eclipse.org/bugs/show_bug.cgi?id=558301
>
> Probably needs better component, please change component as you see fit.
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>
>
> On Fri, 13 Dec 2019 at 09:49, Denis Roy  
> wrote:
>>
>> Jonah,
>>
>> That's a great point.  I think we can do something smart here:
>>
>> When a user hits https://eclipse.org/documentation/ we could examine the 
>> referer, and add some text at the top of the page to indicate the user has 
>> requested older docs, with a suggested link to the same doc on the latest 
>> install.
>>
>> That will help newer docs rank on search engines, help de-list older docs, 
>> and still provide service to the user.
>>
>> We should also verify that we are sending a 301 Permanent redirect, not a 
>> 302 Temporary one.
>>
>> If you think this makes sense, I think next step is a bug.
>>
>>
>> Denis
>>
>>
>> On 2019-12-13 9:25 a.m., Jonah Graham wrote:
>>
>> Hi Fred,
>>
>> I think it is great to get rid of the old documentation - indeed the other 
>> day I did a google search and didn't realize I was looking at an old version 
>> of the documentation.
>>
>> That leads me to my issue with removing - and I don't have a solution, just 
>> a concern. Googling or duckduckgoing many eclipse topics have 
>> help.eclipse.org/kepler in the results (some have neon). What is the effect 
>> on SEO of just removing kepler? Will all relevant search results from google 
>> just disappear making it harder to find information until google and the 
>> like re-rank the results higher?
>>
>>  Almost all the results work if kepler is just replaced with 2019-09 (or 
>> 2019-12 or latest presumably).
>>
>> I see in the time that I have been writing the email that 
>> help.eclipse.org/kepler has disappeared - the effect that it is harder to 
>> find the results because the search within infocenter is not as good as 
>> google.
>>
>> Thanks
>> Jonah
>>
>>
>>
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders
>> www.kichwacoders.com
>>
>>
>> On Fri, 13 Dec 2019 at 08:22, Frederic Gurr 
>>  wrote:
>>>
>>> Hi,
>>>
>>> To further streamline our services and reduce maintenance overhead we
>>> will no longer host info centers at https://help.eclipse.org that are
>>> older than two years (or 8 quarterly releases).
>>>
>>> For older releases people will be advised to run the infocenters locally
>>> by downloading the corresponding Eclipse IDE (Eclipse SDK or EPP
>>> package) from
>>> * https://archive.eclipse.org/eclipse/downloads/ or
>>> * https://www.eclipse.org/downloads/packages/release/
>>>
>>> How to start or stop information center from command line:
>>> *
>>> https://help.eclipse.org/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fua_help_setup_infocenter.htm
>>>
>>> People trying to access old infocenter URLs will be forwarded to
>>> https://www.eclipse.org/documentation
>>>
>>> Please let me know if you have any questions or concerns.
>>>
>>> Regards,
>>>
>>> Fred
>>>
>>> --
>>> Frederic Gurr
>>> Release Engineer | Eclipse Foundation Europe GmbH
>>>
>>> Annastr. 46, D-64673 Zwingenberg
>>> Handelsregister: Darmstadt HRB 92821
>>> Managing Directors: Ralph Mueller, Mike Milinkovich, Gaël Blondelle
>>> ___
>>> 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://www.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://www.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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht 

Re: [cross-project-issues-dev] Bugzilla down?

[Denis Roy]

You folks are on the ball!


Hi,

The monitor Bugzilla
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=12345) is back UP (HTTP
200 - OK) (It was down for 1 minutes and 59 seconds).

*Event timestamp:* 2020-01-09 07:43:43 UTC-5


Not sure what happened, but I'll look into it.


Denis




On 2020-01-09 7:44 a.m., Wim Jongman wrote:
> Hi,
>
> Bugzilla seems to be down.
>
> Cheers,
>
> Wim
>
> ___
> 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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Bugzilla down?

[Paul Pazderski]

Works for me too but https://status.eclipse.org/ shows it as flaky so it 
might have been down for a moment.


Paul

Am 09.01.2020 um 13:55 schrieb Daniel Megert:

It works for me.

Dani



From: Wim Jongman 
To: Cross project issues 
Date: 09.01.2020 13:47
Subject: [EXTERNAL] [cross-project-issues-dev] Bugzilla down?
Sent by: cross-project-issues-dev-boun...@eclipse.org




Hi,

Bugzilla seems to be down.

Cheers,

Wim___
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://www.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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Bugzilla down?

[Daniel Megert]

It works for me.

Dani



From:   Wim Jongman 
To: Cross project issues 
Date:   09.01.2020 13:47
Subject:[EXTERNAL] [cross-project-issues-dev] Bugzilla down?
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi,

Bugzilla seems to be down.

Cheers,

Wim___
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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Bugzilla down?

[Wim Jongman]

Hi,

Bugzilla seems to be down.

Cheers,

Wim
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev