CAcert Code Development list.

[Michael Tänzer <michael.taenzer AT cacert.org>]

Hi Mikolaj,

On 21.03.2012 23:00, Mikolaj Kucharski wrote:
> Sorry for so big delay in coming back to you. I've seen some progress in
> bug #440 and I also see some changes in git for refs/heads/bug-440
> 
> Is there anything, which I can help with?

We are currently testing whether these and other recent changes to the
certificate issuing and renewal process break anything. If you want to
help us testing please go to our test server at
https://cacert1.it-sls.de ;(for instructions please note the "news"
section there) and report what you tested and what the result was in the
bug report https://bugs.cacert.org/view.php?id=440

In addition to the testing the proposed fix also needs to be reviewed by
a second Software Assessor, this can't be sped up very much, only so far
as that successfully tested fixes are more likely to be reviewed next.


> Do you guys have any ETA for the code to be pushed in to production?

No, sorry I can't give you any hard dates. All I can say is that we are
working on it and the fix looks promising so far but we need to make
sure that certificate issuing does not break completely. So it will at
least take another few weeks but not more than a few months (unless
there is a major disturbance in the force ;-)

-- 
Have a nice day,
Michael Tänzer

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature