- Project tools
-
-
- How do I...
-
| Category |
Featured projects |
| scm |
Subversion,
Subclipse,
TortoiseSVN,
RapidSVN
|
| issuetrack |
Scarab |
| requirements |
xmlbasedsrs |
| design |
ArgoUML |
| techcomm |
SubEtha,
eyebrowse,
midgard,
cowiki |
| construction |
antelope,
scons,
frameworx,
build-interceptor,
propel,
phing
|
| testing |
maxq,
aut
|
| deployment |
current |
| process |
ReadySET |
| libraries |
GEF,
Axion,
Style,
SSTree
|
| Over 500 more tools... |
|
[ Date Prev][ Date Next][ Thread Prev][ Thread Next][ Date Index][ Thread Index]
[Catacomb] v1.0 release
Sung Kim wrote:
I think this is our major feature change. We can release Catacomb 1.0 after this work. :-)
I'd like to request that we postpone the v1.0 release of Catacomb until
the entire DASL specification has been implemented. Specifically, Query
Schema Discovery needs to be implemented, along with a couple minor
search functions such as the 'contains' operator. If there are issues
that come up at the interoperability event we should also fix those
before the v1.0 release.
Releasing v1.0 at this time would only precipitate several minor
releases... In my opinion, v1.0 should at least implement a Class 2 DAV
server (compliant with the latest protocol specification) and the
complete DASL specification as well. Support for multiple DBs is
desireable, but not necessary functionality for v1.0.
My reasoning is due to the fact that Catacomb is one of the reference
implementations for DASL that other developers are looking at. Because
of this, v1.0 should be as feature complete as possible. It doesn't make
sense to release v1.0 if it doesn't implement the full DASL spec.
Elias
|