[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Helios review -- important dates
|
For completeness...
I have advised Krum that a 1.0.1 release in this context is not required
(assuming that no new functionality is added post release). I have
advised that the 1.0 release from May 14 can be included in Helios, and
no additional review with the group is required. I have requested that
he provide the required "paragraph or two" describing MAT's
contributions to Helios for the aggregate document.
I have further advised that in the case of a service release ("1.0.1" is
considered a service release number) it is understood that no new
functionality is included and so a release review is not required.
Wayne
Tsvetkov, Krum wrote:
Hello Anne,
I have some questions related to Memory Analyzer.
First some background: We had recently our graduation / move/ release
1.0 review. We are just doing the post-move changes (legal, webmaster
and emo finished their work), and we still haven’t published for
download a 1.0 release. Our initial thinking was to have a 1.0 added
to M7 and if bugfixes are needed – add a 1.0.1 to the final Helios
release. We somehow didn’t manage to finish everything on time for M7
and I’m planning now like this:
- we add another milestone build to M7 (still not our 1.0 which was
reviewed)
- we spend some further time on testing and publish 1.0 downloadable
about 14 May (one week before RC1)
- add MAT 1.0 to RC1
- take part in the review on 28 May, but don’t make another release
(e.g. 1.0.1)
Finally the questions:
- if we follow this plan, do we need to submit IP log again?
- Do we need another set of slides for the review on 28 May?
- Can we really put our 1.0 in RC1 and stick to it for Helios, or is
it obligatory to have another release made on 28 May
One more remark – I just copied all the data from the simultaneous
release tracker of technology.mat to tools.mat, the technology.mat is
still visible on the list here:
http://eclipse.org/helios/planning/SimultaneousReleaseGrid.php?showallprojects=true
. What should I do to remove it from this list?
Sorry for asking too often, but I still need to learn and build my
experience as project lead at Eclipse.
Regards,
Krum
------------------------------------------------------------------------
*From:* cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] *On Behalf Of
*Anne Jacko
*Sent:* Donnerstag, 6. Mai 2010 07:50
*To:* cross-project-issues-dev@xxxxxxxxxxx
*Cc:* emo-ip-team@xxxxxxxxxxx
*Subject:* [cross-project-issues-dev] Helios review -- important dates
Hello Helios participants,
Thanks for your continuing work on making the upcoming release train a
success! Here's some information about getting ready for the review.
Unlike most reviews, we'll do this one on a conference call. The
conference call numbers are listed in the Portal [1].
Important dates:
IP Logs due: Friday, May 28
Docuware due: Friday, May 28
Helios Review: Friday, June 11
Helios Release: Wednesday, June 23
IP Log: Please use the IP Log tool to submit your IP Log. If it
doesn't work for your project for some reason, please submit your log
manually to emo-ip-team@xxxxxxxxxxx <mailto:emo-ip-team@xxxxxxxxxxx>.
Docuware: In addition to the regular review docuware, please submit a
very simple, brief additional file that summarizes what you are
bringing to the release -- just one or two paragraphs, or a few bullet
points is all we're looking for here. We'll combine the short files to
create a longer one that applies to the entire release.
Please note that simple text files are fine for reviews -- there is no
requirement to create a presentation-style document. As long as the
required information is there, you can use whatever format you prefer.
A list of required docuware contents is on the Eclipse wiki. [2]
We encourage you to submit your IP Log and docuware whenever you're
ready -- we are happy to accept them well ahead of time. Please let us
know if you have any questions. Thanks again for all your efforts.
Anne Jacko
emo@xxxxxxxxxxx <mailto:emo@xxxxxxxxxxx>
[1] https://dev.eclipse.org/portal/myfoundation/portal/portal.php
[2]
http://wiki.eclipse.org/Development_Resources/HOWTO/Review_Information_for_Project_Leads#Docuware_Contents
------------------------------------------------------------------------
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org
