Sorry I've been mia. I'm still pretty heads down in development on another 
project. If you can get this done without me go ahead. I agree with Lahiru 
that key signing shouldn't stop the release. Get the release out. We can 
worry about key signing later.

Lawrence 




From:
Sagara Gunathunga <[email protected]>
To:
[email protected]
Date:
04/21/2010 01:39 AM
Subject:
Re: Contributing to woden for the next release



Hi Lahiru , 

Welcome to the Woden project. About the next release, from last October 
code base was freeze for 0.9 release, Woden devs agree to have following 
features for next release [1] and I don't think we need any specific task 
required for next release unless someone come up with a serious issue.   

FYI this is the first release after the Woden code base re-structuring  to 
follow the Maven conventions , I have created required release scripts and 
the release procedure describe here [2] . AFAIK some one bind to the ASF 
web of trust need to sign for proper release , but I'm not yet bind with 
web of trust that is the only obstacle for this release. Sometimes ago 
Lawrence agree to help out for this but seems still he is busy. I'm not 
sure if you are bind with web of trust if so you can help out for signing 
part otherwise have to wait for some one else. 


One thing I couldn't touch so far is status of W3C interoperability report 
described here [3] , I started to do some scripting but couldn't find time 
to finish them, it would be great if you can look in tot this too.  



[1] - http://markmail.org/message/c63rwthvkyp6tlny    
[2] - http://wiki.apache.org/ws/FrontPage/Woden/WodenReleaseGuide
[3] - http://ws.apache.org/woden/dev/devprocess.html


Thanks , 

On Wed, Apr 21, 2010 at 10:28 AM, Lahiru Gunathilake <[email protected]> 
wrote:
Hi Devs,

I'm an Apache Committer for Apache WS projects and PMC Member for Apache 
Qpid and I would like to engage in woden development work for the coming 
release. I saw that you are mentioning to send an email to the dev list if 
someone is willing to contribute towards the project.

I'm thinking of working on couple of issues to be fixed for the coming 
release so that I can get to know the code base first and do something new 
to the project little later. Is there any specific work to be done for the 
next release, can someone please advice me on what to do. For the time 
being I'm thinking of going through the code base and try to fix issues.

Thanks in advance
Lahiru

-- 
Apache Qpid, Worlds dominant messaging middleware..!!!



-- 
Sagara Gunathunga 

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/


Reply via email to