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 » Issue tracking...
Re: Issue tracking... [message #30953 is a reply to message #30928] Sat, 29 January 2011 20:35 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14105
Registered: November 2005
Ultimate Member
dolik.rce wrote on Fri, 28 January 2011 08:28

Back to the topic of issue tracking Smile

I am quite new to this, so I would like to make sure I get some things right. So my idea about typical flow of things is this:



New -> Rejected (closed)
    -> In progress (or just can stay New)
          -> Ready for QA
               (usually switched to reporter)
then reporter either Approved (closed) or returns it to New or In progress.


Quote:


Like who can approve an issue (can I approve issue I reported?) or who to ask for QA (Mirek in case of new features, original creator of changed code in other cases?).



IME it is best when one that reported the issue approves it. Of course, not always possible.

E.g. in #19, the task to do is me to check the code and apply it to uppsrc. When I am done, I will switch it back to you for final check and approve.

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: SSE2(/AVX) and alignment issues
Next Topic: Q: howto incorporate a native console window in GUI
Goto Forum:
  


Current Time: Fri Nov 01 02:05:45 CET 2024

Total time taken to generate the page: 0.01790 seconds