|
|
committed 83 files to 'Moodle CVS' on branch 'MOODLE_19_STABLE' - 02/Apr/08 02:09 PM
MDL-14128, remove all uses of error(get_string())
|
|
|
committed 81 files to 'Moodle CVS' - 02/Apr/08 03:17 PM
MDL-14128, remove all error(getstring()) to print_error()
|
|
|
made changes - 02/Apr/08 06:35 PM
| Field |
Original Value |
New Value |
|
Fix Version/s
|
2.0
[ 10122
]
|
|
|
Fix Version/s
|
1.9.2
[ 10241
]
|
|
committed 1 file to 'Moodle CVS' on branch 'MOODLE_19_STABLE' - 09/Apr/08 11:03 AM
MDL-14128, cannot use a full string in the param.
|
|
|
made changes - 15/Apr/08 10:04 AM
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
made changes - 16/Apr/08 07:00 AM
|
QA Assignee
|
|
stronk7
|
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
made changes - 20/Apr/08 06:42 AM
|
Affects Version/s
|
1.9.1
[ 10240
]
|
|
|
Affects Version/s
|
2.0
[ 10122
]
|
|
|
1) We use to put only one release for each branch both in the "affects versions" and "fix versions". So I guess the correct ones for this should be:
affects versions: 1.9, 2.0 (HEAD)
fix versions: 1.9.1, 2.0 (HEAD)
But, generally, for something fixed in a branch (1.9) we don't use to include HEAD (2.0). It's supposed that we always merge changes there, so finally I'd leave this as:
affects versions: 1.9
fix versions: 1.9.1
And will use the 2.0 for things coming exclusively in 2.0.
Just an explanation. Ciao
P.S.: Of course, once you have resolved one bug you should mark it as resolved (fixed) to allow it to be reviewed on weekly reviews.