Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » RM: "Patch ready"
RM: "Patch ready" [message #33985] Fri, 07 October 2011 08:04 Go to next message
mirek is currently offline  mirek
Messages: 12497
Registered: November 2005
Ultimate Member
I have added a new status to the Redmine intended for patch submission... (Ready for QA should be really reserved for the final QA).

Mirek
Re: RM: "Patch ready" [message #33988 is a reply to message #33985] Fri, 07 October 2011 11:37 Go to previous messageGo to next message
Sender Ghost is currently offline  Sender Ghost
Messages: 299
Registered: November 2008
Experienced Member
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)?

[Updated on: Fri, 07 October 2011 12:22]

Report message to a moderator

Re: RM: "Patch ready" [message #33992 is a reply to message #33988] Fri, 07 October 2011 21:51 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12497
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 ? Smile

Mirek
Re: RM: "Patch ready" [message #33997 is a reply to message #33992] Fri, 07 October 2011 23:29 Go to previous message
Sender Ghost is currently offline  Sender Ghost
Messages: 299
Registered: November 2008
Experienced Member
mirek wrote on Fri, 07 October 2011 21:51


Does it makes sense?


Yes, it makes sense.
Paraphrasing, "Ready for QA" is responsibility of A, if C wants to check quality of applied patch(es) from A point of view. Further, A changes issue status to "Approved" or writes comments about new issue(s). The "Ready for QA" issue status is not mandatory.

Thanks for answering.
Previous Topic: "ToDo"
Next Topic: upp GTK compatibility for Ubuntu broken?
Goto Forum:
  


Current Time: Wed May 27 23:18:32 CEST 2020

Total time taken to generate the page: 0.01385 seconds