Hi Wayne,
Yes, our intention is to graduate with the Kepler release. So the goal is to ship Stardust 1.0 as part of Kepler.
I have added the release information to our project info page accordingly. Would be great if you could add this to the Kepler page.
I understand that this approach will require to fulfill requirements for release, being member of the release train and graduation simultaneously and getting things right all in one round. Are there specific
areas of risk that you would consider especially important to review? Feedback on that would be highly appreciated.
We do also have an second branch compatible with Helios. Originally we had considered a first release based on that branch. However, at the moment we are not planning for a concrete release from this branch as
we wanted to concentrate our effort on Kepler as we think a release based on the current platform version will be far more useful.
Regards
Herbert
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
On Behalf Of Wayne Beaton
Sent: Dienstag, 19. Februar 2013 16:39
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] Where is the "Simultaneous Release Tracker"
I removed the tracker from the portal a couple of weeks ago, in favour of replacement functionality in what we're calling the Project Management Infrastructure (PMI). While I generally agree with the sentiment
expressed by Daniel, I'll admit that I kept it relatively low profile because I wanted to see who would notice. I will be spending a lot of my time updating documentation this week.
For the time-being, the functionality provided by the release tracker doesn't have a general interface; I have some open questions regarding how this should manifest. In my mind, for example, it doesn't make sense to allow any project at any time to declare
that they're part of the release (including past releases as is supported by the old stuff). I am thinking that members of the planning council should be able to add projects to a simultaneous release. For now, however, that functionality is restricted to
me.
Stardust is already part of Kepler and is listed as having a +3 offset.
I've noticed that Stardust has not had a release. I am a little uncomfortable with a project participating in the simultaneous release without having first engaged in an independent release. What is Stardust's intention? Does Stardust intend to graduate with
Kepler (i.e. produce a 1.0 or higher release), or will this be an incubation release?
If you go to the project's info page [1] and log in, there is an option there to show the project's releases. On that page, you can add as many release entries as required. One of those releases should coincide with the Kepler release. Let us know which one
will be part of Kepler, and I'll add to the Kepler page [2].
HTH,
Wayne
[1] http://projects.eclipse.org/projects/soa.stardust
[2] http://projects.eclipse.org/releases/kepler
Hi,
today I went to „My Foundation Portal“ and didn’t find the tracker. Can someone help me?
Thanks, Simone
Simone Seurer • Configuration/Release
Engineer • SunGard • Gobal Business Services and Technology • Solmsstraße 18, 60486 Frankfurt am Main, Germany
•
Tel +49 69 70768 564
• Mobile +49 176 1111 0184 •
simone.seurer@xxxxxxxxxxx
•
www.sungard.com/infinity
Join the online conversation with SunGard’s customers, partners and industry experts and find an event near you at:
www.sungard.com/ten.
CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you receive this e-mail in error, please notify the sender and delete this e-mail from your system.
SunGard Global Trading (Deutschland) GmbH • Registered: Frankfurt am Main, Handelsregister Frankfurt HRB 85990 • Geschäftsführer: Harold Finders,
Christian U. Haas, Henry Morton Miller Jr., Victoria E. Silbey
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
