Re: [cross-project-issues-dev] Mac signing service issues -- plan for M4

[Mikael Barbero]

The signing issue is due to too much difference between the system clock and 
the time stamping authority (and for some reason, NTP does not work the mac 
signing machine). I manually synched the time on the machine and the signing 
now works properly.

Cheers,
Mikael

> Le 16 déc. 2015 à 22:03, David M Williams  a écrit 
> :
> 
> Given there is currently "no solution in sight" for this week, I think the 
> best course of action is to push ahead, and produce M4 as planned, with 
> affected projects disabling "Mac signing".
> 
> Once we have that build "in hand", a) if the user experience is "really bad", 
> we can reconsider (but as far as know, if they are doing fresh install, then 
> they have to do that "open" or "ctrl-open" trick we have used in the past -- 
> that is, in the past there has been milestones without a Mac signature. b) if 
> enough people are around next week, to redo contributions with Mac signed, we 
> can do an M4a deliverable.
> 
> But, in either case, since we are between a rock and a hard place, I think 
> best to try and produce one as planned. Otherwise, we might be well into 
> January before we could produce one, depending on everyone's holiday 
> schedules.
> 
> Thanks,
> 
> 
> 
> 
> 
> From:Denis Roy 
> To:Cross project issues ,
> Date:12/16/2015 01:36 PM
> Subject:[cross-project-issues-dev] Mac signing service issues
> Sent by:cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> Folks,
> 
> The Mac signing service is currently broken. We're tracking the issue in :
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438 
> 
> 
> Denis
> 
> ___
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
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] Eclipse asked if I trust the Eclipse signing certificate, if I want to install something

[Lars Vogel]

> Did you check the JVM and their trusted certificates? Any changes and/or 
> updates there?

Thanks for the answer Markus. I will have a look, so far I wasn't even
aware that the JVM has its own trusted certificates. I always assumed
Eclipse has this implemented as part of p2.

Best regards, Lars

On Thu, Dec 17, 2015 at 12:38 PM, Markus Knauer
 wrote:

> Are the root certificates that are mentioned in the certificate chain
> trusted?
>
> I tried it with my own Mars.1 RCP/RAP package and it worked without showing
> me this dialog.
>
> Regards,
> Markus
>
>
> On 17 December 2015 at 11:50, Lars Vogel  wrote:
>>
>> Recently Eclipse started to ask me to confirm that I trust the Eclipse
>> certificate, if I want to install something.
>>
>> Example: Using 4.5.1.M20150904-0015 under Ubuntu 15.10 while
>> installing Wikitext support from
>> http://download.eclipse.org/mylyn/snapshots/weekly
>>
>> Is this expected? I used to be that the Eclipse IDE would trust
>> Eclipse signed content automatically
>>
>> Best regards, Lars
>>
>> --
>> Eclipse Platform UI and e4 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-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 UI and e4 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-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] Mac signing service issues -- plan for M4

[Denis Roy]

On 17/12/15 03:23 AM, Mikael Barbero wrote:
The signing issue is due to too much difference between the system 
clock and the time stamping authority (and for some reason, NTP does 
not work the mac signing machine). I manually synched the time on the 
machine and the signing now works properly.


*sigh*  The breakage coincided with system updates and a reboot.

How did you figure it out?  I couldn't get codesign to return an actual 
error (other than, "1").


Oh, and thank you for fixing this.

Denis




Cheers,
Mikael

Le 16 déc. 2015 à 22:03, David M Williams > a écrit :


Given there is currently "no solution in sight" for this week, I 
think the best course of action is to push ahead, and produce M4 as 
planned, with affected projects disabling "Mac signing".


Once we have that build "in hand", a) if the user experience is 
"really bad", we can reconsider (but as far as know, if they are 
doing fresh install, then they have to do that "open" or "ctrl-open" 
trick we have used in the past -- that is, in the past there has been 
milestones without a Mac signature. b) if enough people are around 
next week, to redo contributions with Mac signed, we can do an M4a 
deliverable.


But, in either case, since we are between a rock and a hard place, I 
think best to try and produce one as planned. Otherwise, we might be 
well into January before we could produce one, depending on 
everyone's holiday schedules.


