U++ forum: Welcome to the forum

Status & Roadmap

Authors & License

Funding Ultimate++

Search on this site

Search in forums

Home » Developing U++ » U++ Developers corner » Issue tracking...

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Return to the default flat view

Create a new topic

Submit Reply

Re: Issue tracking... [message #30970 is a reply to message #30953]

Sun, 30 January 2011 18:20

dolik.rce is currently offline

dolik.rce
Messages: 1789
Registered: August 2008
Location: Czech Republic

Ultimate Contributor

dolik.rce@gmail.com

mirek wrote on Sat, 29 January 2011 20:35

dolik.rce wrote on Fri, 28 January 2011 08:28

Back to the topic of issue tracking Smile

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

Ok, that clears it up for me, thanks Mirek. I was mystified about the Approved state - it just didn't occur to me that it means "approve the solution" (not "approve the issue"). My English is getting worse and worse over the time Smile

Smile

Honza

Report message to a moderator

Send a private message to this user

[Message index]

		Issue tracking... By: mirek on Wed, 12 January 2011 21:05
		Re: Issue tracking... By: dolik.rce on Wed, 12 January 2011 21:14
		Re: Issue tracking... By: mirek on Wed, 12 January 2011 21:20
		Re: Issue tracking... By: mirek on Wed, 12 January 2011 21:27
		Re: Issue tracking... By: mirek on Wed, 12 January 2011 21:35
		Re: Issue tracking... By: koldo on Thu, 13 January 2011 09:10
		Re: Issue tracking... By: mr_ped on Thu, 13 January 2011 09:53
		Re: Issue tracking... By: unodgs on Thu, 13 January 2011 11:57
		Re: Issue tracking... By: mirek on Thu, 13 January 2011 19:17
		Re: Issue tracking... By: tojocky on Fri, 14 January 2011 17:06
		Re: Issue tracking... By: tojocky on Thu, 13 January 2011 15:31
		Re: Issue tracking... By: chickenk on Wed, 19 January 2011 11:27
		Re: Issue tracking... By: mr_ped on Fri, 14 January 2011 20:08
		Re: Issue tracking... By: harmac on Wed, 19 January 2011 22:49
		Re: Issue tracking... By: unknown user on Thu, 20 January 2011 00:59
		Re: Issue tracking... By: kohait00 on Thu, 20 January 2011 09:34
		Re: Issue tracking... By: chickenk on Thu, 20 January 2011 10:41
		Re: Issue tracking... By: mirek on Thu, 20 January 2011 14:19
		Re: Issue tracking... By: kohait00 on Thu, 20 January 2011 15:27
		Re: Issue tracking... By: fudadmin on Thu, 20 January 2011 16:10
		Re: Issue tracking... By: kohait00 on Thu, 20 January 2011 16:23
		Re: Issue tracking... By: unknown user on Thu, 20 January 2011 16:51
		Re: Issue tracking... By: fudadmin on Thu, 20 January 2011 15:54
		Re: Issue tracking... By: dolik.rce on Fri, 28 January 2011 14:28
		Re: Issue tracking... By: Novo on Sat, 29 January 2011 16:30
		Re: Issue tracking... By: mirek on Sat, 29 January 2011 20:35
		Re: Issue tracking... By: dolik.rce on Sun, 30 January 2011 18:20
		Re: Issue tracking... By: dolik.rce on Mon, 31 January 2011 16:25
		Re: Issue tracking... By: mirek on Mon, 31 January 2011 18:52
		Re: Issue tracking... By: dolik.rce on Mon, 31 January 2011 19:46

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

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

PDF

]

Current Time: Tue May 14 18:15:42 CEST 2024

Total time taken to generate the page: 0.02394 seconds