| RE: [cross-project-issues-dev] Helios review -- important dates |
|
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 Hello Helios participants, 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]
|