On Tue, 2005-08-02 at 12:14 -0700, Eric Pugh wrote:
> First off, I'll start with a mea culpa.  As one of the people who  
> picked up commons-email and moved it from commons-sandbox into  
> commons proper, and a committer on the Turbine project where commons- 
> email came from, I should have done a better job.  My only excuse/ 
> reason was some personal issues came up during my attempt to release  
> 1.0 that pretty much shut down all my activity on OSS stuff.
> 
> However, at this point, I have "cleared the decks", and am ready to  
> get back into being active on the Jakarta Commons community.   I'll  
> take a look at the updated list of changes, including the ones that  
> Siegfried sent me directly in an attempt to get some movement done!

cool

> IIRC, my big difficulty a couple months ago when trying to do the  
> release was I just switched to OSX, and didn't get the whole key  
> signing thing...   

i've been working on key signing documents for the foundation site and
i've used macOSX since the public beta. so, if you don't grok keys yet,
i'd be glad to help.

> I am at OSCON this week, if any other Commons  
> committers are there I bet we could do a bit of pair programming and  
> knock out updated RC and 1.0 this week...

i'm in sunny yorkshire (so that rules me out) but +1 to the concept

> Being as the code has sat for a while since the last 1.0 vote thread  
> passed months ago, I would do another RC first.

the good news is that we already have a recent RC:
http://people.apache.org/~rdonkin/commons-email/

i rolled the release as a stand in for dion (who has been going through
some difficult times lately...)

AIUI the major question remaining is which of the proposed significant
additions to the API should be added before the 1.0. IIRC they are
listed in bugzilla and dion is in favour of one of them. (please check
the recent emails for details).

- robert


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

Reply via email to