View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008891 | mantisbt | administration | public | 2008-02-14 23:32 | 2008-04-19 04:10 |
Reporter | hubdog | Assigned To | jreese | ||
Priority | normal | Severity | trivial | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.1.0 | ||||
Fixed in Version | 1.2.0a1 | ||||
Summary | 0008891: change version's released property's default value to unreleased | ||||
Description | by now , the default value of new created version's released property is true which I think the default value should be false | ||||
Tags | No tags attached. | ||||
I completely agree with this proposal. |
|
A agree as well. Our development starts by creating a new version and then targeting issues on that version meaning the version may not be released for some time. This poor default forces the immediate edit of the "new version" to mark it as unreleased. |
|
+1 |
|
I agree too. |
|
Fix has been applied to trunk 1.2.x r5030. Is this something that could be applicable to the 1.1.x branch? |
|
The change is not really a bug fix that is relevant to 1.1.x. I also prefer that such change of behaviour is not done as part of a maintenance release. |
|
Fair enough. Resolved. |
|