It's not a silly question, the answer is because, I opened a jira ticket [1]
in which there are few sub-issues/tasks :
The release build due to the Git migration is broken:
- TLF external build
- Build Number
- ASDoc for the experimental lib
- Building process (.gitignore, empty.properties)
So, I created a branch where I/we will solve all of them, for each
particular sub-issues/tasks resolution, it will be one commit with a message
prepend with the jira issue id, once all done, I'll clean up the branch and
merge it to the develop branch as a set of commit to fix the release build.
In jira, because I prepended each commit with the jira issue id, I'll find
on the jira issue source tab, the links to all the sources fixed (as soon as
fisheye will be operational, probably in the week).
-Fred
[1] https://issues.apache.org/jira/browse/FLEX-33451
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 4:48 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
You can see the fix in the branch I did
Perhaps a silly question but if you have a fix in a branch why hasn't it
been merged into develop? Especially if it fixes an issue. Other people may
have this issue but they wouldn't know that your branch fixes it.
Thanks,
Justin
