Karl Wettin wrote:
Cool.
A related question,
I'm working on another project that I aim to pop in commons-snadbox
before ApacheCon EU. It's a command pattern suite (commons-command?)
with inital focus on command queue. More or less an ExecutorService on
steriods. The persistency layer is currently limited to BerkeleyDB but I
was hoping to add BananaDB support too.
This would mean that the commons-sandbox project would depend on a labs
project. The problem here is that both projects are limited by the no
releases policy so I would have to copy BananaDB to the trunk of the
sandbox project or script it up so it would check out the labs project,
build, and add it to the local repository. These are both rather nasty
solutions according to me.
Any comments on how to handle that in a nice way? Could I perhaps do a
private release as the individual Karl rather than as the committer
Karl, host it on my own server and let the sandbox project depend on that?
Yes, private releases are permitted for any code you find at the ASF.
This includes any project, whether you are involved or not; and any
code, whether released or unreleased.
You can even host the release at your people.a.o space.
What must be done is to cleary distinguish it from an Apache release.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
