Comment 13 for bug 1319545

1) I don't think we can get this into production without memcache for RelStorage. Do you suggest that I make a ticket for ChrisR next week to research what versions of libmemcached/pylibmc we can get running? Or do we need to go into RelStorage and straighten it out?

2) Want me to make a ticket for ChrisR to address the postoffice.queue setting?

3) I think we'll enter a stage where we don't do a flurry of small fixes on master. I can ask ChrisR to get the current backlog of commits onto the branch.

--Paul

On Jul 4, 2014, at 7:05 PM, Chris McDonough <email address hidden> wrote:

> Note that we'll need to backport commits that go into master into
> karlserveless. I've tried to cherry-pick some already, and I believe
> the ones that are outstanding start at
> https://github.com/karlproject/karl/commit/25e66a85834019740cfa4590b6adec1b7351157b
>
> --
> You received this bug notification because you are subscribed to KARL3.
> https://bugs.launchpad.net/bugs/1319545
>
> Title:
> Investigate removing karlserve
>
> Status in KARL3:
> In Progress
>
> Bug description:
> Absent the never-realized "plankton KARL" business model, the
> complexity / obfuscation of karlserve is outweighing its utility. We
> need to figure out how much work is involved to rip it out.
>
> As a deliverable, create a branch of the 'dev-buildout' and remove all
> traces of 'karlserve' from it. Document what features will need to be
> re-worked (e.g., plugin scripts, etc.)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/1319545/+subscriptions