On Sun, Oct 21, 2012 at 8:28 PM, Michael MacFadden
wrote:
> Please referer to the previous email from Angus posted to the dev list
> titles "Release Update" on 9/29/12:
>
> --
>
> Hi All,
> The last review for licensing stuff is up, i'd appreciate it if you all
> looked at it and pointed out a
ome how obfuscating those libraries jars would
solve.
From: "Ed - 0x1b, Inc."
Reply-To:
Date: Sunday, October 21, 2012 7:38 PM
To:
Subject: Re: Releasing...
I'm sorry, why is an open source project obfuscating anything?
On Sun, Oct 21, 2012 at 1:06 PM, Michael MacFadden
;
> > From: Angus Turner
> > Reply-To:
> > Date: Sunday, October 21, 2012 12:58 PM
> > To:
> > Subject: Re: Releasing...
> >
> > Sorry i'm the hold up. My script that I used to remove the copyright
> > headers changed all the comments to
source obfuscator.
>
> And yep. I'll help with the final signing.
>
> ~Michael
>
> From: Angus Turner
> Reply-To:
> Date: Sunday, October 21, 2012 12:58 PM
> To:
> Subject: Re: Releasing...
>
> Sorry i'm the hold up. My script that I used to
bject: Re: Releasing...
Sorry i'm the hold up. My script that I used to remove the copyright
headers changed all the comments to not being javadocs anymore. I've been
busy lately and haven't had time to fix it.
The next step is working out how to obfuscate the jars in a couple of t
Sorry i'm the hold up. My script that I used to remove the copyright
headers changed all the comments to not being javadocs anymore. I've been
busy lately and haven't had time to fix it.
The next step is working out how to obfuscate the jars in a couple of the
libraries to make them compatible wit
Where did we get to on preparing a tet release? Have we got licensing
headers in order? Does anything else stand in our way?
Thx,
Upayavira
