You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by Apache Wiki <wi...@apache.org> on 2006/08/09 08:13:44 UTC
[Directory Wiki] Update of "ReleasesHowto" by JohnStroy
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Directory Wiki" for change notification.
The following page has been changed by JohnStroy:
http://wiki.apache.org/directory/ReleasesHowto
The comment on the change is:
Tempted to change to wiki syntax for lists. And did.
------------------------------------------------------------------------------
=== What can we release? ===
- * Ok we want to release some code but what will that code be exactly. We have a few projects each with a deliverable or more. Let's start by trying to guage the health and usability of each project. If I'm wrong anywhere let me know by making corrections to this page.
+ * Ok we want to release some code but what will that code be exactly. We have a few projects each with a deliverable or more. Let's start by trying to guage the health and usability of each project. If I'm wrong anywhere let me know by making corrections to this page.
- ** janus - looks good for a beta and seems like a single jar - in fact it comes as several jars, but I can look into producing a single one (Vincent)
+ * janus - looks good for a beta and seems like a single jar - in fact it comes as several jars, but I can look into producing a single one (Vincent)
- ** eve - ok for first release but is alpha quality and has a single jar
+ * eve - ok for first release but is alpha quality and has a single jar
- ** ldap - oh yeah has been ready for a while and is kind beta grade with a single jar
+ * ldap - oh yeah has been ready for a while and is kind beta grade with a single jar
- ** snickers - ok for first time release but definately alpha crud that needs an overhaul with serveral jars
+ * snickers - ok for first time release but definately alpha crud that needs an overhaul with serveral jars
- ** naming - looks great with a single jar
+ * naming - looks great with a single jar
- ** kerberos - ok for first release but definately alpha grade with one jar
+ * kerberos - ok for first release but definately alpha grade with one jar
- ** rms - heck no (looks like a lost cause right now)
+ * rms - heck no (looks like a lost cause right now)
- * We got a bunch of projects of varying maturity. It makes sense to make them be able to release on their own. There is no need to have them release together unless one has dependencies on the release of another. Also sometimes it might make sense to release all together if 5 out of six are already being released. We want to release anything that works and anything we want exposed to users. I think all projects minux rms are good candidates as mentioned above.
+ * We got a bunch of projects of varying maturity. It makes sense to make them be able to release on their own. There is no need to have them release together unless one has dependencies on the release of another. Also sometimes it might make sense to release all together if 5 out of six are already being released. We want to release anything that works and anything we want exposed to users. I think all projects minux rms are good candidates as mentioned above.
=== What release numbers do we start with? ===
@@ -36, +36 @@
==== Eve Roadmap for 1.0 ====
- 1. Add support for controls and implement a few useful/common ones
+ 1. Add support for controls and implement a few useful/common ones
- a. Persistant Search Control
+ a. Persistant Search Control
- b. Sort Control
+ a. Sort Control
- c. Named References/ManageDsaIT
+ a. Named References/ManageDsaIT
-
- 2. Complete all JNDI operations and Schema support in Eve JNDI provider
+ 1. Complete all JNDI operations and Schema support in Eve JNDI provider
-
- 3. Complete support for most schema checking constructs
+ 1. Complete support for most schema checking constructs
- a. objectClass
+ a. objectClass
- b. attribute syntaxes
+ a. attribute syntaxes
- c. matching rules
+ a. matching rules
- d. dit structure rules
+ a. dit structure rules
- e. dit content rules
+ a. dit content rules
- f. name forms
+ a. name forms
-
- 4. Enable minimal subschemaSubentries and Authoritative Areas for administration
+ 1. Enable minimal subschemaSubentries and Authoritative Areas for administration
-
- 5. Flexible ACI/ACL based authorization system
+ 1. Flexible ACI/ACL based authorization system
-
- 6. Better transaction management and ACIDity instead of using buffer cache
+ 1. Better transaction management and ACIDity instead of using buffer cache
-
- 7. Replication piggybacking on queueing technologies
+ 1. Replication piggybacking on queueing technologies
-
- 8. Triggers and Stored Procedures
+ 1. Triggers and Stored Procedures
-
- 9. Better error handling and easily understood messages
+ 1. Better error handling and easily understood messages
-
- 10. Awesome documentation and tools
+ 1. Awesome documentation and tools
-
- 11. Correct Abandon operation handlingg
+ 1. Correct Abandon operation handling
@@ -74, +64 @@
==== Eve Roadmap for 1.2 ====
- 1. Language Tags
+ 1. Language Tags
-
- 2. In memory backend alternatives
+ 1. In memory backend alternatives
-
- 3. Support collective attributes
+ 1. Support collective attributes
-
- 4. Support dynamic attributes
+ 1. Support dynamic attributes
-
- 5. SASL/GSSAPI/Kerberos support
+ 1. SASL/GSSAPI/Kerberos support
-
- 6. DNS-based service location
+ 1. DNS-based service location
-
- 7. Password Modify
+ 1. Password Modify
-
- 8. Enable ~= using soundex algorithms (might pass on this - no one uses it or is stupid enough to depend on it so its mostly a toy which adds complexity at no benefit IMO)
+ 1. Enable ~= using soundex algorithms (might pass on this - no one uses it or is stupid enough to depend on it so its mostly a toy which adds complexity at no benefit IMO)
=== Ok so what's the first release revision for Eve already? ===
@@ -105, +88 @@
* First off we need documentation that is up to date and the site must also be up to date to reflect the status of the software.
* We need to have what's there working properly. So then I guess we need to define what works:
- ** the JNDI provider is operational although schema access does not exist yet
+ * the JNDI provider is operational although schema access does not exist yet
- ** the protocol supports core operations minus extended ops and abandon
+ * the protocol supports core operations minus extended ops and abandon
- ** size and time limits are not honored
+ * size and time limits are not honored
- ** aliases work
+ * aliases work
- ** schema is not published
+ * schema is not published
- ** subschema subentires do not exist
+ * subschema subentires do not exist
- ** simple bind is supported only
+ * simple bind is supported only
- ** no controls are supported yet
+ * no controls are supported yet
- ** operational attributes in 2252 are supported
+ * operational attributes in 2252 are supported
- ** no schema checking enabled
+ * no schema checking enabled
- ** interceptor framework is in place and it works
+ * interceptor framework is in place and it works
- ** multiple partions work
+ * multiple partions work
- ** schema subsystem for bootstrapping works
+ * schema subsystem for bootstrapping works
* We need to let users know that if you want to store, retrieve and search for entires then Eve will do that at this point. Anything more than the trivial simple stuff may not be there like controls and such. It's a bit limiting. However building on this will be very rapid thanks to the interceptors.
-
-
-
-