Thanks,





From: Denis Roy >
To: Cross project issues >,

Date: 12/16/2015 01:36 PM
Subject: [cross-project-issues-dev] Mac signing service issues
Sent by: cross-project-issues-dev-boun...@eclipse.org 






Folks,

The Mac signing service is currently broken. We're tracking the issue 
in :

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

Denis



___
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] Eclipse asked if I trust the Eclipse signing certificate, if I want to install something

[Doug Schaefer]

It's all the chain of trust. The root certificate, the one at the bottom,
should be in your JVM's collection of trusted certificates. Each one signs
the one above until you get to the top one which is the one used to sign
the jars. As long as the JVM can follow that chain to one it knows, it'll
pass the verification.

BTW, this has nothing to do with p2. p2 just uses the facilities the JVM
provides.

On Thu, Dec 17, 2015 at 9:37 AM, Lars Vogel  wrote:

> > Did you check the JVM and their trusted certificates? Any changes and/or
> updates there?
>
> Thanks for the answer Markus. I will have a look, so far I wasn't even
> aware that the JVM has its own trusted certificates. I always assumed
> Eclipse has this implemented as part of p2.
>
> Best regards, Lars
>
> On Thu, Dec 17, 2015 at 12:38 PM, Markus Knauer
>  wrote:
>
> > Are the root certificates that are mentioned in the certificate chain
> > trusted?
> >
> > I tried it with my own Mars.1 RCP/RAP package and it worked without
> showing
> > me this dialog.
> >
> > Regards,
> > Markus
> >
> >
> > On 17 December 2015 at 11:50, Lars Vogel  wrote:
> >>
> >> Recently Eclipse started to ask me to confirm that I trust the Eclipse
> >> certificate, if I want to install something.
> >>
> >> Example: Using 4.5.1.M20150904-0015 under Ubuntu 15.10 while
> >> installing Wikitext support from
> >> http://download.eclipse.org/mylyn/snapshots/weekly
> >>
> >> Is this expected? I used to be that the Eclipse IDE would trust
> >> Eclipse signed content automatically
> >>
> >> Best regards, Lars
> >>
> >> --
> >> Eclipse Platform UI and e4 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-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 UI and e4 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-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] Is projects.eclipse.org hoarked?

[Bob Brodt]

Thanks Mathias. It looks like our web wizards have fixed the problem :)

On Wed, Dec 16, 2015 at 7:58 PM, Wayne Beaton  wrote:

> The web team has fixed the problem.
>
> You should be good-to-go.
>
> Wayne
>
> On 16/12/15 05:32 PM, Bob Brodt wrote:
>
> Well, apparently the web team already knows about it and, according to
> Wayne, they're hard at work fixing it ;)
>
> On Wed, Dec 16, 2015 at 3:13 PM, Matthias Sohn 
> wrote:
>
>>
>>
>> On Wed, Dec 16, 2015 at 10:02 PM, Bob Brodt < 
>> bbr...@redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> I'm trying to create a new release record using the Project Management
>>> Infrastructure. After entering the release number and clicking "Create and
>>> Edit", I get a page that looks like this:
>>>
>>
> --
> Wayne Beaton
> @waynebeaton
> The Eclipse Foundation
> [image: EclipseCon NA 2016] 
>
> ___
> 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
>



-- 

Robert ("Bob") Brodt
Senior Software Engineer
JBoss by 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

[cross-project-issues-dev] TM participating in Neon

[Greg Watson]

The TM project will be participating in Neon with an offset of +1. The release 
record is here:

https://projects.eclipse.org/projects/tools.tm/releases/4.1.0

Regards,
Greg
___
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] Improve Startup Performance ofEclipse

[Ed Merks]

Sam,

Doing work on a Job definitely makes like easier for the main thread, so 
it's definitely a good option.  The advantage of IStartup is that it 
happens after the IDE is painted so that approach has zero impact 
because it 100% offloads the work...  But if no one can use it,  because 
it might be disabled, it seems crippled.   In terms of the concern about 
users disabling IStartup, I wonder who actually knows how to do that?  
I.e., is this more a theoretical problem as opposed to a significant 
problem?



