You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Samisa Abeysinghe <sa...@wso2.com> on 2007/02/05 07:01:35 UTC
[Axis2] Time for 1.0 Release
We have been able to come a long way since we started the Axis2/C effort.
IMHO, by now, we have the basic Axis2 architecture implemented with
Axis2/C as well as many quality of service modules such as Rampart and
Sandesha2.
So I would like to propose that we release 1.0 with current set of
features and look to stabilize the current code base before we release
1.0 as much as possible.
I think we should be able to do this release in one months time.
Thoughts, comments please.
Thanks,
Samisa...
--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Time for 1.0 Release
Posted by Dinesh Premalal <xy...@gmail.com>.
Samisa Abeysinghe <sa...@wso2.com> writes:
> I added version macros and functions for compile time and runtime
> checks looking how it was done it APR.
> I went through the APR versioning doc couple of times and I hope we
> could use as it is as our versioning guidelines.
+1 , It is better to get exsisting guideline and tailor it to our
requirements rather than developing it from the scratch.
thanks,
Dinesh
--
Dinesh Premalal
dinesh@wso2.com
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Time for 1.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
>
> As a C project, I would suggest that it might make sense for Axis2/C
> to follow the lead of other major Apache C projects, such as APR and
> httpd. These two have fairly detailed versioning guidelines and
> requirements, especially in relation to the promise of stable APIs
> and ABIs, compile-time options, etc.:
>
> http://apr.apache.org/versioning.html
>
I added version macros and functions for compile time and runtime checks
looking how it was done it APR.
I went through the APR versioning doc couple of times and I hope we
could use as it is as our versioning guidelines.
Thanks,
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Time for 1.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Chris Darroch wrote:
> Samisa Abeysinghe wrote:
>
>
>> So I would like to propose that we release 1.0 with current set of
>> features and look to stabilize the current code base before we release
>> 1.0 as much as possible.
>> I think we should be able to do this release in one months time.
>>
>
> I fear I'm rather swamped in work for the next few months, but
> I hope to review the codebase before the 1.0 release.
>
>
> I do have a related issue, though, that I think is worth
> discussing before such a release, and that's what the versioning
> scheme and rules should be for the project. I'd think these
> need to be nailed down more or less in stone prior to a 1.x
> or 1.x.x major release.
>
> Users should understand what kinds of guarantees are being made
> with regard to future compatibility, since we expect them to develop
> third-party service modules. They should certainly not have to
> rewrite or recompile these modules if they upgrade their Axis2/C
> installation to pick up a security bug fix, for example.
>
> So, with what versions is it acceptable for Axis2/C to break
> compatibility with previous versions? How should the versioning
> scheme indicate such transitions? What about patch releases to
> fix security bugs; can these change the API or ABI at all? And
> so forth.
>
>
> As a C project, I would suggest that it might make sense for Axis2/C
> to follow the lead of other major Apache C projects, such as APR and
> httpd. These two have fairly detailed versioning guidelines and
> requirements, especially in relation to the promise of stable APIs
> and ABIs, compile-time options, etc.:
>
> http://apr.apache.org/versioning.html
> http://svn.apache.org/viewvc/httpd/httpd/trunk/VERSIONING?view=markup
>
+1. It would take some effort to make the binary compatibility to get
going. I have dropped the ops in many of the structs but a few remains.
I hope we can adopt the above guidelines as they are to our project.
I wild look into the above and see what else we need to do in order to
adhere to the version guidelines.
> Axis2/C also installs a lot of libraries, and as such, I'd suggest
> that it follow the same guidelines that APR does, with respect to
> parallel installation and library naming:
>
> http://www106.pair.com/rhp/parallel.html
>
> Such a scheme allows, for example, a libwoden-2.so from a future
> Axis2/C installation to be installed alongside a libwoden-1.so
> from a previous installation.
>
+1. We would need to re-visit our build system for this. But yes it is
worth the effort.
Samisa...
>
> One interesting issue is that Axis2/C is contains both applications,
> like httpd, and libraries, like APR. It also contains a number of
> related sub-projects. It allows for third-party service modules to be
> written against its API, like httpd. And it may compile its own
> "third-party" modules (e.g., mod_axis2) for use with httpd.
>
> These complexities probably mean that we need to develop a fairly
> comprehensive set of versioning rules, and possibly make some
> changes to the installation process (e.g., to follow the parallel
> installation guidelines above) prior to announcing a 1.0 or 1.0.0
> stable release.
>
> Chris.
>
>
--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Time for 1.0 Release
Posted by Chris Darroch <ch...@pearsoncmg.com>.
Samisa Abeysinghe wrote:
> So I would like to propose that we release 1.0 with current set of
> features and look to stabilize the current code base before we release
> 1.0 as much as possible.
> I think we should be able to do this release in one months time.
I fear I'm rather swamped in work for the next few months, but
I hope to review the codebase before the 1.0 release.
I do have a related issue, though, that I think is worth
discussing before such a release, and that's what the versioning
scheme and rules should be for the project. I'd think these
need to be nailed down more or less in stone prior to a 1.x
or 1.x.x major release.
Users should understand what kinds of guarantees are being made
with regard to future compatibility, since we expect them to develop
third-party service modules. They should certainly not have to
rewrite or recompile these modules if they upgrade their Axis2/C
installation to pick up a security bug fix, for example.
So, with what versions is it acceptable for Axis2/C to break
compatibility with previous versions? How should the versioning
scheme indicate such transitions? What about patch releases to
fix security bugs; can these change the API or ABI at all? And
so forth.
As a C project, I would suggest that it might make sense for Axis2/C
to follow the lead of other major Apache C projects, such as APR and
httpd. These two have fairly detailed versioning guidelines and
requirements, especially in relation to the promise of stable APIs
and ABIs, compile-time options, etc.:
http://apr.apache.org/versioning.html
http://svn.apache.org/viewvc/httpd/httpd/trunk/VERSIONING?view=markup
Axis2/C also installs a lot of libraries, and as such, I'd suggest
that it follow the same guidelines that APR does, with respect to
parallel installation and library naming:
http://www106.pair.com/rhp/parallel.html
Such a scheme allows, for example, a libwoden-2.so from a future
Axis2/C installation to be installed alongside a libwoden-1.so
from a previous installation.
One interesting issue is that Axis2/C is contains both applications,
like httpd, and libraries, like APR. It also contains a number of
related sub-projects. It allows for third-party service modules to be
written against its API, like httpd. And it may compile its own
"third-party" modules (e.g., mod_axis2) for use with httpd.
These complexities probably mean that we need to develop a fairly
comprehensive set of versioning rules, and possibly make some
changes to the installation process (e.g., to follow the parallel
installation guidelines above) prior to announcing a 1.0 or 1.0.0
stable release.
Chris.
--
GPG Key ID: 366A375B
GPG Key Fingerprint: 485E 5041 17E1 E2BB C263 E4DE C8E3 FA36 366A 375B
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Time for 1.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
BTW, I would like to volunteer as the release manager. If anyone else
is interested in volunteering as release manager, please let know.
Samisa...
Dinesh Premalal wrote:
> Samisa Abeysinghe <sa...@wso2.com> writes:
>
>> So I would like to propose that we release 1.0 with current set of
>> features and look to stabilize the current code base before we release
>> 1.0 as much as possible.
>> I think we should be able to do this release in one months time.
>>
>
> +1, Are we going to release Savan and Sandesha2 with Axis2/C or as seperate
> projects ? Because we had in mind to move those projects as separate
> projects.
>
> thanks,
> Dinesh
>
--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Time for 1.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Dinesh Premalal wrote:
> Samisa Abeysinghe <sa...@wso2.com> writes:
>
>> So I would like to propose that we release 1.0 with current set of
>> features and look to stabilize the current code base before we release
>> 1.0 as much as possible.
>> I think we should be able to do this release in one months time.
>>
>
> +1, Are we going to release Savan and Sandesha2 with Axis2/C or as seperate
> projects ? Because we had in mind to move those projects as separate
> projects.
>
Sandesha2 is seperate already. I think you are questioning about Rampart
and Savan.
I would rather keep them in the same repo for 1.0 and look to separate
them post 1.0 if required.
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Time for 1.0 Release
Posted by Dinesh Premalal <xy...@gmail.com>.
Samisa Abeysinghe <sa...@wso2.com> writes:
> So I would like to propose that we release 1.0 with current set of
> features and look to stabilize the current code base before we release
> 1.0 as much as possible.
> I think we should be able to do this release in one months time.
+1, Are we going to release Savan and Sandesha2 with Axis2/C or as seperate
projects ? Because we had in mind to move those projects as separate
projects.
thanks,
Dinesh
--
Dinesh Premalal
dinesh@wso2.com
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org