[cross-project-issues-dev] Service downtime.

Hi Folks, Just to let you know that we've finished moving the hippcentos slave as well as our sonar instance and they are back up. We had some issues with upgrading sonar but it looks ok now. Sorry about the extra time required. -Matt. ___

[cross-project-issues-dev] Correction: Eclipse Top-Level Project Participates in Oxygen

It of course Oxygen! Dani - Forwarded by Daniel Megert/Zurich/IBM on 29.07.2016 17:32 - From: Daniel Megert/Zurich/IBM To: cross-project-issues-dev Date: 29.07.2016 16:37 Subject:Eclipse Top-Level Project Participates in Neon The

[cross-project-issues-dev] Eclipse Top-Level Project Participates in Neon

The Eclipse top-level project participates in Neon with offset +0. For details see https://projects.eclipse.org/projects/eclipse/releases/4.7.0. Dani ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your

Re: [cross-project-issues-dev] Service downtime

On 28/07/2016 12:25, Frederic Gurr wrote: > My suggestion was to get this fixed in Hudson/Sonar plugin. > > In the meantime, Mikael Barbero suggested that you don't need to use the > Sonar plugin to run an analysis. > According to >

Re: [cross-project-issues-dev] [aeri] How To Automatically Create Bug Reports from your Error Reports

For me both the request reopening and the create bug report idea sounds fine. This way there won't any point in time where the user would feel stuck how to give feedback. Which is - if I understand correctly - the purpose of the AERI project. Anyway, thanks for the feedback and also thanks for