Hi Scott,

+) I will update the documentation

+) the XML test files are indeed broken and this could be from
code-wrestling two years ago - thanks for spotting this

+) which source archive do you mean -
fulcrum-yaafi-crypto-1.0.7-SNAPSHOT-sources.jar or
fulcrum-yaafi-crypto-1.0.7-SNAPSHOT-src.xxx? Both of them include
licence and notice file.

Well, it looks like another release candidate for today ...

Cheers,

Siegfried Goeschl

Scott Eade wrote:
>
>> Hi folks,
>>
>> after updateing theWiki
>> (http://wiki.apache.org/turbine/FulcrumMaven2Migration) how to make a
>> release I would like to call another vote to release
>> fulcrum-yaafi-crypto-1.0.6
>>
>> Tag:
>>
>> https://svn.apache.org/repos/asf/turbine/fulcrum/tags/FULCRUM_YAAFI_CRYPTO_1_0_6/
>>
>>
>> Site:
>>
>> http://turbine.apache.org/builds/fulcrum/fulcrum-yaafi-crypto/1.0.6/RC3/site/
>>
>>
>> Binaries:
>>
>> http://turbine.apache.org/builds/turbine/fulcrum/fulcrum-yaafi-crypto/1.0.6/RC3/staged/org/apache/fulcrum/fulcrum-yaafi-crypto/1.0.6
>>
>>
>> [X] +1 release it
>> [ ] +0 go ahead I don't care
>> [ ] -1 no, do not release it because
>>   
> But:
> * There really needs to be a documentation page added that shows how
> to use it - "Look at the tests."
> * The test file plain-utf16.xml is wrong - the first XML declaration
> needs to be discarded and the license header needs to come after the
> second XML declaration such that the file begins with the byte order
> mark.
> * The test file plain.xml exhibits the same problems as
> plain-utf16.xml - presumably this should be something other than utf16.
> * Should the src archive include anything outside of the src
> directory, e.g. at the very least the pom and license file?
>
> Scott
>
> ---------------------------------------------------------------------
> 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