Beth,
This seems reasonable to me –
I’d much rather see PTP show up in the Kepler packages, the impact of losing that would be huge.
Jay
From: ptp-dev-bounces@xxxxxxxxxxx [mailto:ptp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Beth Tibbitts
Sent: Friday, June 14, 2013 2:00 PM
To: Parallel Tools Platform general developers
Subject: Re: [ptp-dev] Fw: [epp-dev] EPP Kepler RC4
I haven't heard from anyone, and must leave for the day very shortly, so I am making an executive decision to vote +1 for the parallel
package as is, otherwise it would involve a complicated discussion to lobby for a rebuild, which is unlikely,
or have it omitted from the packages for Kepler.
Based on notes below, I think we can live with it, and are even more motivated to get our 7.0.1 out soon (like June 26?)
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
Beth
Tibbitts---06/14/2013 01:26:55 PM---Here is Markus' response. See attached. So where we stand now is, with PTP 7.0 Kepler, and the para
Here is Markus' response. See attached.
So where we stand now is, with PTP 7.0 Kepler, and the parallel package as is,
1. if you install PTP from (what will be) the kepler p2 repository into CPP package, you fail creating a sync project
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410643
2. if you try to run our parallel debugger from the parallel package - it won't copy it automatically to the remote target.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410811
Plus a few more I've seen go by as well.
Both can be fixed by installing from our 7.0.1 which becomes more important.
Opinions?
I don't have the will to fight a package respin today.
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
----- Forwarded by Beth Tibbitts/Watson/IBM on 06/14/2013 12:58 PM -----
Hi Beth,
I know that this may sound very frustrating but to me it doesn't look like a blocker. A rebuild of a single package is something that we can offer for a milestone build, but release candidates are different. The reason is that we have a single p2 repository
with the metadata of *all* packages. If we rebuild this p2 repository, we must rebuild *all* packages to make sure they correspond to the p2 repository that we release together with the build. For milestone builds I accept small differences between the packages
and the p2 repository on a case by case basis, but we cannot accept this in the release.
This comes down to: If we have to run a rebuild for a single package, we need to convince all other package maintainers to re-test their packages.
(That's the situation right now... I know that it is possible to mirror selectively (and manually) artifacts from different p2 repositories into one, but that doesn't sound right for a release. Too many errors could be introduced then.)
Thanks,
Markus
On Fri, Jun 14, 2013 at 3:09 PM, Beth Tibbitts <tibbitts@xxxxxxxxxx> wrote:
We unfortunately are missing the feature that got entangled in RC2.
I really hate to ask but...can we get a respin of just parallel package?
I have added the feature back in:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410811
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
Markus
Knauer ---06/14/2013 04:22:04 AM---Hi package maintainers, last chance... the RC4 build is ready, it includes the changes from the
Hi package maintainers,
last chance... the RC4 build is ready, it includes the changes from the rebuild yesterday, and all build log files look good, nothing suspicious in there. Please test the following build carefully:
http://build.eclipse.org/technology/epp/epp_build/kepler/download/20130614-0234/
The p2 repositories for this build are
http://build.eclipse.org/technology/epp/epp_build/kepler/download/20130614-0234/repository/ and
http://download.eclipse.org/releases/staging/
Please let me know your votes as soon as possible, and don't forget about the "incubation" statement.
The next steps will be as described in the Kepler Final Daze document [1] in the wiki. In addition to that I will ask for your help next week to review the description of your package, the URLs to the N&N, etc. in the epp.website.xml files, and the webmasters
may need your help with icons, feature matrix etc.
Thanks,
Markus
[1] http://wiki.eclipse.org/Kepler/Final_Daze_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
###
EclipseSource Group
Telefon: +49 721 664733-0 (GMT +2)
Telefax: +49 721 66473329
http://eclipsesource.com
Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
