Skip to main content

Version Information

2 replies [Last post]
Anonymous

We need a consistent mechanism to convey version information for
bug tracking purposes. Currently, the CDC builds support a command
line option "cvm -version" to get the high level product packaging
information. There has not been a command line option for this sort
of information in the feature phone bundles, because the embedded
device did not always include a "command line".

I'd like to gather the high level requirements before we make implementation
decisions about how the information should appear. Here are a few
initial requirements on the issue.

- should be consistent for phoneme feature and advanced products
- should be complete enough information to accurately file bugs
- should be complete to include all major component version
information in the presence of multiple profiles and optional
packages included in a build
- should be extensible to include third party information or OEM
added components, e.g. operator required additional interfaces
- should be visually present in source bundles, similar to other
top level notices or starting instructions
- should be accessible from binary releases, via command line
options or diagnostic displays(similar to about box information)

What additional requirements should we add to the list?

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
davyp
Offline
Joined: 2007-01-03

On a related note, the BINARY_BUNDLE_NAME does not specify anymore which profile is inside the package. It
used to be something like CDC_HI_FP_PP, but now each profile (CDC, Foundation, ...) is packaged as
phoneme_Advanced-*.zip

Davy

cjplummer
Offline
Joined: 2006-10-16

That's a result of changes I just made to cleanup the -version output. I neglected to check how these changes would affect the default binary bundle name. I'll look into it.

Chris Plummer