Hi Kevin, Thanks for helping!
The way you did it is perfectly fine. We have it set up so the mailing list alerts us to pull requests. I just merged your request. We’re in the process of working on the 4.14 release. Your change was merged into the develop branch. Hopefully we’ll apply it to the release branch as well and it will make it into the current release. If not, it will make it into the next release. Thanks, Harbs On Jan 1, 2015, at 9:53 PM, kevin.godell <kevin.god...@gmail.com> wrote: > I am trying to have a better understanding of the overall process of how bugs > are fixed, files are updated, and releases are made. This has left me with > several questions that I hope to have answered. > > Does a jira ticket need to be made for a bug to be fixed, or can I submit a > patch without a jira ticket? > > Is git the location of where updates are made? If so, and a patch is > submitted there, what happens if it gets approved? > > Does jenkins receive the committed files from git automatically to create > the releases, or is there some human intervention? > > I ask these questions, because I recently ran into a bug > https://issues.apache.org/jira/browse/FLEX-34630 > I found that if I edited 1 line of code, it would work properly. I then > found the file in git, branched it and then submitted a pull request. Keep > in mind that I am not entirely sure what that means. I then came here to > post these questions, and found that my pull request was posted here, to my > surprise. > > > > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/Flex-Development-Workflow-involving-jira-git-and-jenkins-tp44053.html > Sent from the Apache Flex Development mailing list archive at Nabble.com.
