[Portfolio] Manage status changes

[Beth Kirschner]

I have no problem reviewing the changes in the branch. We can worry  
about whether or not to back-port to 2.6.x later.

- Beth

On May 4, 2009, at 4:24 PM, Maurer, Christopher Wayne wrote:

> As I was working to merge the changes in for the following jiras:
> SAK-15822 (change status for all users)
> SAK-16261 (group aware)
>
> I noticed that I used some functionality not yet available in  
> trunk.  It will be part of the SAK-15710 merge later on.  So, is it  
> ok if I just merge these changes in to that branch for you guys to  
> look at?  Or would you rather wait till that stuff all makes it to  
> trunk then try to merge?
> It will also mean that this won’t port to 2.6.
>
> Chris
> _______________________________________________
> portfolio mailing list
> portfolio at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/portfolio
>
> TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"