...
Our QA in our own test server has gone very fine. No issues found so far, except a minor i18n issue that we are going to send to JIRA. (Edit: reported as
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-27829 |
|---|
|
)
Of course, if you find any issue or error in this document or in the patches, do not hesitate in documenting it here or just contact me to fix it.
...
Set the next property in your sakai.properties:
| Code Block |
|---|
|
assignment.usePeerAssessment=true |
Create a new table in your database. The script (for MySQL) is included in https://source.sakaiproject.org/svn/reference/trunk/docs/conversion/sakai_10_0_mysql_conversion.sql
A similar script for Oracle can be found there. The SQL needed (for MySQL) is this one.
| Code Block |
|---|
|
-- ------------------------
--
-- SAK-23812 Peer Review feature for Assignments
--
-- ------------------------
CREATE TABLE ASN_PEER_ASSESSMENT_ITEM_T (
SUBMISSION_ID varchar(255) NOT NULL,
ASSESSOR_USER_ID varchar(255) NOT NULL,
ASSIGNMENT_ID varchar(255) NOT NULL,
SCORE int(11) NULL,
REVIEW_COMMENT varchar(6000) NULL,
REMOVED bit(1) NULL,
SUBMITTED bit(1) NULL,
PRIMARY KEY(SUBMISSION_ID,ASSESSOR_USER_ID)
);
create index PEER_ASSESSOR_I on ASN_PEER_ASSESSMENT_ITEM_T (SUBMISSION_ID, ASSESSOR_USER_ID);
create index PEER_ASSESSOR2_I on ASN_PEER_ASSESSMENT_ITEM_T (ASSIGNMENT_ID, ASSESSOR_USER_ID);
-- --------------------
--
-- END SAK-23812 Peer Review feature for Assignments
--
-- -------------------- |
| Warning |
|---|
Very important: If you run Peer Review in a cluster environment, you should be aware of | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-23130 |
|---|
|
and | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-13776 |
|---|
|
. It seems that jobScheduler can fail if it is running in several nodes of a cluster. The solution is enabling jobScheduler in only one of the servers and disabling it in the others. |
...
The JIRAs
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-23812 |
|---|
|
- The main JIRA, with a lot of revisions. There are several conflicts with 2.9, mainly in AssignmentAction, but not difficult to adjust them.
patch_PeerReview_SAK-23812_Completo.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25609 |
|---|
|
- Subtask of SAK-23812. Straightforward backport.
patch_PeerReview_SAK-25609.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25610 |
|---|
|
- Subtask of SAK-23812. Straightforward backport.
patch_PeerReview_SAK-25610.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25611 |
|---|
|
- Subtask of SAK-23812. Straightforward backport.
patch_PeerReview_SAK-25611.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25638 |
|---|
|
- Straightforward backport.
patch_PeerReview_SAK-25638.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25639 |
|---|
|
- Three revisions. Issues backporting this patch because it collides with Group Submissions feature, not included in 2.9. Some diff tweaks were necessary.
patch_PeerReview_SAK-25639_Completo.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25644 |
|---|
|
- A minor issue with a property changed in another JIRA. Quite straightforward backport.
patch_PeerReview_SAK-25644.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25645 |
|---|
|
- Straightforward backport.
patch_PeerReview_SAK-25645.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25660 |
|---|
|
- A minor issue because 2.9 uses deprecated StringUtil instead StringUtils. Quite straightforward backport.
patch_PeerReview_SAK-25660_Completo.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25666 |
|---|
|
- Straightforward backport.
patch_PeerReview_SAK-25666.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25716 |
|---|
|
- Subtask of SAK-23812. It is a straightforward backport and it is included by error (my fault) in SAK-23812 patch, so you can ignore it.
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25719 |
|---|
|
- Straightforward backport.
patch_PeerReview_SAK-25719.patch
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25897 |
|---|
|
- It is addressed in
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-26050 |
|---|
|
- Straightforward backport. This patch is for jobscheduler tool.
...
There is a single JIRA that I have not been able to backport.
| Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-27787 |
|---|
|
- Peer Assessment Student View or Reviews looks ugly
...