Project

General

Profile

Bug #11455

Redmine issue template.

Added by Roman Lebedev over 2 years ago. Updated 8 months ago.

Status:
New
Priority:
Critical
Assignee:
-
Category:
-
Target version:
Start date:
01/13/2017
Due date:
% Done:

0%

Estimated time:
Affected Version:
git master branch
System:
all
bitness:
64-bit
hardware architecture:
amd64/x86

Description

If it is possible, when tracker = camera support (FIXME: or always?),
the issue description should contain a text about raw.pixls.us
Something like:

Please visit raw.pixls.us and make sure that we have all the samples for your camera under CC0 licese!

History

#1 Updated by Roman Lebedev over 2 years ago

  • Project changed from darktable to website
  • Tracker changed from Bug to Feature

#2 Updated by Tobias Ellinghaus over 2 years ago

I can't see any setting for a default text or any message to be shown.

#3 Updated by Roman Lebedev almost 2 years ago

  • hardware architecture set to amd64/x86
  • bitness set to 64-bit
  • System set to all
  • Affected Version set to git master branch
  • Target version set to 2.4.0
  • Priority changed from Low to Critical
  • Subject changed from Camera support issue template to Redmine issue template.
  • Project changed from website to darktable
  • Tracker changed from Feature to Bug

This needs to happen before rc.

#4 Updated by Rafa G. almost 2 years ago

Roman Lebedev wrote:

This needs to happen before rc.

I think "Issue Templates"[1] plugin could be useful for this case.
It seems to be updated and well documented2

[1] http://www.redmine.org/plugins/redmine_issue_templates
[2] https://www.r-labs.org/projects/issue-template/wiki/About_en

#5 Updated by Roman Lebedev over 1 year ago

  • Target version changed from 2.4.0 to 2.6.0

#6 Updated by Roman Lebedev over 1 year ago

Up.

#7 Updated by Roman Lebedev 12 months ago

If this is not going to be resolved i might be forced to move the shop elsewhere.

#8 Updated by Roman Lebedev 10 months ago

[00:17:44] <LebedevRI> houz, hanatos: while most interested parties are present, i would like to once more highlight https://redmine.darktable.org/issues/11455#note-7 
[00:18:23] <houz> i still don't know how to do that
[00:19:40] <LebedevRI> just saying
[00:29:22] <hanatos> i have no clue about redmine. or issue tracking or development practices in general..
[00:29:28] <hanatos> does github support such features?
[00:30:26] <LebedevRI> https://blog.github.com/2016-02-17-issue-and-pull-request-templates/
[00:32:16] <hanatos> aha! fwiw i'm not opposed to moving issue tracking to another place, such that repo and issues would be in one place.
[00:46:15] <LebedevRI> well, that sounds better than what i have wrote in that comment

#9 Updated by Pascal Obry 9 months ago

Great, I am also in favor of using GitHub issues. That would ease my work too to have all at the same place.

@hanatos, can you activate the issue tracker on our GitHub to start playing with it?

#10 Updated by Roman Lebedev 9 months ago

Pascal Obry wrote:

Great, I am also in favor of using GitHub issues. That would ease my work too to have all at the same place.

@hanatos, can you activate the issue tracker on our GitHub to start playing with it?

It is easy to activate it, but should there be a [migration] plan first?
Also, what about the existing redmine issues?

#11 Updated by Pascal Obry 9 months ago

Well, we can keep the Redmine open and work on the issues there but without allowing creating new issues.

#12 Updated by Roman Lebedev 9 months ago

Pascal Obry wrote:

Well, we can keep the Redmine open and work on the issues there but without allowing creating new issues.

Please do ideally make a decision soon.
Having two issue trackers is even much worse than having one broken issue tracker.

#13 Updated by Roman Lebedev 8 months ago

Roman Lebedev wrote:

Pascal Obry wrote:

Well, we can keep the Redmine open and work on the issues there but without allowing creating new issues.

Please do ideally make a decision soon.
Having two issue trackers is even much worse than having one broken issue tracker.

Were there any further thoughts here? Which one is to stay?
Can the creation of new issues be at least disabled on the other one?

Also available in: Atom PDF

Go to top