Grouper Developers Forum

[Chris Hyzer <>]

I think the set of changes is significant, and I just assumed they would be 
in 2.0 so its hard to remember what is a bolt on (e.g. the UI screens), and 
what I put in the core of Grouper (e.g. how attributes are used to store 
invites, etc).  I could do more research in svn diffs to have a real answer 
if you are interested in that path.  When did you want to release 2.0?  What 
issues in Jira/Roadmap must be in 2.0 vs in 2.1 six months from now?

Thanks,
Chris

-----Original Message-----
From: Tom Barton 
[mailto:]
 
Sent: Monday, January 03, 2011 2:55 PM
To: Chris Hyzer
Cc: 

Subject: Re: [grouper-dev] 2.0 release

Judging by the issues in jira, there's still much work remaining to be
completed for 2.0. And I'm not sure that all 2.0 roadmap items have jira
counterparts as yet.

One approach to your situation is to refactor 2.0 roadmap items and jira
issues into 2.0 and 2.1 (or did you mean 2.0.1?). Another is to package
up your external user management capabilities as an optional patch to
1.6.3, to be superseded when 2.0 is released. Is the set of dependent
changes too large for that approach?

Tom

On 1/3/2011 1:42 PM, Chris Hyzer wrote:
> Hey,
> 
>  
> 
> I'm usually the one dragging feet... but in this case Penn wants to use
> external user management in Feb, so any chance we can stop work on 2.0
> and test and release 2.0 at end of Jan?  J  The stuff not done yet could
> be pushed to 2.1...  is there anything that you need in 2.0 that you
> aren't sure is coded yet?
> 
>  
> 
> Thanks,
> 
> Chris
>