On Sat, Mar 14, 2009 at 2:52 PM, Bernd Fondermann <bf_...@brainlounge.de> wrote: > 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.
'private releases' doesn't make any sense. if the audience is going beyond this mailing list, it is a release: <http://www.apache.org/dev/release.html> > You can even host the release at your people.a.o space. No, please don't. > > What must be done is to cleary distinguish it from an Apache release. > Then it should be completely re-branded, ie, instead of 'Apache Foo' it needs to be labeled 'Bar'. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org For additional commands, e-mail: labs-h...@labs.apache.org
