I can't take the credit regarding AmiSSL - most of the work has been done by Jens Maus, and several others have been involved. It's true that development did stall, but to cut a long story short I stepped in recently to help fix everything as the code was broken and simply didn't work. Now it is working again, the AmiSSL team have regained their motivation, as you can see from GitHub
.
AmiSSL is not dependent on IBrowse and can be released at any time. However, IBrowse is if course dependent on AmiSSL - it would be foolish to release IBrowse 2.5 until the SSL issues were fixed and that means a new AmiSSL.
I didn't realise until yesterday, while reworking the SSL code in IBrowse, that IBrowse 2.4 and AmiSSL 3.6 could already handle TLSv1 connections - IBrowse 2.4 explicitly disables it for a reason I am unsure of. Wish I'd figured that out earlier as I could have published the "fix" as soon as POODLE hit and sites began to shut off SSLv3, but better late than never!