Hi Siegfried,

Can you please clarify if this to release 1.0.6-RC1 or 1.0.6 final? From the subject I would infer the latter, but the links below suggest the former. If it is 1.0.6 final it would seem that the site and the artifacts are going to be regenerated, so arguable we would be checking the wrong things here.

Does your new Fulcrum M2 Migration wiki page cover deployment to the staging site (in this case your personal apache webspace)? That would be helpful.

Great to see some progress on this. I am certainly not trying to block things, just to understand the new process that is likely to be used extensively in the future.

Scott

Siegfried Goeschl wrote:
Hi folks,

I would like to release fulcrum-yaafi-crypto-1.0.6 as first full-blown
M2 release

+) fulcrum-yaafi-crypto was refactored from fulcrum-yaafi to separate
encryption/decryption from the Avalon container
+) it contains the transparent configuration file decryption support
+) this separation was driven by concerns regarding ECCN export code
(ECCN is sort of viral)
+) I intend to keep the version number in sync with fulcrum-yaafi

Tag:
https://svn.apache.org/repos/asf/turbine/fulcrum/tags/FULCRUM_YAAFI_CRYPTO_1_0_6_RC1
Site:
http://people.apache.org/~sgoeschl/download/fulcrum-yaafi-crypto-1.0.6-RC1/site/
Distributable:
http://people.apache.org/~sgoeschl/download/fulcrum-yaafi-crypto-1.0.6-RC1

+-0/1 as you think fit, thanks!

[ ] +1
[ ] =0
[ ] -1

Vote is open for 96 hours ...


Siegfried Goeschl


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to