[cas-dev] JIRA issues

[Scott Battaglia]

Awesome! I didn't know those JIRA instances existed. We should add those 
issues to the Yale JIRA instance then for tracking purposes and notify 
the list they exist.  In addition we should probably update the web site 
to reflect the multiple JIRA instances that exist.  I'll try and do the 
web site update tonight.

-Scott

Andrew Petro wrote:
> On tracking issues for the Yale CAS clients and Yale CAS server:
>
> Yale Technology & Planning hosts a JIRA instance for these projects.
>
> Java CAS Client:
>
> http://tp.its.yale.edu/jira/browse/JCC
>
> CAS server:
>
> http://tp.its.yale.edu/jira/browse/CAS
>
> Those issues should be entered there.  I'd strongly suggest that no
> information be *deleted* from the JA-SIG JIRA without first making sure it's
> reflected there, since deleting and thereby forgetting these ideas seems
> like a needless waste.
>
> So we have a couple problems here.  One of them is the low visibility and
> awareness of existing infrastructure in support of the Yale CAS
> distributions.
>
>
>
> But the underlying issue here is a need for more infrastructure, context,
> and iterations around these libraries, and for that bringing them under the
> JA-SIG banner seems like the way to go.
>
> I would like to see the existing Java CAS client library re-released under
> the JA-SIG banner.  Again, here's the idea:
>
> Under the JA-SIG banner, create a CVS space for, JIRA issue tracker for, and
> web presence for, JA-SIG Java CAS client version 2.1.1, which is *exactly*
> the source code of Yale Java CAS client 2.1.1
>
> Roll forward with iteration on addressing feature requests, bugs,
> documentation, etc. consistent with the JA-SIG release strategy for patches
> and minor versions starting from that baseline.
>
> At such a time that the revolutionarily new Java CAS client that you're
> working on, Scott, becomes viable, then we can look at retiring this
> codebase into quiet maintenance.  I don't think we're there yet, and I think
> it has some legs if we can give it the infrastructure it needs.
>
> I'm willing to do some of this work on a volunteer basis and to serve as a
> "release engineer" for the JA-SIG Java CAS Client 2.1.x series, but as you
> know I'm already behind schedule on getting the 2.5.3 uPortal release out.
> Transitioning those uPortal efforts to the capable Rutgers-led release
> engineering regime should free up some time.  Bringing the Java CAS client
> under JA-SIG should make it more possible for contributors to post patches,
> etc., to support progress of this library.
>
> Andrew
>
>   
>> -----Original Message-----
>> From: cas-dev-bounces at tp.its.yale.edu [mailto:cas-dev-
>> bounces at tp.its.yale.edu] On Behalf Of Scott Battaglia
>> Sent: Thursday, May 04, 2006 10:24 AM
>> To: Mailing list for CAS developers
>> Subject: Re: [cas-dev] JIRA issues
>>
>> William G. Thompson, Jr. wrote:
>>     
>>> Scott Battaglia wrote:
>>>
>>>       
>>>> I'm noticing a bunch of JIRA issues for the Yale CAS Java clients and
>>>> Yale CAS 2.0.x which are not covered within in the scope of the CAS
>>>> project in the JA-SIG JIRA.   Any objections to deleting them and
>>>> notifying the cas-users list that the JIRA instance is for issues
>>>> related to JIRA CAS 3.x?
>>>>
>>>>         
>>> seems reasonable only if there is place to capture the client bugs,
>>> feedback, etc.  should we have another JIRA project for clients?
>>>
>>>       
>> however, there are no CAS clients released under the JA-SIG banner.
>> -Scott
>>     
>
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>