For the next release, we need to go with Rampart trunk or with a new
release from the trunk as WSS4J 1.6 migration work is happening in the
trunk.
Thanks,
Thilina
On Tue, Jan 3, 2012 at 12:35 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
On Tue, Jan 3, 2012 at 11:41 AM, Samisa Abeysinghe
-1 on moving to trunks until we get a series of successful Bamboo builds.
We need a stable foundation to stand on first, before we do any drastic
changes.
On Tue, Jan 3, 2012 at 11:46 AM, Sameera Jayasoma same...@wso2.com wrote:
Hi Samisa,
On Tue, Jan 3, 2012 at 11:44 AM, Samisa Abeysinghe
Hi Folks,
How about the $subject ?
At the moment, we are sticking with the released versions of 3.2.0. Moving
to Apache trunks requires some changes in certain Carbon components, for
example moving to Neethi 3.0 requires some changes in rampart-* orbit
bundles, caching and throttling modules.
On Tue, Jan 3, 2012 at 9:13 AM, Thilina Buddhika thili...@wso2.com wrote:
Hi Folks,
How about the $subject ?
At the moment, we are sticking with the released versions of 3.2.0. Moving
to Apache trunks requires some changes in certain Carbon components, for
example moving to Neethi 3.0
+1, We have already pointed shindig to the apache trunk, since we need OS
2.0 updates.
Regards,
/Nuwan
On Tue, Jan 3, 2012 at 10:43 AM, Amila Suriarachchi am...@wso2.com wrote:
On Tue, Jan 3, 2012 at 9:13 AM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
How about the $subject ?
On Tue, Jan 3, 2012 at 10:48 AM, Nuwan Bandara nu...@wso2.com wrote:
+1, We have already pointed shindig to the apache trunk, since we need OS
2.0 updates.
+1
Regards,
/Nuwan
On Tue, Jan 3, 2012 at 10:43 AM, Amila Suriarachchi am...@wso2.comwrote:
On Tue, Jan 3, 2012 at 9:13 AM,
On Tue, Jan 3, 2012 at 9:13 AM, Thilina Buddhika thili...@wso2.com wrote:
Hi Folks,
How about the $subject ?
At the moment, we are sticking with the released versions of 3.2.0. Moving
to Apache trunks requires some changes in certain Carbon components, for
example moving to Neethi 3.0
On Tue, Jan 3, 2012 at 11:41 AM, Sameera Jayasoma same...@wso2.com wrote:
On Tue, Jan 3, 2012 at 9:13 AM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
How about the $subject ?
At the moment, we are sticking with the released versions of 3.2.0.
Moving to Apache trunks requires some
Hi Samisa,
On Tue, Jan 3, 2012 at 11:44 AM, Samisa Abeysinghe sam...@wso2.com wrote:
On Tue, Jan 3, 2012 at 11:41 AM, Sameera Jayasoma same...@wso2.comwrote:
On Tue, Jan 3, 2012 at 9:13 AM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
How about the $subject ?
At the moment, we
I am not a fan of using Apache trunks. The problem with using Apache trunks
is that, we will have longer cycles to release from our trunk.
On Tue, Jan 3, 2012 at 11:46 AM, Sameera Jayasoma same...@wso2.com wrote:
Hi Samisa,
On Tue, Jan 3, 2012 at 11:44 AM, Samisa Abeysinghe
+1.
We can safely move to Synapse trunk as all the fixes/features available in
2.1.0-wso2v4/5 are already included in the Synapse trunk.
On Tue, Jan 3, 2012 at 10:54 AM, Pradeep Fernando prad...@wso2.com wrote:
On Tue, Jan 3, 2012 at 10:48 AM, Nuwan Bandara nu...@wso2.com wrote:
+1, We have
+1.
Lets update the Carbon version in the trunk to 4.0.0-SNAPSHOT also.
Thanks,
Sameera.
On Tue, Jan 3, 2012 at 9:13 AM, Thilina Buddhika thili...@wso2.com wrote:
Hi Folks,
How about the $subject ?
At the moment, we are sticking with the released versions of 3.2.0. Moving
to Apache
Why do we need Apache trunks? Why cannot we live with a release Apache
projects?
We are adding double trouble if we depend on bleeding Apache trunks.
This is similar to having a stable Carbon core and depend the
products/features on a stable core.
On Tue, Jan 3, 2012 at 10:54 AM, Pradeep
On Tue, Jan 3, 2012 at 11:41 AM, Samisa Abeysinghe sam...@wso2.com wrote:
Why do we need Apache trunks? Why cannot we live with a release Apache
projects?
IMO, it's because most of apache releases are not very frequent and the
fixes are available in the trunks only. For instance in the
On Tue, Jan 3, 2012 at 11:41 AM, Samisa Abeysinghe sam...@wso2.com wrote:
Why do we need Apache trunks? Why cannot we live with a release Apache
projects?
We are adding double trouble if we depend on bleeding Apache trunks.
This is similar to having a stable Carbon core and depend the
15 matches
Mail list logo