On 17/12/2015 6:56 PM, Sam Davis wrote:
On Tue, Dec 15, 2015 at 11:22 PM, Mickael Istria > wrote:



Why not scheduling a job inside the IStartup? So you get the best
user experience with faster startup, and still the possibility for
advanced users who actually tweak that kind of thing to
enable/disable it?


The concern is that users who don't know what they are doing will 
disable things to "improve" performance and end up with a broken IDE.


On Wed, Dec 16, 2015 at 2:00 AM, Ed Merks > wrote:


The disadvantage of scheduling a job in the startup, is that it's
processed during the time when the IDE itself is trying to paint
for the first time, whereas IStartup happens after the IDE is
visible to the user.   So the former has the potential to impact
the perceived startup time while the latter happens after the user
perceives their IDE is up and running.


Hmm, on my machine it takes about 0.06ms to create and schedule a Job. 
So with 1200 plugins installed, if every single one of them started 
eagerly and scheduled a job, the total time spent scheduling jobs 
would be about 72ms, which is not perceptible. Of course these numbers 
are not worth the paper they're printed on, but nevertheless I think 
the time spent loading classes for the bundle's start() method is 
likely to be much greater than the time spent scheduling a job, so I'm 
not sure there is much gain to be had from using IStartup.


Cheers,
Sam


___
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] [mdt-bpmn2.dev] The Neon Opt-in Deadline is Friday

[Bob Brodt]

Hi all,

MDT-BPMN2 will participate in the Neon release as version 1.2.1, release
record is here:

https://projects.eclipse.org/projects/modeling.mdt.bpmn2/releases/1.2.1

This release is the same as for Mars - nothing has changed since the model
is static and is still BPMN v2.0 compliant.

Cheers,
Bob


Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat


On Wed, Dec 16, 2015 at 8:40 PM, Wayne Beaton  wrote:

> The opt-in deadline for Neon is on Friday.
>
> AFAICT, we haven't heard from these projects:
>
>
>- WindowBuilder
>- Business Process Model and Notation (BPMN2)
>- BPEL Designer
>- Target Management
>
>
> If you don't opt-in, you're not in.
>
> I've copied each of these projects' dev lists on this note (note that I
> have superpowers that allow me to post on a project mailing list without
> joining it, so I won't see your response unless you post to
> cross-project-issues-dev). If you're receiving this and your project
> doesn't have at least one representative on the cross-project-issues-dev
> mailing list, please get somebody to join.
>
> I've confirmed the IP dates with the IP team. I've updated the Neon wiki
> page. For reference:
>
> Dec 18/2015 - Opt-in deadline
> Feb 12/2016 - CQ Submission deadline (specify that the CQ is required for
> Neon)
> May 26/2016 - IP Log submission deadline
> June 2/2016 - Review materials due
> June 9/2016 - End of Release Review Period
>
> I've also opened an "Every Detail Matters for Neon" bug [1]. I intend to
> drive this bug a little harder than last year's as we put more emphasis on
> user experience.
>
> Thanks,
>
> Wayne
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=48
> --
> Wayne Beaton on behalf of the Eclipse Management Organization
> @waynebeaton
> The Eclipse Foundation
> [image: EclipseCon NA 2016] 
>
> ___
> mdt-bpmn2.dev mailing list
> mdt-bpmn2@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
>



-- 

Robert ("Bob") Brodt
Senior Software Engineer
JBoss by 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] [mdt-bpmn2.dev] The Neon Opt-in Deadline is Friday

[Bob Brodt]

Hi all,

SOA-BPEL Designer will participate in the Neon release as version 1.0.5,
release record is here:

https://projects.eclipse.org/projects/soa.bpel/releases/1.0.5

This release is the same as for Mars and will be built for the Neon target
platform - nothing else has changed.

Cheers,
Bob


Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat

On Wed, Dec 16, 2015 at 8:40 PM, Wayne Beaton  wrote:

