You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by Dasarath Weeratunge <dw...@purdue.edu> on 2007/07/06 16:40:24 UTC

Re: a code release anyone?

Quoting Hannes Erven <ha...@erven.at>:

> Hi folks,
> 
> 
> 
> > How about we do a release for kandula-1? What's the process followed by
> axis2
> > people? Its great if we can also release kandula-2 at the same time but
> docs and
> > sample applications are still on their way it seems :-)
> 
> 
> I'd suggest to wait for a Kandula-1 release until the WS-BA samples have 
> been put in -- the developers decided lately do delegate that work to 
> Georg and me, but since we do not yet have collected enough karma... ;-)
> 
> But, as soon as that's done, +1 from me for a Kandula-0.2 release.

Definitely. We should wait till you get karma and are able to add in the
samples and docs.

I will try to compile a list of things that we need to do
before the code release. Then everyone can add/delete items to/from that. I was
hoping Thilina (since he is/was the release manager for axis2) would let us 
know about the process that needs to be followed to do a code release at 
Apache. Even a link to a webpage will do. Based on the list of things we have
completed let us decide whether we can up the code release version up a little
bit to say around .7. In the long run we should aim for version 1.0 which will 
require at least couple more code releases within a short span before that.

thanks,
--dasarath






> 
> 
> As for Kandula-2, the last time I took a quick look at the WS-BA 
> components they did not seem somewhere near a release, but I guess the 
> Kandula-2 experts should speak for themselves.
> 
> 
> Best regards,
> 
> 	-hannes
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org


Re: a code release anyone?

Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
I'm more than willing to give a helping hand to the release process..
First we might need to identify a release manager for the release, who
would drive the release process...

Following are couple of helpful links..
http://www.apache.org/dev/release.html
http://incubator.apache.org/guides/releasemanagement.html#best-practice

thanks,
Thilina

PS: Following is a recent mail by Dims regarding the new guidelines
for a releases in the WS project...

Folks,

How about we follow incubator project guidelines in addition to what
we do now...Please reply back to general@ws (am BCC'ing all dev
lists).

- All Release binaries must be be explicitly VOTE'd on
- All Release binaries should pass the RAT test [1] (exception: not
sure if RAT support C/C++ code)
- There must be at least 3 Binding PMC VOTE's on each release (which
we do already)

Thanks,
dims

[1] http://code.google.com/p/arat/

On 7/6/07, Dasarath Weeratunge <dw...@purdue.edu> wrote:
> Quoting Hannes Erven <ha...@erven.at>:
>
> > Hi folks,
> >
> >
> >
> > > How about we do a release for kandula-1? What's the process followed by
> > axis2
> > > people? Its great if we can also release kandula-2 at the same time but
> > docs and
> > > sample applications are still on their way it seems :-)
> >
> >
> > I'd suggest to wait for a Kandula-1 release until the WS-BA samples have
> > been put in -- the developers decided lately do delegate that work to
> > Georg and me, but since we do not yet have collected enough karma... ;-)
> >
> > But, as soon as that's done, +1 from me for a Kandula-0.2 release.
>
> Definitely. We should wait till you get karma and are able to add in the
> samples and docs.
>
> I will try to compile a list of things that we need to do
> before the code release. Then everyone can add/delete items to/from that. I was
> hoping Thilina (since he is/was the release manager for axis2) would let us
> know about the process that needs to be followed to do a code release at
> Apache. Even a link to a webpage will do. Based on the list of things we have
> completed let us decide whether we can up the code release version up a little
> bit to say around .7. In the long run we should aim for version 1.0 which will
> require at least couple more code releases within a short span before that.
>
> thanks,
> --dasarath
>
>
>
>
>
>
> >
> >
> > As for Kandula-2, the last time I took a quick look at the WS-BA
> > components they did not seem somewhere near a release, but I guess the
> > Kandula-2 experts should speak for themselves.
> >
> >
> > Best regards,
> >
> >       -hannes
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: kandula-dev-help@ws.apache.org
>
>


-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org