Hi Sergei,

here are some thoughts off the top of the head ...

On Fri, May 04, 2007 at 05:51:36PM +0400, Sergei Vyshenski wrote:
> Let me request to schedule a release 1.0 for this June.
That sounds pretty early to me ...

> Here we need a reliably working version with at least basic functionality.
Could you clarify on what the basic functionality would be in your
opinion?

> Current revision of OpenXPKI is unstable, sometime irreproducible. 
Granted, it is a development version. I haven't seen irreproducible
errors in quite a while though (mostly after we fixed the session startup
bug in 795). If you still see some, why not report them using the tracker
or the mailing list (even if you believe that they are irreproducible
it would help other people if they seem them to spot that someone else
was having the same problem)?

> It happens that new heavy errors are introduced at a pace much faster than 
> they could be traced down.
That's probably because a whole lot of new features have been added,
too.

> (Just to mention, a utf8 story during last months: 
> multi-level errors which are very hard to investigate are still there.)
Where is the bug report on that?

> Existing clever tests seem not be run *before* commits.
ACK. Unluckily, this seems to be true. I am working on fixing this by
implementing an automatic testing that is run every night or so to make
sure the tests don't break unnoticed any longer.

> New tests for new code are not covering all functionality.
That is lightly put. A great amount of new code does not have any
tests at all. I've been trying out Devel::Cover for the test generation
and our test coverage is not too good.

> Do you mind if I (or somebody else?) split svn branches: 
> 
> 1) one to be a development branch, 
> 2) other meant to turn into stable release during this May and June?
Might be a good idea. I am still not sure about the timeframe, though.

> Do you mind if we negotiate a policy about commits into stable branch?
> I suggest something like:
> 
> - no new functionality is allowed to be added to the stable branch 
> unless absolutely necessary *and* unless accepted by the mail list.
Sounds reasonable. I am not sure if we have enough features already to
do this right now. Here is my wishlist for a stable release, fresh from
the SF tracker:
- [ 1669932 ] Bulk request support
- [ 1630657 ] Super search for web interface
- [ 1600234 ] Do not use default passwords in default installation
- [ 1630650 ] A nicer system error page
- [ 1597757 ] Replace SQL wildcards with '*' wildcard in workflow search

> Not even if Volkswagen produces a new version of its auto, 
> which could be supported by OpenXPKI.
:-)

> - each functionality which is not basic but works unreliably, 
> and with no clearly seen ways to fix,
> should be removed from the stable branch after negotiating at the mail list.
Anything particular you have in mind?

> - productivity enhancement is allowed after negotiating at the mail list.
OK ...

> - (heavily tested locally) bugfixes are welcome.
OK ...

> - contributions to docs and web zone are welcome.
Definitely :-) I believe having a 1.0 without any more documentation
than at the moment is not really possible, there is still a lot to
be done there.

> - translations of all tags to at least English are welcome.
Another point that is a must for a 1.0 for me, there shouldn't be
any I18N_ identifiers (at least on the English version) on the web
interface any more. This is problematic because we need to identify
which tags actually end up at the web interface (some of them seem
to be 'internal' Exception identifiers that can remain untranslated).

> - adding of new tests at every suitable location is welcome.
Definitely. I am working on redoing the workflow tests so that we
can test the basic workflows again (this should be pretty easy using
OpenXPKI::Client) and web interface tests using Test::WWW::Mechanize
and HTTP::Recorder (this will need a test webserver setup, but otherwise
it is pretty straightforward, too).

> Perhaps you have other plans or more clever ideas about 
> how to pave a road to release?
Good question, I'll guess I'll have to think about that for a while.

Just my 2cts,
Best regards,
    Alex
-- 
Dipl.-Math. Alexander Klink | IT-Security Engineer
        [EMAIL PROTECTED] | working @ urn:oid:1.3.6.1.4.1.11417

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel

Reply via email to