Hi,

I agree, doing the final before ApacheCon would be nice.

It seems we are currently not fixing all that many issues. So I think
we can only include major blockers that really would void a release, I
think the function-handling changes seem to not cause much regressions
so we are not that far away from a release.

Do we have a way of identifying issues in bugzilla which are blocking
the release so we know what we should concentrate on?

Thanks... Dominik.

On Wed, Sep 24, 2014 at 12:50 PM, kiwiwings <[email protected]> wrote:
> If it's because of #54764, I don't mind a final, otherwise I think it would
> be nice to roll out something before the next ApacheCon, i.e. end of
> October.
>
> I'm still tweaking the XML signature stuff, but it would be nice, if someone
> give it a review, so maybe I can bring it into the final:
> https://svn.apache.org/repos/asf/poi/branches/xml_signature/
>
> Things to look at:
> - Configuration stuff (SignatureConfig):
>   what's better, to configure everything in one place or per facet?
> - Dependencies: if one wants to use the dsign classes, they will need to
> include Bouncycastle and Apache Santuario. I've choosen Santuario to be
> compatible with IBM JDKs - but of course the classes (in an older revision)
> would be available in the Oracle JDK. Furthermore updates to xmlsec can be
> easier integrated.
> - Basic signing/validation looks ok, but the edge cases are a bit difficult
> to test, so I'm sure there will bug fixes in upcoming releases
> - Documentation ... left for later ;)
>
>
>
> --
> View this message in context: 
> http://apache-poi.1045710.n5.nabble.com/Another-beta-tp5716696p5716699.html
> Sent from the POI - Dev mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to