[DRMAA-WG] Proposal how to handle versioning for group documents/implementations

Rajic, Hrabri hrabri.rajic at intel.com
Tue Jan 15 01:17:16 CST 2008


Background

As a group we had two kinds of documents:
  * those submitted to OGF
  * unofficial at the time that had their own release numbers not fully
following OGF ones

Once the group realized that the unofficial documents could be 
useful for the wider audience, the implementation were already in the
field 
synchronized with those unofficial documents.


Proposal candidate

This proposal advocates we keep the keep official DRMAA documents fully 
synchronized in versioning numbers when the content is synchronized.
The implementations would follow the same versioning as the 
documents they refer to, proclaiming OGF document compliance.

The benefit of the scheme is uniformity across both 
documents and implementations, resulting in greater user confidence,
by avoiding potential doubts due to versioning discrepancy.

It is expected that same binding version releases would not be
necessarily simultaneous, so there could be time lags and possible
different current versions.  When the versions are matched in numbers
the same semantics is the norm, when adjusted for different language
bindings.

The "bug implementation releases" could use a third number (subminor?)
in their versions, meaning link compatibility with the implementations
having the same major and minor versions.


[It goes without saying that there is an adjustment that needs to be
made
to make the above proposal a reality.  A good side is that it is one
time
adjustment, not allowing exceptions also in the future.]

-Hrabri 


More information about the drmaa-wg mailing list