Home » Developing U++ » U++ Developers corner » RM: "Patch ready"
Re: RM: "Patch ready" [message #33992 is a reply to message #33988] |
Fri, 07 October 2011 21:51 |
|
mirek
Messages: 13980 Registered: November 2005
|
Ultimate Member |
|
|
Sender Ghost wrote on Fri, 07 October 2011 05:37 | Hello, Mirek.
I would like to clarify this topic.
Now, if developer create a patch and submit it for the issue, (s)he need to select "Patch ready" status, right?
In what situations, after this, the status of the issue can be selected for "Ready for QA" and later for "Approved"/"Rejected"? And who really must select this after (e.g. issue starter, developer who did quality analysis and/or applied the patch to repository)?
|
Ideal sequence:
Well, there is issue. Person A finds it and posts (directly or inderectly) to RM.
Person B, without direct write priviledges to update uppsrc fixes it. Posts a patch to the very same RM issue as "Patch ready"
Person C (one from "cxl", "trc" or "unodgs") checks the patch, applies it to uppsrc, commits svn, changes to "Ready for QA" and assigns the task back to A to check it solved the problem.
Does it makes sense? My problem was that "Ready for QA" was the status for QA person, preferably the one that has submitted the issue....
Surely, in practice, I will make it "Approved" after applying the patch quite often, but that is another issue (like missing QA ?
Mirek
|
|
|
Goto Forum:
Current Time: Wed May 29 03:12:29 CEST 2024
Total time taken to generate the page: 0.02146 seconds
|