RE: Post-graduation release

2007-02-17 Thread Nicko Cadell
> Does the version info for the .dll's identify which variant > each file is? Likely it should either have an Apache > copyright or license notice in the version info. Each assembly has a different title. #if (CLI_1_0) [assembly: AssemblyTitle("log4net for CLI 1.0 Compatible Frameworks")] #e

Re: Post-graduation release

2007-02-17 Thread Curt Arnold
On Feb 17, 2007, at 3:05 PM, Nicko Cadell wrote: 1. Build should be reproducible (other than timestamps and other trivia) I'm not sure how you are handling strong naming in your releases. If you have a signing key, we may want to find a way to securely share the key. Perhaps have it gpg e

RE: Post-graduation release

2007-02-17 Thread Nicko Cadell
> 1. Build should be reproducible (other than timestamps and > other trivia) > > I'm not sure how you are handling strong naming in your > releases. If you have a signing key, we may want to find a > way to securely share the key. Perhaps have it gpg encrypted > for multiple private keys

Post-graduation release

2007-02-16 Thread Curt Arnold
I think it would be good in relatively short order to do a post- graduation release. Don't know where things are in the development cycle, so I'll defer to everybody else on the actual timing. There are a few things that will need to be checked on the release. I'm rattlin