> The opt-in deadline for Neon is on Friday.
>
> AFAICT, we haven't heard from these projects:
>
>
>- WindowBuilder
>- Business Process Model and Notation (BPMN2)
>- BPEL Designer
>- Target Management
>
>
> If you don't opt-in, you're not in.
>
> I've copied each of these projects' dev lists on this note (note that I
> have superpowers that allow me to post on a project mailing list without
> joining it, so I won't see your response unless you post to
> cross-project-issues-dev). If you're receiving this and your project
> doesn't have at least one representative on the cross-project-issues-dev
> mailing list, please get somebody to join.
>
> I've confirmed the IP dates with the IP team. I've updated the Neon wiki
> page. For reference:
>
> Dec 18/2015 - Opt-in deadline
> Feb 12/2016 - CQ Submission deadline (specify that the CQ is required for
> Neon)
> May 26/2016 - IP Log submission deadline
> June 2/2016 - Review materials due
> June 9/2016 - End of Release Review Period
>
> I've also opened an "Every Detail Matters for Neon" bug [1]. I intend to
> drive this bug a little harder than last year's as we put more emphasis on
> user experience.
>
> Thanks,
>
> Wayne
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=48
> --
> Wayne Beaton on behalf of the Eclipse Management Organization
> @waynebeaton
> The Eclipse Foundation
> [image: EclipseCon NA 2016] 
>
> ___
> mdt-bpmn2.dev mailing list
> mdt-bpmn2@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
>



-- 

Robert ("Bob") Brodt
Senior Software Engineer
JBoss by 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

[cross-project-issues-dev] Neon M4 staging repository is final (again)

[David M Williams]

It appears there were no other contributions after picking up these final 
ones. So 'staging' is now final, again, for M4. 
Markus and I will coordinate our "promoting" these tomorrow, on Friday, 
and via IM we have agreed 4 PM at the latest.
We hope earlier, if we can get the EPP packages produced, and the majority 
of them signed off sooner than that. 

Thanks all, 




From:   David M Williams/Raleigh/IBM@IBMUS
To: Cross project issues , 
Date:   12/17/2015 07:04 AM
Subject:Re: [cross-project-issues-dev] Mac signing service issues 
-- updated plan for M4
Sent by:cross-project-issues-dev-boun...@eclipse.org



Given Mikael's  "new news", and other's requests, I have "re-enabled" the 
"VALIDATE" job on Hudson. 

It immediately started with these "changes"  listed:

Oomph (late)
Upgrade Buildship to 1.0.7 

Anyone else? 

I would like to set a deadline of 12 Noon today (Eastern time). I think it 
will be a bit rushed, but believe then we can still make M4 available on 
Friday, but, let's say we make the repo and EPP packages available by 4 PM 
on Friday, instead of 10 AM on Friday. I think that will give time for all 
the re-work, and sanity checks by EPP Package maintainers and at the same 
time "get it over with" before some start their end-of-year holidays. 

Let me know if any of these times are unreasonable or simply do not work 
due to timezone differences. (It is too early in the morning for me to 
compute or look them up myself :) ... not to mention, it depends on 
exactly who is effected and may need to "rebuild".) 

But, unless you hear otherwise, that is our revised plan. 

Thanks, 
 



From:Mikael Barbero 
To:Cross project issues , 
Date:12/17/2015 03:23 AM
Subject:Re: [cross-project-issues-dev] Mac signing service issues 
-- planfor M4
Sent by:cross-project-issues-dev-boun...@eclipse.org



The signing issue is due to too much difference between the system clock 
and the time stamping authority (and for some reason, NTP does not work 
the mac signing machine). I manually synched the time on the machine and 
the signing now works properly.

Cheers,
Mikael

Le 16 déc. 2015 à 22:03, David M Williams  a 
écrit :

Given there is currently "no solution in sight" for this week, I think the 
best course of action is to push ahead, and produce M4 as planned, with 
affected projects disabling "Mac signing". 

Once we have that build "in hand", a) if the user experience is "really 
bad", we can reconsider (but as far as know, if they are doing fresh 
install, then they have to do that "open" or "ctrl-open" trick we have 
used in the past -- that is, in the past there has been milestones without 
a Mac signature. b) if enough people are around next week, to redo 
contributions with Mac signed, we can do an M4a deliverable. 

But, in either case, since we are between a rock and a hard place, I think 
best to try and produce one as planned. Otherwise, we might be well into 
January before we could produce one, depending on everyone's holiday 
schedules. 

