I agree that, once it's apparent no one's willing to own maintenance of
this BerkeleyDbTicketRegistry module and mostly no one's using it, it's
appropriate to first @deprecate it and then drop it.
I agree that asking on cas-user@ is also important prior to removing it.
Folks discussed this at the Columbia developer meetup and identified
this module as a candidate for deprecation and then removal. Nobody
there seemed to be using it or interested in maintaining it either.
Andrew
On 9/15/2011 3:52 PM, Marvin Addison wrote:
Can we deprecate it in 3.4.11? And remove it in 3.5 or 4.0 (whatever we name
it)?
+1
That's more polite than simply dropping it.
Obviously retract that if a volunteer steps up to own?
I'd like to see both reasonably broad interest _and_ a maintainer to
keep it. This thread is to gauge interest, so CAS+BDB users please
raise your hand.
M
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
