Re: [epp-dev] Luna M3 and Mac OSX Mavericks issues

[Cédric Brun <cedric.brun@xxxxxxx>]

Sorry for the lag, I was abroad.

I'm OK not publishing the modeling package for M3. We will target the users to M4 interim builds if we can have some quite quickly.

I also agree with Markus's proposal to publish what we have with the workaround and focus on fixing the Mac problem for real: many things moved for M3 (new equinox, gtk3...) Which makes me think we need as much testing as possible.


David M Williams <david_williams@xxxxxxxxxx> a écrit :

My view is to make available what you have,
with the "work around". 

And we are not "publishing"
modeling package, I assume? 

If we start now ... we might get a good
M4 :) ... just a reminder we can't wait until the last few days before
deadline before we test build, repos, and updates (and, I am a little guilty
of that myself this time). 

I think M3 is "early enough"
users would expect it to be "rough" ... much different recommendation
if we were at M7 or something. 




From:      
 Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>
To:      
 EPP Developer Mailing
List <epp-dev@xxxxxxxxxxx>, 
Date:      
 11/15/2013 07:10 AM
Subject:    
   [epp-dev] Luna
M3 and Mac OSX Mavericks issues
Sent by:    
   epp-dev-bounces@xxxxxxxxxxx

---

Hi package maintainers,

I'm sure you are aware of bug 421816 [1]. There's currently
an issue if someone wants to start one of the M3 packages from build [2]
with the Gatekeeper enabled. Now I'd like to get some feedback from you
about how we should proceed.

From my point of view there are two alternatives:

(1) Release the M3 build [2] as is and provide a description
of the workaround (disable Gatekeeper, start, enable Gatekeeper again).
This workaround seems to be popular, at least YourKit tells its users about
it. It's just meant as a temporary workaround for M3 and the underlying
issue has to be fixed before/with M4.

(2) Use [3] as a basis, sign all packages, but delay the
release (i.e. no release today, or not before early next week). Note that
this alternative involves some risk and a lot of work (work that has to
be done anyway for M4, it is not wasted).

This morning I tried several other ways, but they don't
look very attractive to me:
- With Gunnar I tried to hand-patch the existing M3 build...
if it was really successfully someone could have convinced me that this
is a temporary way for M3, but I wouldn't call our try successful.
- Enhance the existing build and add signing capabilities...
I'd prefer to move forward instead of investing a lot of time here.

Good, that's the current status. But now: What's your
opinion, or do you have better ideas?

Thanks,
Markus



[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=421816
[2] http://build.eclipse.org/technology/epp/epp_build/luna/download/20131113-1841/
[3] https://hudson.eclipse.org/hudson/user/mknauer/my-views/view/EPP/job/luna.epp-tycho-build/

_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev