[Contrib: Evaluation System] 1.3.x next (and final?) RC

[Rick Moyer]

Nicola,

	EVALSYS-1026 has be committed to trunk and has been set to merge to 1.3.x

	As for the patches I've applied, mostly for Adam, they all have been committed to trunk.  I'll let Adam or the appropriate person decide and set if they are to be merged to 1.3.x

	I'm wondering why code would be merged from 1.3.x into trunk.  I understood that trunk is always the most current version of the code and 1.3.x, etc is simply a point in time version of the code.  Also that all development work should be done against trunk.  Are my assumptions correct?

	I agree with Beth on marking issues as resolved then closed.  So EVALSYS-1026 has been resolved.

Thanks,
Rick

-----Original Message-----
From: evaluation-bounces at collab.sakaiproject.org [mailto:evaluation-bounces at collab.sakaiproject.org] On Behalf Of Nicola Monat-Jacobs
Sent: Thursday, February 17, 2011 8:35 PM
To: evaluation at collab.sakaiproject.org
Subject: [Contrib: Evaluation System] 1.3.x next (and final?) RC

Hi All -

It's been a crazy month (I'm sure for us all), but I didn't want to shirk my duties here (better late than never right?)

Thanks Beth for getting 1.3.x status field added - I think it will be very helpful.

Today when I checked there were two issues with 1.3.x status = merge: EVALSYS-1061 and EVALSYS-1072  
I have merged them in and set their 1.3.x status to 'resolved'.

Once they're merged into trunk (if appropriate) and 1.3.x, what's the preferred procedure? Should I resolve them, or should we have some kind of testing phase before we call them resolved?

I've also gone through all the emails that were sent out in the last two weeks after the conference call and changed any relevant items to 1.3.x status = merge. Can everyone review and just confirm that this looks right? Also, if there is a JIRA that should be in there that's not, let me know that too.

https://jira.sakaiproject.org/secure/IssueNavigator.jspa?jqlQuery=project+%3D+EVALSYS+AND+%221.3.x+status%22+%3D+Merge

If everyone okay's this, I'll start merging these guys in too. I'm going to assume that everything needs to be merged into trunk and 1.3.x unless the issue explicitly says it doesn't.

Also, Rick, I notice there's a lot of issues where you're commented about merging a fix in. Were these fixes merged to evalsys trunk and/or 1.3.x?

I don't know if we'll get a final RC out tomorrow, but I can definitely tag something if people feel we should.


Thanks,
Nicola
_______________________________________________
evaluation mailing list
evaluation at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/evaluation

TO UNSUBSCRIBE: send email to evaluation-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"