Thanks, 





From:Denis Roy 
To:Cross project issues , 
Date:12/16/2015 01:36 PM
Subject:[cross-project-issues-dev] Mac signing service issues
Sent by:cross-project-issues-dev-boun...@eclipse.org



Folks,

The Mac signing service is currently broken. We're tracking the issue in :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438

Denis

___
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
[attachment "signature.asc" deleted by David M Williams/Raleigh/IBM] 
___
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 

Re: [cross-project-issues-dev] Improve Startup Performance ofEclipse

[Sam Davis]

On Tue, Dec 15, 2015 at 11:22 PM, Mickael Istria  wrote:

>
> Why not scheduling a job inside the IStartup? So you get the best user
> experience with faster startup, and still the possibility for advanced
> users who actually tweak that kind of thing to enable/disable it?
>

The concern is that users who don't know what they are doing will disable
things to "improve" performance and end up with a broken IDE.

On Wed, Dec 16, 2015 at 2:00 AM, Ed Merks  wrote:

> The disadvantage of scheduling a job in the startup, is that it's
> processed during the time when the IDE itself is trying to paint for the
> first time, whereas IStartup happens after the IDE is visible to the
> user.   So the former has the potential to impact the perceived startup
> time while the latter happens after the user perceives their IDE is up and
> running.
>

Hmm, on my machine it takes about 0.06ms to create and schedule a Job. So
with 1200 plugins installed, if every single one of them started eagerly
and scheduled a job, the total time spent scheduling jobs would be about
72ms, which is not perceptible. Of course these numbers are not worth the
paper they're printed on, but nevertheless I think the time spent loading
classes for the bundle's start() method is likely to be much greater than
the time spent scheduling a job, so I'm not sure there is much gain to be
had from using IStartup.

Cheers,
Sam
___
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] Is projects.eclipse.org hoarked?

[Christopher Guindon]

Hi All,

Here's a quick update on what happened yesterday. We upgraded the Drupal 
Bootstrap base theme[1] to the latest release for all of our sites. This 
went well for all of our sites except projects.eclipse.org.


The projects.eclipse.org website is using a custom module called fel[2] 
that overrides the default bootstrap HTML of a fieldset. This module is 
responsible for breaking the collapsible fieldset functionality of 
Bootstrap.


Yesterday, we reverted to a previous version of the Bootstrap theme to 
allow our users to use the site and this morning I pushed out a fix that 
removes the conflict with the bootstrap theme and the fel module.


Cheers,


[1] https://www.drupal.org/project/bootstrap
[2] https://www.drupal.org/project/fel

On 2015-12-17 10:38 AM, Bob Brodt wrote:

Thanks Mathias. It looks like our web wizards have fixed the problem :)

On Wed, Dec 16, 2015 at 7:58 PM, Wayne Beaton > wrote:


The web team has fixed the problem.

You should be good-to-go.

Wayne

On 16/12/15 05:32 PM, Bob Brodt wrote:

Well, apparently the web team already knows about it and,
according to Wayne, they're hard at work fixing it ;)

On Wed, Dec 16, 2015 at 3:13 PM, Matthias Sohn
> wrote:



On Wed, Dec 16, 2015 at 10:02 PM, Bob Brodt
> wrote:

Hi all,

I'm trying to create a new release record using the
Project Management Infrastructure. After entering the
release number and clicking "Create and Edit", I get a
page that looks like this:



-- 
Wayne Beaton

@waynebeaton
The Eclipse Foundation
EclipseCon NA 2016 

___
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




--

Robert ("Bob") Brodt
Senior Software Engineer
JBoss by 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


--
Christopher Guindon
Lead Web Developer
Eclipse Foundation
Twitter: @chrisguindon

EclipseCon NA 2016 
___
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] EMF Parsley participating in Neon

[Lorenzo Bettini]

Hi,

The EMF Parsley project will be participating in the Neon release train
with an offset of +3.

The release record can be found here:

https://projects.eclipse.org/projects/modeling.emf-parsley/releases/1.0.0

cheers
Lorenzo

-- 
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

