Hi Lawrence , I was little busy during the last couple of weeks but now I manged to complete new build scripts for releases.
1.) I used Maven assembly plug-in to create a archive files and used Ant checksum task through the Antrun Maven plug-in to generate hash digests. You can use following command to generate above artifacts. *mvn clean package assembly:assembly antrun:run -P dist * It Would be nice if you can find sometimes to run this yourself. 2.) I have created a wiki page [1] to describe Woden release procedure , It's a modified version of "Woden Decision Making and Development Processes" page. Please take a look and ensure about the procedure also feel free to add necessary changes. 3.) I have little doubt about the SVN tag procedure for releases. please correct me if I'm wrong with following procedure ? a.) In SVN trunk change dependency versions as Apache released versions instead of SNAPSHOT versions . As a example for Axiom version value should be 1.2.8 instead of 1.2.9-SNAPSHOT. b.) Create a SVN tag. c.) Checkout from above tag and build the release artifacts. d.) Once the release is completed change those dependency values again to SNAPSHOT versions in the trunk. Once I get your feedback I will continue with remaining tasks. [1] - http://wiki.apache.org/ws/FrontPage/Woden/WodenReleaseGuide Thanks, On Sat, Oct 31, 2009 at 2:45 AM, Sagara Gunathunga < [email protected]> wrote: > Hi Lawrence, > > Thanks for details and links and i will go through them. Most recent event > for me is Apache Asia Roadshow in early December . Most probably you have to > sign for the release this time . I will update you once i finish the build > scripts. > > Thanks, > > On Sat, Oct 31, 2009 at 2:20 AM, Lawrence Mandel <[email protected]>wrote: > >> >> Here's a link with the details [1]. In general, you need to find Apache >> committers who are already in the Web of trust (see [2]) and have them sign >> your key to integrate you in the Web of trust. This process is usually >> handled at ApacheCon or other events where you can meet face to face. >> >> [1] http://www.apache.org/dev/release-signing.html >> [2] >> http://www.apache.org/~henkp/trust/apache.html<http://www.apache.org/%7Ehenkp/trust/apache.html> >> >> Lawrence >> >> >> >> From: >> Sagara Gunathunga <[email protected]> >> To: >> [email protected] >> Date: 10/30/2009 03:18 PM >> Subject: Re: Woden 1.0 Milestone 9 release >> >> ------------------------------ >> >> >> >> Hi Lawrence, >> >> On Sat, Oct 31, 2009 at 12:30 AM, Lawrence Mandel >> <*[email protected]*<[email protected]>> >> wrote: >> >> Sounds good. Let's talk once you're ready to start the release process. >> >> Sure ! >> >> >> Note that as part of the process someone from Woden will need to sign the >> release. Are you tied in to the Apache Web of Trust? If not, I can sign the >> release. >> >> No I don't tied in to the Apache Web of Trust. Is there any approach to >> get tied in to the Apache Web of Trust ? If it's a complex task better >> to sign the release by you. >> >> Thanks, >> >> >> Lawrence >> >> >> >> >> From: Sagara Gunathunga >> <*[email protected]*<[email protected]> >> > To: *[email protected]* <[email protected]> Date: 10/30/2009 >> 12:23 PM Subject: Re: Woden 1.0 Milestone 9 release >> >> ------------------------------ >> >> >> >> Hi Lawrence , >> >> I'm happy to lead the release process for 0.9 release , but as you said I >> need some helps. This is the first time I'm going to handle a release >> process so there is a possibility to something go wrong , it would be >> great if you can closely inspect my works throughout the release process >> and provide comments as needed. At the moment I have to create a new build >> scripts, once I ready to start resale process I will inform you . >> >> Thanks, >> >> On Fri, Oct 30, 2009 at 9:14 PM, Lawrence Mandel >> <*[email protected]*<[email protected]>> >> wrote: >> >> Hi Sagara, >> >> I don't have time to manage the release process but would be happy to help >> you through it if you'd like to give it a shot. John Kaputin has also >> managed the Woden release process but afaik is tied up working on other >> things at the moment and likely won't have time to lead the process for the >> M9 release. >> >> Lawrence >> >> >> >> From: Sagara Gunathunga >> <*[email protected]*<[email protected]> >> > To: *[email protected]* <[email protected]> Date: 10/26/2009 >> 12:46 PM Subject: Re: Woden 1.0 Milestone 9 release >> >> >> ------------------------------ >> >> >> >> >> >> Sounds great ! We need a new Maven based build script for release process >> , I will look in to this. >> >> BTW so far Lawrence manage the release process as the release manager . >> Lawrence , do you have any time to manage this release ? >> >> If not any one have any other suggestions ? >> >> Thanks, >> >> On Fri, Oct 23, 2009 at 1:55 AM, Arthur Ryman >> <*[email protected]*<[email protected]>> >> wrote: >> +1 >> >> >> On Thu, Oct 22, 2009 at 11:04 AM, Lawrence Mandel >> <*[email protected]*<[email protected]>> >> wrote: >> >> I agree that Woden is due for a release. +1 >> >> Lawrence >> >> From: Jeremy Hughes <*[email protected]* <[email protected]>> To: * >> [email protected]* <[email protected]> Date: 10/22/2009 >> 06:04 AM Subject: Re: Woden 1.0 Milestone 9 release Sent by: * >> [email protected]* <[email protected]> >> >> >> >> ------------------------------ >> >> >> >> +1 >> >> 2009/10/22 Sagara Gunathunga >> <*[email protected]*<[email protected]> >> >: >> > Hi all, >> > >> > During the recent past we have introduced following features to Woden. >> > >> > 1.) Woden serialization feature based on both DOM and OM. >> > 2.) WSDL2.0 components level equals method. >> > 3.) Woden no longer depend on Xerces , possible to switch with any >> > JAXP implementation. >> > 4.) Woden logging strategy. >> > 5.) Maven plugin for Woden WSDL converter >> > 6.) New Maven friendly directory structure. >> > >> > >> > Also other than above , after the milestone 8 release Woden team have >> > resolved following JIRA issues. >> > >> > 1.) (WODEN-224) Dependencies should refactor among modules. >> > 2.) (WODEN-208) Provide simple error message if user tries to parse >> WSDL 1.1 >> > 3.) (WODEN-182) Private QName class causes classloading issues >> > 4.) (WODEN-57) Use ws-commons-java5 for QName class >> > 5.) (WODEN-220) OMWSDLReader should support to read from WSDLSource. >> > 6.) (WODEN-211) Refactor directory layout to be more Maven compliant >> > 7.) (WODEN-170) mvn pom.xml to download test-suite.zip from W3C >> > 8.) (WODEN-181) getInterfaceMessageReferenceElement() method >> > required on BindingMessageReferenceElement >> > 9.) (WODEN-74) Validation does not report a QName resolution error >> > for the {interface fault} property of InterfaceFaultReference >> > 10.) (WODEN-194) Change isSafety() method to isSafe() >> > 11.) (WODEN-195) Improve formatting of messages with no message >> parameters >> > 12.) (WODEN-192) schemaLocation URI not resolved correctly using jar >> files >> > 13.) (WODEN-191) URISyntaxException in SimpleURIResolver when path >> > contains spaces >> > 14.) (WODEN-189) NPE when interface extension used with Element API >> > 15.) (WODEN-179) Remove WSDLReader.readWSDL methods that take an >> > ErrorHandler parameter >> > 16.) (WODEN-178) DescriptionImpl methods addElementDeclaration and >> > addTypeDefinition should not be public >> > 17.) (WODEN-177) Share client-configurable objects across the Woden >> > implementation >> > 18.) (WODEN-176) Remove the setParentElement method from the API >> > 19.) (WODEN-175) ImportElement and IncludeElement should extend >> NestedElement >> > 20.) (WODEN-173) Correct the WSDL object model implementation >> inheritance >> > 21.) (WODEN-174) Include the prefix in QNames from the target namespace >> > 22.) (WODEN-36) Maven build system for Woden >> > >> > >> > >> > IMO at this point we can think about Woden milestone 9 release, WDYT ? >> > >> > >> > >> > Thanks , >> > >> > >> > -- >> > Sagara Gunathunga >> > >> > Blog - *http://ssagara.blogspot.com* <http://ssagara.blogspot.com/> >> > Web - >> > *http://people.apache.org/~sagara/*<http://people.apache.org/%7Esagara/> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: >> > *[email protected]*<[email protected]> >> > For additional commands, e-mail: >> > *[email protected]*<[email protected]> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: >> *[email protected]*<[email protected]> >> For additional commands, e-mail: >> *[email protected]*<[email protected]> >> >> >> >> >> >> >> >> -- >> Sagara Gunathunga >> >> Blog - *http://ssagara.blogspot.com* <http://ssagara.blogspot.com/> >> Web - >> *http://people.apache.org/~sagara/*<http://people.apache.org/%7Esagara/> >> >> >> >> >> -- >> Sagara Gunathunga >> >> Blog - *http://ssagara.blogspot.com* <http://ssagara.blogspot.com/> >> Web - >> *http://people.apache.org/~sagara/*<http://people.apache.org/%7Esagara/> >> >> >> >> >> -- >> Sagara Gunathunga >> >> Blog - *http://ssagara.blogspot.com* <http://ssagara.blogspot.com/> >> Web - >> *http://people.apache.org/~sagara/*<http://people.apache.org/%7Esagara/> >> >> > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/> > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
