flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <webdoubl...@hotmail.com>
Subject Re: asdoc - Release build broken (was: Release build broken)
Date Thu, 28 Mar 2013 04:57:35 GMT
Note: If the resolution of some of the sub-issues would have required more 
than one commit, opening a sub-branch would have been a good practice 
because the set of commits done in the sub-branch would has been merged into 
the mother branch first.

-Fred

-----Message d'origine----- 
From: Frédéric THOMAS
Sent: Thursday, March 28, 2013 5:42 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)

You right, I had to do that but didn't do it, feel free to open other
tickets.
There're no needs to open a new branch, the mother one exists already, just
prepend the commit messages with the real issue ids, I'll modify the commit
messages of the others before merging to reflect the new issue ids.

-Fred

-----Message d'origine----- 
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:37 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)

Hi,

> You right, I just filled the jira accordingly.
Thanks that's a lot clearer.

There still a minor workflow issue here in that unless we make each of those
sub tasks real JIRA subtasks how do I know who's working on each one (or if
anyone is). I can't assign the entire bug to myself as I wouldn't want to
indicate that I'm working on all of it and only one person can be assigned
the bug so that could stop other people from working on  it. We could make
each task be a real JIRA sub task but then do each of those need their own
git branches as well?

Thanks,
Justin


Mime
View raw message