As far as I can see Git has no check in revision numbers. Currently the
build release process uses SVN version number I think the number is
appended to the RSLs and may be used elsewhere.
Anyone have any ideas on how to resolve this?
Good question, really, at the moment I don't know, I'm going to dig into.
Also how do we identify which GIT check in fixed a JIRA bug? Used to be
that we just add the SVN revision checkin but now a push can result in
several checkins.
I would say indicating the JIRA Ticket id in the commit message, it should
link commit(s) with this JIRA ticket but this feature didn't work with our
SVN, I don't know if we'll be luckier with GIT.
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Monday, March 18, 2013 3:28 AM
To: dev@flex.apache.org
Subject: Git and revision numbers
Hi,
As far as I can see Git has no check in revision numbers. Currently the
build release process uses SVN version number I think the number is appended
to the RSLs and may be used elsewhere.
Anyone have any ideas on how to resolve this?
Also how do we identify which GIT check in fixed a JIRA bug? Used to be
that we just add the SVN revision checkin but now a push can result in
several checkins.
The commit hashes are rather ugly, for instance:
fc57407c78d25a64afce4c12ac759139720f4347 Added pt_PT postcode validator
strings
8645f87c26e55f55807e74befaa659b39c9ef93c Added pt_BR postcode validator
strings
2d41d857e14a9bce839285c8bb73da801b2c0877 Added ja_JP postcode validator
strings
8b9c4a6de050f821a6a3894dbda4f7091be2487c Added de_DE postcode validator
strings
Thanks,
Justin
