Project

General

Profile

Actions

Defect #13189

open

Redmine version in trunk should be based on next major release

Added by Harry Garrood about 11 years ago. Updated almost 11 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

I'm developing a plugin against trunk, which relies on the IssueQuery class. This class only exists in trunk. Therefore the first version which will contain IssueQuery will be 2.3.0, so it makes sense to put this in my init.rb:

requires_redmine :version_or_higher => '2.3.0'

However trunk says the current version is 2.2.3-devel; should it be 2.3.0-devel?


Files

Actions #1

Updated by Jean-Philippe Lang about 11 years ago

OTOH, if we set trunk version to 2.3.0 just after 2.2.0 is released, the IssueQuery model might not be present yet in a 2.3.0 trunk. So I don't know if there's a right solution. Maybe we could change the behaviour of requirements when using a devel version (eg. send a warning instead of aborting).

Actions #2

Updated by Harry Garrood about 11 years ago

Ah, I see. Yeah, sending a warning seems to be a better solution. Shall I put a patch together?

Actions #3

Updated by Jean-Philippe Lang about 11 years ago

Sure, a patch is welcome.

Actions

Also available in: Atom PDF