Le 22/06/2011 11:15, Patrick Heinzelmann a écrit :
The name of the file and versionLabel have the postfix and so that
somebody with technical background knows that it is no release
version.
The release version of an app, which will be shipped to the customer
will have no postfixes (like: -RELEASE) of build. A normal user
doesn't know what -SNAPSHOT means.
Yes. But a developper or a tester that want to install an updated
SNAPSHOT is forced to uninstall and reinstall because the versionNumber
has not changed between the two build. With the timestamping idea of
velo (for 2.0 desciptors) it was working well.
"adopt a X.Y numbering scheme"
It is the question wheter you make your bug tracking based on build
version or product version and if every build version is a product
version and if you want release every product version or also can skip
a version. Think about Flash Player versioning.
In the most of my projects, the bug tracking and testing were made
based on product version, which itself was the product of sprint
because otherwise you would go mad because CI was running all the time
trigger by subversion checkins.
Yeah I think I got your point and I tought one more time about CI and
update descriptor coupling and the crazyness it'll drive...
Patrick
On 22 Jun., 08:44, Simon Morvan<[email protected]> wrote:
Le 22/06/2011 02:40, Patrick Heinzelmann a écrit :> See decriptor file info:
A string value of the format<0-999>.<0-999>.<0-999> that represents
application version which can be used to check for application
upgrade.
Values can also be 1-part or 2-part. It is not necessary to have a 3-
part value.
Yeah I'm aware of that. Meaning that velo version numbering scheme for
SNAPSHOT version doesn't work with 2.6 namespace.
I think I'll dive into flexmojos code to find out which workaround I can
setup.
BTW, this is (again) a pity : we're limited to X.Y.Z for version
numbering so if its already the company versionning scheme, you got no
way of numbering (correctly) your snapshots/ci versions.
What I want achieve is to have my ci server produce a .air and an update
descriptor to automate the deployment of updates on testing users
machines. I think I'll be forced to adopt a X.Y numbering scheme for our
public releases to have one digit left for snapshots...
Too bad.
--
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos
http://flexmojos.sonatype.org/
