[zi-dev] build infos in package and application XML

Hi,

I wonder, if an optional build date element would make sense in the package 
and application xml.

Up to now, we only define the release date

<release>
	<date>DD-MM-YYYY</date>
</release>

Now imagine, someone is wrapping up phpMyAdmin version 2.5.6. to be installed 
with the ZZ/OSS Installer Client. This version has been release 01-03-2004, 
hence we would write in the package or application XML:

<release>
	<version>2.5.6</version>
	<date>01-03-2004</date>
</release>

If the ZIC bundle of phpMyAdmin has not been issued by the phpMyAdmin team, 
but by a third party, it would be interesting to now, when the bundle has 
been created, thus I would suggest an additional <bundled> element:

<release>
	<version>2.5.6</version>
	<date>01-03-2004</date>
	<bundled>21-03-2004</date>
</release>

Of course, we could allow for a <bundle> element in analogy to <release>, 
which could provide additional information and allow an independet tracking 
of bundles:

<release>
	<version>2.5.6</version>
	<date>01-03-2004</date>
	<notes>Fixed: ... Bugs: ...</notes>
</release>
<bundle>
	<version>20040301-2</version>
	<date>01-03-2004</date>
	<notes>
	The package was not correctly bundled, a file was
	not specified in the filelist
	</notes>
</bundle>

This way, an application or package XML would also allow to track changes 
accross different bundle versions within the same <changelog> element as with 
previous releases.

<changelog>
	<release>...</release>
	<bundle>...</bundle>
</changelog>

Is this useful and what's the best approach?

Sandro
-- 
COntent NEtwork SYStem
[http://www.conesys.net]

ZZ/OSS Installer
[http://www.zzoss.com/projects/installer]


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click