I think it's time to discuss about 0.9.2. First we don't release it tomorrow. Second it is not ready for a release because it is not stable enough. Third do there be any missing features or general problems which prevent us from starting snapshots and RCs for a 0.9.2 release? Fourth should we still maintain RPMS for a small number of distributions? Fifth which items are necessary for a minimal usable documentation?
1. Schedule
-----------
There is no exact schedule. We start the discussion now. So who should know when we finished :)
2. Stability
------------
0.9.2 will include a lot of new features. These features must be tested. Many people will go from 0.9.0 or 0.9.1 to 0.9.2 and think it is a complete new software. It uses a changed install method. There are no sheets and finally you have to login! So it will be no surprise if we need more time for testing than for 0.9.1.
3. Features
-----------
Does anybody need a special feature which requires changes in the core components of OpenCA? Does anybody need an additional feature like a special information if he inspect a request? If you need a special feature then please describe for what do you want to use this feature, so that we can set an appropriate priority.
4. Distros
----------
Distributions are the next big problem. Should OpenCA publish packages? There are many Linux based distributions, BSD styles and commercial systems like AIX and Solaris. OpenCA operates at minimum under Linux, OpenBSD, FreeBSD, NetBSD, Solaris and AIX. All these systems were reported for 0.9.0 or 0.9.1. So I think it is a good idea to remove distribution specific stuff from the CVS. This would also reduce the number of used directories and make targets. We do not plan to remove special flags which are used to get a better control over the installed files - especially the external perl modules.
Brian build packages for Debian - which I don't find until now - but it is possible. I also think that it is a bad idea to manage specs for all the different distros in OpenCA's CVS. We only produce the software. Actually I prefer debian for my servers and so our RPMs are really outdated. I think it is better to have no RPMs than to have outdated RPMS for only a small number of Linux distributions.
5. Documentation
----------------
Which docs do you really need? Which docs can you write by your own? The documentation for 0.9.2 will be much better than for any other former release and the new documentation will be much more reliable because it is in CVS.
Ok, I think this is enough for one mail and it is only the beginning. 0.9.2 is much more a major release than 0.9.1. It is important now to get an overview what's going on. It is really frustrating for a developer to read webpages like "we fixed these bugs in OpenCA and added these functions" and we never received any mail. OpenCA is Open Source so it is absolutely possible to integrate changes or to be part of the project.
So we wait for comments, ideas and questions related to 0.9.2.
Best regards
Michael
P.S. before somebody asks; I try to integrate OpenSC smartcards as HSM but actually I have trouble with their PKCS#11 module. If we ever get OpenSC or MuscleCard working then we will add it to 0.9.2.
--
-------------------------------------------------------------------
Michael Bell Email: [EMAIL PROTECTED]
ZE Computer- und Medienservice Tel.: +49 (0)30-2093 2482
(Computing Centre) Fax: +49 (0)30-2093 2704
Humboldt-University of Berlin
Unter den Linden 6
10099 Berlin Email (private): [EMAIL PROTECTED]
Germany http://www.openca.org
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