___
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] Mac signing service issues -- updated plan for M4

[David M Williams]

Given Mikael's  "new news", and other's requests, I have "re-enabled" the 
"VALIDATE" job on Hudson. 

It immediately started with these "changes"  listed:

Oomph (late)
Upgrade Buildship to 1.0.7 

Anyone else? 

I would like to set a deadline of 12 Noon today (Eastern time). I think it 
will be a bit rushed, but believe then we can still make M4 available on 
Friday, but, let's say we make the repo and EPP packages available by 4 PM 
on Friday, instead of 10 AM on Friday. I think that will give time for all 
the re-work, and sanity checks by EPP Package maintainers and at the same 
time "get it over with" before some start their end-of-year holidays. 

Let me know if any of these times are unreasonable or simply do not work 
due to timezone differences. (It is too early in the morning for me to 
compute or look them up myself :) ... not to mention, it depends on 
exactly who is effected and may need to "rebuild".) 

But, unless you hear otherwise, that is our revised plan. 

Thanks, 
 



From:   Mikael Barbero 
To: Cross project issues , 
Date:   12/17/2015 03:23 AM
Subject:Re: [cross-project-issues-dev] Mac signing service issues 
-- plan for M4
Sent by:cross-project-issues-dev-boun...@eclipse.org



The signing issue is due to too much difference between the system clock 
and the time stamping authority (and for some reason, NTP does not work 
the mac signing machine). I manually synched the time on the machine and 
the signing now works properly.

Cheers,
Mikael

Le 16 déc. 2015 à 22:03, David M Williams  a 
écrit :

Given there is currently "no solution in sight" for this week, I think the 
best course of action is to push ahead, and produce M4 as planned, with 
affected projects disabling "Mac signing". 

Once we have that build "in hand", a) if the user experience is "really 
bad", we can reconsider (but as far as know, if they are doing fresh 
install, then they have to do that "open" or "ctrl-open" trick we have 
used in the past -- that is, in the past there has been milestones without 
a Mac signature. b) if enough people are around next week, to redo 
contributions with Mac signed, we can do an M4a deliverable. 

But, in either case, since we are between a rock and a hard place, I think 
best to try and produce one as planned. Otherwise, we might be well into 
January before we could produce one, depending on everyone's holiday 
schedules. 

Thanks, 





From:Denis Roy 
To:Cross project issues , 
Date:12/16/2015 01:36 PM
Subject:[cross-project-issues-dev] Mac signing service issues
Sent by:cross-project-issues-dev-boun...@eclipse.org



Folks,

The Mac signing service is currently broken. We're tracking the issue in :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438

Denis

___
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
[attachment "signature.asc" deleted by David M Williams/Raleigh/IBM] 
___
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] Eclipse asked if I trust the Eclipse signing certificate, if I want to install something

[Markus Knauer]

Did you check the JVM and their trusted certificates? Any changes and/or
updates there?
Are the root certificates that are mentioned in the certificate chain
trusted?

I tried it with my own Mars.1 RCP/RAP package and it worked without showing
me this dialog.

Regards,
Markus


On 17 December 2015 at 11:50, Lars Vogel  wrote:

> Recently Eclipse started to ask me to confirm that I trust the Eclipse
> certificate, if I want to install something.
>
> Example: Using 4.5.1.M20150904-0015 under Ubuntu 15.10 while
> installing Wikitext support from
> http://download.eclipse.org/mylyn/snapshots/weekly
>
> Is this expected? I used to be that the Eclipse IDE would trust
> Eclipse signed content automatically
>
> Best regards, Lars
>
> --
> Eclipse Platform UI and e4 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-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] Eclipse asked if I trust the Eclipse signing certificate, if I want to install something

[Lars Vogel]

Recently Eclipse started to ask me to confirm that I trust the Eclipse
certificate, if I want to install something.

Example: Using 4.5.1.M20150904-0015 under Ubuntu 15.10 while
installing Wikitext support from
http://download.eclipse.org/mylyn/snapshots/weekly

Is this expected? I used to be that the Eclipse IDE would trust
Eclipse signed content automatically

Best regards, Lars

-- 
Eclipse Platform UI and e4 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-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