Hi All,
It's totally embarrassing but a user's have just reported that I made a fatal typo in a last minute fix. I fear we can't
ship with this typo in place. Is there any chance to get a contribution into Kepler with a fix to this fix?
The bug that was found late and that I fixed two days
Eike, as much as I like to be accommodating, this doesn't sound like a
respin everything candidate. Is there a way to make this available as a
feature patch from your own project repo, so your users could get it
immediately upon 6/26 release?
Does this impact any/many EPP packages? If so,
On 06/13/2013 07:46 PM, Pascal Rapicault wrote:
I'm not involved in the actual process that makes the various builds happen,
however I would like to vote for a rebuild to happen to give him a chance to
get his changes in.
If we can't do changes, then why don't we release now?
Although I may
No matter how this will be decided, I've updated our contribution file with a new, good R-build. It's next to impossible
that we srew the aggregation up with it.
Thanks and sorry again for all the hazzle!
Cheers
/Eike
http://www.esc-net.de
http://thegordian.blogspot.com
+1 for a respin. That'd -hopefully- allow the build to pick up a now
conform (epl-v10.html/signed) mavenarchiver feature for m2e-wtp.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410670
Fred Bricon
2013/6/13 Eike Stepper step...@esc-net.de
Am 13.06.2013 20:01, schrieb Ed Willink:
Hi
CDO
And so started the respin where everything changed…
Fred, this is far from being a blocker change, so even though this is a benign
change, I don’t know if we want to consume it.
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf
I know it's benign, that's why I didn't request a respin in the first
place.
Now it doesn't hurt to ask :-)
2013/6/13 Pascal Rapicault pascal.rapica...@ericsson.com
And so started the respin where everything changed…
** **
Fred, this is far from being a blocker change, so even though
So, now we have two requests.
And, luckily for you all, I am not the (final) decision maker here ... for
me, it has to be a causes the machine to burst into flames sort of
problem to justify a respin :)
But, there is a Planning Council Exception process and I'm quite happy to
listen to the
What Denis said. +1
From: Denis Roy denis@eclipse.orgmailto:denis@eclipse.org
Reply-To: Cross project issues
cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org
Date: Thursday, 13 June, 2013 3:16 PM
To:
From: Denis Roy denis@eclipse.org
On which day does last minute begin, as we are 13 days away from
the release? As a casual observer I'm puzzled by the test early,
test often, fix nothing mantra. Does today's RC somehow become
null and void if a respin is made and serious problems
I'm hesitating to bring it up, but ... in case a respin is done, it
would be good if this build could eliminate the outdated rap.rwt
bundle that was accidentally contributed by Gyrex [1]. This version of
the rap.rwt bundle contains a critical bug [2] that is fixed in RAP's
final RC4 contribution.
Ralf, my current plan is to do the respin using the last aggregation build
as input, except for those cases approved by Planning Council ... so,
would ask for you to do the same. Work the issue through your PMC and
Planning Council rep first (Ian Bull) and if they all agree, to Ian to
submit
On 06/13/2013 03:46 PM, John Arthorne wrote:
From: Denis Roy denis@eclipse.org
On which day does last minute begin, as we are 13 days away from
the release? As a casual observer I'm puzzled by the test early,
test often, fix nothing mantra. Does today's RC somehow become
null and
The Technology PMC is lead by Gunnar. But Chris and I can take the
initiative.
I would not ask for a respin to address the m2e-wtp "problem". IMHO,
the errant feature conforms to the spirit of the rules and so does
not warrant a respin in and of itself.
I
http://download.eclipse.org/releases/staging/
After review from the Planning Council, I have respun the staging
repository, with just the CDO contribution contributing anything new. For
everyone else, I used the previous staging build as input for your
contributions, so would expect identical
Thank you, David, for taking care of the EPP repo build and starting it
manually.
Regarding the RAP issue with the duplicate bundles... Yes, we are lucky! I
kept my mouth shut in the discussion yesterday because I had the theory
that p2 would resolve this 'problem' itself by running the
16 matches
Mail list logo
