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?
Maybe I should bring this up on the commons list too?
(BananaDB is no way near tested or stable enough to try promoting it
for the incubator.)
karl
14 mar 2009 kl. 10.43 skrev Bernd Fondermann:
Hi Karl,
your original posting didn't make it to the list.
The answer is nevertheless: Yes :-)
Bernd
Karl Wettin wrote:
I took the silence as a yes and just went ahead and created a 0.1
tag after noticing some other labs had a tags directory..
karl
12 mar 2009 kl. 21.14 skrev Karl Wettin:
Does the Labs no releases policy allow me to create local tags in
the SVN?
BananaDB 0.1-SNAPSHOT is now rather stable and I'd like to tag
this as 0.1 in the SVN so I get get started working on planned
features without getting worried about what I might mess up.
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
