Let's stop for a second and identify what problems we are trying to solve. I think there are actually several. I can think of:
1) Looking at JIRA ticket, what changes to Git were related 2) Looking at GIT log to see what JIRA issues got fixed (in order to update release notes or when someone asks if a release contains a fix) 3) Determining if a release contains a particular commit/push 4) Monotonically increasing build numbers for version checking It looks like folks solve #4 by counting commits to master. I guess that's ok, but doesn't really seem that helpful. Can we solve #3 and #4 by substituting YYYYMMDD as the build number? I think it solves #2 as well: you can see if the log shows the JIRA issue before the date decoded from the build number. For #1, knowing the hash or partial hash still doesn't give you a sense for when it happened. I suppose we could use dates here as well to at least bracket what changes and assuming the log mentions the JIRA issue. I saw suggestions that you name branches with the JIRA issue. I assume that is because the branch name shows up automatically in the log when pushed? Otherwise it is just a convention and folks will make mistakes. Could we put a URL to the log message or even commit email in the JIRA issue? On 3/18/13 2:49 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: > Hi Jose, > > I thought about the short sha1 too and it could work, I was thinking about a > lightweight tag too (more readable), not sure though what is the best, I > have to dig into more deeply. > > Thanks, > -Fred > > -----Message d'origine----- > From: Jose Barragan > Sent: Monday, March 18, 2013 10:37 AM > To: dev@flex.apache.org > Subject: Re: Git and revision numbers > > In my work, I use the build number of the Hudson, or occasionally the short > version of the commit SHA that I am building. > Anyway, I leave as you get the short version of the SHA, in GIT > git log -1 --pretty=format:%h > -- > Jose Barragan > Chief Software Architect > Codeoscopic Madrid > C/. Infanta Mercedes, 92. > Planta 5. 505. > 28020 Madrid. > Tel.: +34 912 94 80 80 > > On Mar 18, 2013, at 10:17 AM, Frédéric THOMAS <webdoubl...@hotmail.com> > wrote: > >> JIRA use the JIRA Fisheye plugin to link the sources with, aparently, it's >> not setup for our project, I retreived the infra ticket [1], we can then >> directly deal with altassian to setup our project with fisheye. >> >> From [2] : >> >> Support FAQ >> Can we use Fisheye to browse and search our repository? >> Yes. See http://fisheye6.atlassian.com/ for some working examples. (Our >> Jira Fisheye currently disabled, looking into it) >> >> The people at Atlassian kindly provide FishEye instances of ASF projects, >> upon request. >> >> First, check with your project's PMC, and then ask Atlassian to setup a >> FishEye instance for your project. (No need to keep infra the loop.) >> Create a support request at Atlassian Support in the FishEye project. >> Please use the "Public Hosting" component for your request. >> If there is no response after a reasonable amount of time, infra has >> access to set up projects on Fisheye, but consider this a last resort >> option, Atlassian should be first point of contact. >> Atlassian now run a local synced copy of the ASF repository, hence >> requests can now be made direct without infra needing to be involved. >> >> So, I decided to open an issue at Altassian fisheye [3] >> >> -Fred >> >> [1] https://issues.apache.org/jira/browse/INFRA-5635 >> [2] https://cwiki.apache.org/INFRA/infra-faq.html >> [3] https://support.atlassian.com/browse/JST-59433 >> >> -----Message d'origine----- From: Frédéric THOMAS >> Sent: Monday, March 18, 2013 9:29 AM >> To: dev@flex.apache.org >> Subject: Re: Git and revision numbers >> >> Who is JIRA admin btw ? it seem the fisheye plugin is there but >> misconfigured. >> >> -Fred >> >> -----Message d'origine----- From: Frédéric THOMAS >> Sent: Monday, March 18, 2013 9:19 AM >> To: dev@flex.apache.org >> Subject: Re: Git and revision numbers >> >>> That's a feature we have but maybe broken (we should deal with infra >>> IMO). >> >> -Fred >> >> -----Message d'origine----- From: Justin Mclean >> Sent: Monday, March 18, 2013 8:58 AM >> To: dev@flex.apache.org >> Subject: Re: Git and revision numbers >> >> Hi, >> >>> You can check writing the JIRA ticket id in the commit message(s), push >>> it/them , then go to JIRA, in the source tab, you should see all the >>> modified files (if this feature is not broken again). >> >> As far as I know this is not a feature we have - so what can we put in >> JIRA >> to show exactly what changes that have occurred. >> >> Justin >> > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
