All
As several libraries are approaching Beta (feature complete), I wanted
to get some thoughts out to the group on versioning and naming of
deliverables. Can you provide feedback on the following? I'll assume
that no feedback means this is an appropriate starting place.
We will have two kinds of release: milestone releases and daily drops.
Milestone releases will appear on sourceforge and llrp.org. Maintainers
of each language will be responsible for building the milestone releases
and release notes. The llrpadmin will set the release schedule and tag
the CVS tree with the appropriate release numbers in advance of the
release date to give maintainers tine to build and test releases. Daily
drops will be automated and appear on sourceforge; they are intended for
developer and test use only.
I think having a common version number across all languages is
beneficial for a few reasons:
Reduced version complications. (e.g. today we released C version 1.6 and
Java version 1.4 ????)
The common files can share the same version. If they don't we're likely
to get pretty confused. (e.g. C version 1.2 is built on common
llrpdef.xml version 1.6, but Java Version 1.2 is built on common
llrpdef.xml 1.2).
It's a good way to qualify feature sets independent of language. For
example, 1.0 will contain a feature set across all languages (of course
exceptions will be allowed).
Daily drops will contain a CVS tarball will be made of the whole archive
and placed on sourceforge in the download area and will only be
versioned with the date.
LTK_Nightly_date.zip
LTK_Nightly_date.tgz
A source package will be released at each LTK target milestone that will
contain:
All documentation for all languages
General documentation on LTK
Common definitions and any vendor extension definitions that
have been submitted and tested
All source (no auto generated components) and makefiles for
all languages
The pakage will be release under two compression formats
with the following naming convention where Maj and Min are the Major and
Minor release numbers respectively.
LTK_Source_Maj_Min.tgz
LTK_Source_Maj_Min.zip
A binary package will be released for each language at each LTK target
milestone that meets the milestone feature list including:
The LLRP.xsd.
API documentation for the language
Header files
Compiled library (windows)
Example source
The packages will be released under two compression formats
with the following naming convention
LTK_<lang>_Maj_Min.zip
LTK_<lang>_Maj_Min.tgz (only for non-windows releases)
A Common package will released at each LTK target milestone including:
The LLRP xsd.
General documentation
All vendor definitions submitted to the site.
Core llrpdef.xml and llrpdef.xsd files
The packages will be released under two compression formats
with the following naming convention
LTK_Common_Maj_Min.zip
LTK_Common_Maj_Min.tgz
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
