Re: Delivery Status Notification (Failure)

[Emily Jiang <em...@googlemail.com>]

Thanks Felix. Agree. With the Aries versioning policy, it reduces the chance
to bump
versions too much.

One question on the Aries version policy:
In the versioning policy,
http://aries.apache.org/development/versionpolicy.html
, it states "*The version should relate to the most recent release of the
package and not to the version found in trunk.*"  It will be good to have
the release version as an comment in the package.info (or an automatically
generated package version map per release) so that the developers can
immediately decide whether the package version needs to be updated. At the
moment, developers have to look at the change histories and this process
requires the knowledge of the last release date, which does not show in the
change history.

Thoughts?


-- 
Thanks
Emily
=================
Emily Jiang
ejiang@apache.org

Re: Delivery Status Notification (Failure)

[Holly Cummins <cu...@uk.ibm.com>]

+1

I think that's a great idea, and automating it as part of the release 
process should (I hope!) be a lot less work than a full automated 
bytecode-based version-calculation solution. 

--
Holly Cummins
IBM Hursley, UK
cumminsh@uk.ibm.com 



Emily Jiang <em...@googlemail.com> 
04/08/2011 09:45 AM
Please respond to
dev@aries.apache.org


To
dev@aries.apache.org
cc

Subject
Re: Delivery Status Notification (Failure)






Thanks Felix. Agree. With the Aries versioning policy, it reduces the 
chance
to bump
versions too much.

One question on the Aries version policy:
In the versioning policy,
http://aries.apache.org/development/versionpolicy.html
, it states "*The version should relate to the most recent release of the
package and not to the version found in trunk.*"  It will be good to have
the release version as an comment in the package.info (or an automatically
generated package version map per release) so that the developers can
immediately decide whether the package version needs to be updated. At the
moment, developers have to look at the change histories and this process
requires the knowledge of the last release date, which does not show in 
the
change history.

Thoughts?


-- 
Thanks
Emily
=================
Emily Jiang
ejiang@apache.org







Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU