hi oliver
releases of sandbox components by the jakarta-common team are forbidden. (i believe that - with pmc approval - that slide could release a sandbox component for it's own purposes.) so, what's needed is promotion to the jakarta commons.
of course, one of the major is that the component has an active community to support it and that it's ready for (at least a 0.x) release. it's never too early to push for promotion, especially if the component is already mature (in a code sense).
you might like to start another thread asking other people what they think is required for promotion but i'd say that a good place to start would be by adding transaction to the website.
- robert
On 17 May 2004, at 08:23, Oliver Zeigermann wrote:
Although newly created package transaction is active and actually almost feature complete as it has been factored out from the Jakarta Slide Project. What is involved to make a release or is it pre-mature to think about it now?
Oliver
Henri Yandell wrote:
I'm interested in finding out which parts of sandbox are not active and
which would be worth putting time into getting a release done.
Currently on the Commons site we list these as the active components,
which are actually active and where are they release wise?
attributes
bzip2
chain
compress
convert
functor
hivemind - promoted to jakarta
jex
jrcs - left commons (need to confirm, bit unsure on this)
launcher
mapper
messenger
naming - moved to directory project
periodicity
primitives
reflect
resources
sql
threadpool
vfs
Though the navigation lists the following as sandbox projects [and thus we
assume active]. Not quite the same, so a bit of figuring out to do here.
Attributes
Cache
Chain
Clazz
Compress
Convert
Events
Functor
Id
JJar
JRCS
Mapper
Messenger
Resources
Scaffold
SQL
ThreadPool
VFS
Workflow
Hen
---------------------------------------------------------------------
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]
