[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dsdp-tcf-dev] Cutting a TCF Release for Helios
|
Hi
all,
I think that a
formal release of TCF should be cut for Helios in the SVN
Repository.
Reasons
include:
- TCF is being
delivered as part of CDT 7.0, so it *is* being released, no matter what is
done to the Repository.
- Because of being
released, TCF must provide an IP Log and Release Review Slides (I have taken
care of that by including TCF in the TM slides and IP Log, since TM is the
container of TCF).
- It is good for our
communities to have a formal milestone in terms of API changes, such that
people know what has been changed in this year compared to last year
etc.
So - what is
involved in cutting a formal TCF release?
- Right now, we have
in SVN .../releases/0.2.0 which points to SVN version 836. This is our
baseline from last year.
- Increase
the bundle and feature versions to "0.3.0" or "0.2.100" as
appropriate. Keep at "0.2.0" when absolutely nothing was changed; use
"0.2.100" when only minor implementation changes occurred; use "0.3.0" when
API was added or new features were added compared to the "0.2.0"
state.
- Ensure that all the
legal files (abouts etc) are in place as needed - I can take care of
that.
- When happy with
everything, create a "releases/0.3.0" tag to point to your 0.3.0
version.
As mentioned, I can
take care of (3) but I need YOU as the TCF committers / contributors to handle
(2) and (4). Make sure that TCF is in a "stable" state when creating the 0.3.0
tag (well, as far as I know TCF is always stable).
Many thanks for your
help;
Please let me know
if there are any questions.
Thanks,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
direct
+43.662.457915.85 fax +43.662.457915.6
