It is best to agree on the list, before using any of the possible mechanisms. The library could have 1.0.1 version number in its name. Also, the last digit would not be possible to retrieve programmatically via DRMAA API if used internally. I would use a tag or document description for a spec and document relevant changes inside. Hrabri
-----Original Message----- From: drmaa-wg-bounces@ogf.org [mailto:drmaa-wg-bounces@ogf.org] On Behalf Of Daniel Templeton Sent: Monday, November 26, 2007 2:58 PM To: DRMAA Working Group Subject: [DRMAA-WG] Versioning
Given the defined versioning scheme (major.minor), how should I represent that the latest change to the DRMAA Java language binding spec has revved it past its previous 1.0 status, but that it is still 1.0 compliant. What I want to say is that it's 1.0.1, but that's not possible. The closest I can come is 1.1, which sounds like it's no longer based on the 1.0 DRMAA spec. Thoughts?
Daniel -- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg