[Contrib: Evaluation System] 1.3.0-RC4 tagged!

[Nicola Monat-Jacobs]

Our latest (and hopefully final!) RC is now tagged! Check it out from:

https://source.sakaiproject.org/contrib/evaluation/tags/1.3.0-RC4

Beth - can we get this loaded on the UMich test server? 

Thanks everyone for great conversations to help move this along at the conference! Special thanks also to Adam, Rick, Beth, Aaron and Jim for their assistance in various ways. It's much appreciated and I know all the new folks that showed up to hear us chat about EvalSys are grateful we have such great people spending time on this project.

Once it's up on the UMich test server, we'll have to get everyone to test, so get ready for that!

-------------------------------------------------------------

Since we have so many various folks involved, a little JIRA review seems like a good idea just so everyone is on the same page. (This should follow the community practices for core Sakai - if it differs, let me know.)

When you commit a fix for a bug, please include the JIRA id like so:

EVALSYS-1071 Upgrade to poi 3.7

Then the "Subversion Commits" tab in JIRA will pick it up. If for whatever reason you can't do that, please include the revision id of your commit.

Once something is fixed in trunk, the JIRA can be resolved, and the fixVersion should be set to the next release which has not yet been tagged, branched or feature frozen. Since we haven't tagged or feature frozen 1.4, 1.4 is what you'll set it to when you fix it in trunk. (Setting fixVersion=trunk ultimately ends up being very unmeaningful information over time.)

If the fix is something that should be merged into a release that has already been tagged, branched or feature frozen (like and important big fix), then you should set the 'status' for that version to 'merge' - then folks like me can run a report and see what needs to be merged in. Once it has been merged in, the merger will set the status to 'resolved'.

At the end of the summer, we'll feature freeze 1.4. That will entail making a 1.4.x 'branch' folder for that version and then cutting various RC tags for it until we're happy we have a solid 1.4 release. Until we make that 1.4.x branch, you can contribute features and bug fixes to trunk and they will be part of 1.4 when it is branched. The '1.4 status' field does not become relevant until that branch folder is created, because there's nowhere to merge a fix right now. 

Please review for more info:
https://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines

THANKS FOR READING THIS FAR!

- Nicola