COmanage Developers List

[Scott Koranda <>]

> > Instead, please assemble a list of JIRA issues that you think should be
> > blockers for 0.9.4 and then 1.0.0. My current thought is to finish up
> > CO-310 and a few other small/critical/low hanging issues and then tag
> > 0.9.4 probably mid-to-late next week. If there's anything you want
> > included before I tag, be sure to include it in your list, or flag it as
> > a Blocker in JIRA.
> > 
> > For 1.0.0, I'd like to keep the scope fairly small. My primary task will
> > be "installation simplification", as well as any fixes that shake out of
> > 0.9.4 or are sponsored by a client. I'm thinking we could tag 1.0.0 as
> > early as mid July.
> > 
> > Anything you don't enumerate in a list for 0.9.4 or 1.0.0 will probably
> > get swept into the FUTURE bucket.
> > 
> 
> Hi,
> 
> I looked at all the tickets assigned to me. The following
> tickets I have made blockers for 0.9.4 or 1.0.0:
> 
> - CO-1081 "REST API filter returned CoOrgIdentityLinks by CO
>   ID" I have made a blocker for 1.0.0 since we are seeing this
>   functionality used/requested by GEANT and NIH due to the
>   need to query with an ePPN and find a corresponding CoPerson
>   record for a particular CO
> 
> - CO-1061 "COOrgIdentityLinkResponse incorrect" I have made a
>   blocker for 0.9.4 since the fix just needs to be restructed
>   per Benn's request and then pushed. It is already in place
>   for GEANT in a slighly different format.

CO-1061 has been resolved.

> 
> - CO-1045 "Error adding self to open group" I have made a
>   blocker for 0.9.4 since I think the fix is easy.

CO-1045 is fixed but since Mike Manske reported it I have
asked him to verify before resolving.

> - CO-739 "admin group for CO should not be deleted" I made a
>   blocker for 0.9.4 since I think that is fixed but I need to
>   verify it.

CO-739 is fixed.

> 
> - CO-187 "Changing the name of a COU does not change the name
>   of the admin group associated with it" I made a blocker for
>   1.0.0 since I think that it is fixed but I need to verify
>   it.
> 
> - CO-105 "Verify authz failure behavior" I made a blocker for
>   1.0.0 since I think that it is fixed but I need to verify
>   it.
> 
> - CO-84 "Error on creating new CO admin" I made a blocker for
>   1.0.0 since I think that it is fixed but I need to verify
>   it.
> 
> The rest of the tickets have been set to "Future".
> 
> I will be looking into the above tickets that are blockers in
> the coming days.
> 

So I believe I have fixed all 0.9.4 blockers assigned to me. I
will now be moving onto 1.0.0 blockers. Please let me know if
you find anything amiss.

Thanks,

Scott