On Tue, Apr 22, 2008 at 9:27 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto:
<snip> > > 2. it uses mailet-api-3.0-SNAPSHOT. i would prefer to use the last > > mailet release. > > > > +1 > Furthermore IIRC current mailet-api trunk is really similar to mailet 2.3. > So maybe a mailet-api 2.3.1 (should be backward compatible) should be made, > too, before moving to 3.0-SNAPSHOT. +0 i'm willing to support such as release but i'm not sure when i'll be able to find the cycles to push it forward... > > 3. i would like to think about creating a baseline release for this > > component. what needs to be done? > > > > We need to update our crypto notice/export stuff. We previously declared > only JAMES-Server 2.3.1 in the ASF pages. yes (there are some more details to be taken care of as well) IMHO it would be better not to ship the crypto-mailets with 3.0 releases but to allow users to download the jar if they want to use the crypto stuff. > > 4. i would like to merge in the work from the cryptography branch. i > > think that it might be best to tidy up trunk first then create a 1.0 > > branch then merge in changes from the branch. > > > > What is the "cryptography branch" ? the development area for Vincenzo and myself to work on OpenPGP, there has been some interest lately in completing this implementation. it should be *much* easier to work on this now that crypto-mailets is a separate project. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
