FYI
Thank you Ed for the fast answer.
-------- Original-Nachricht --------
Lukas,
Comments below.
On 16/01/2012 3:12 PM, Lukas Ladenberger wrote:
Hello Ed,
I have some questions regarding the first release of the RMF
project:
- Do we have to write a Release Review for incubation releases
(see http://www.eclipse.org/projects/dev_process/development_process_2011.php#6_3_3_Release_Review)
?
Yes, I think so.
- We disscussed today about labeling conventions for releases. We
determined the following conventions:
- Releases label: Myy.mm (i.e. M12.01).
Releases are generally labeled with the version number of the
release, e.g., 0.7.0. Look at these as a good example of the
platform's convention, which most projects try to follow:
http://download.eclipse.org/eclipse/downloads/
-
Release candidate label: Myy.mmRCx (i.e. M12.01RC1)
Please note: Our release label is simultaneously also our
milestone label. As a consequence our first official release label
would be: M12.01 and the label for the RCP zip product file would
be: pror-M12.01-incubation-macosx.cocoa.x86_64.zip.
I don't think folks will expect to see numbers like that.
As you can see we have no "top level" version number like 3.7 in
the eclipse project. Our "top level" version number would be
simultaneously our milestone label. Is this ok?
I think the version number of your bundles is very important to your
clients. It's a statement about the API. Information about the
date of the build should generally appear in the finally qualifier
that's also part of the version in the bundles and features.
Eventually you're likely to have maintenance streams, that are going
on at the same time as you work on new releases, and then the dates
will be very confusing.
Thank you.
Best regards,
Lukas
|
