Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New issue: mention the dirac version concerned #93

Closed
sposs opened this issue Jun 10, 2011 · 4 comments
Closed

New issue: mention the dirac version concerned #93

sposs opened this issue Jun 10, 2011 · 4 comments

Comments

@sposs
Copy link
Contributor

sposs commented Jun 10, 2011

It would be good practice that the issues reported have in the title the DIRAC version concerned. That would help the devs to prioritize and for users to look up their own version easier. Maybe a tag could be designed for that.

@acasajus
Copy link
Contributor

We could use the milestones feature. I guess it's supposed to
determine the version were it'll be released but..

On 10 June 2011 17:15, sposs
reply@reply.github.com
wrote:

It would be good practice that the issues reported have in the title the DIRAC version concerned. That would help the devs to prioritize and for users to look up their own version easier. Maybe a tag could be designed for that.

Reply to this email directly or view it on GitHub:
#93

@acasajus
Copy link
Contributor

acasajus commented Oct 4, 2011

Can't use labels as we'd get an infinite amount of them and then the rest of the labels would lose functionality. The only solution I see is that the person opening the bug writes what's the version that fails.

@sposs
Copy link
Contributor Author

sposs commented Oct 4, 2011

That was what I wanted to say.

Thanks.

SP

-----Original Message-----
From: Adrià Casajús [mailto:reply@reply.github.com]
Sent: 04 October 2011 12:43
To: Stephane Guillaume Poss
Subject: Re: [DIRAC] New issue: mention the dirac version concerned (#93)

Can't use labels as we'd get an infinite amount of them and then the rest of the labels would lose functionality. The only solution I see is that the person opening the bug writes what's the version that fails.

Reply to this email directly or view it on GitHub:
#93 (comment)

@acasajus
Copy link
Contributor

acasajus commented Oct 4, 2011

Ok. I close the issue

@acasajus acasajus closed this as completed Oct 4, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants