You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by David Blevins <da...@visi.com> on 2006/03/14 04:50:40 UTC
[VOTE] Release Axis 1.4 final branch
Dims created an Axis 1.4 final branch in early Dec at:
http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
There was a vote to release this that went through but the binaries
were never produced. Geronimo, Jonas and others are using this code
and it would be great to see it made official. I am volunteering as
Release Manager and would like to kicked this release out the door
before the month is through.
Here is my +1 for me as Release Manager and seeing 1.4 released this
month.
-David
Re: [RESULT] Release Axis 1.4 final branch
Posted by Glen Daniels <gl...@thoughtcraft.com>.
OK, +1 on releasing the branch as 1.4, then gearing up for 1.4.1 from
HEAD soon thereafter. Go for it David! Let us know if you need
anything, and thanks.
--Glen
Re: [RESULT] Release Axis 1.4 final branch
Posted by David Blevins <da...@visi.com>.
On Apr 4, 2006, at 12:31 AM, Guillaume Sauthier wrote:
> Glen Daniels wrote:
>> Hi David!
>>
>> David Blevins wrote:
>>> Looks like there is more or less a consensus to release 1.4 final
>>> branch. Going to get started on that then.
>>
>> Sounds good, though there have actually been some good fixes added
>> to the trunk since the 1.4 branch.... Considering we haven't done
>> the release yet, I'm doubting anyone is really using the 1.4
>> branch as a checkpoint as yet (?) - do you think it might be worth
>> merging the HEAD over to 1.4 before releasing? I'd be +1 for
>> this, but even if not I'd like to see the HEAD go out as 1.4.1
>> pretty quickly....
> We (JOnAS team) are already shipping with that 1_4_FINAL version.
> (Are we alone to use that version, geronimo guys ?) So we would
> like to have an official release.
> We know that that version is ok in regards with JOnAS test suite
> (and TCK).
>
Right, Geronimo did the same thing.
-David
> For us, 1.4 is what is located in that 1_4_FINAL branch.
> Then, the HEAD should be 1.5 (if there are a lot of changes) or
> 1.4.1 (is less changes).
>
> What do you think ?
>
> Guillaume
>>
>>> Glen, as I understand it, you've done all the Axis releases to
>>> date. You have a checklist or something of the steps required?
>>> Or at minimum, a couple tips?
>>
>> Here's what I think needs doing, which has usually been some
>> combination of myself and dims (he's usually done at least the
>> last two steps).
>>
>> * Make sure version is updated (xmls/properties.xml,
>> release-notes.html, changelog.html)
>>
>> * Make sure change log is updated (changelog.html)
>>
>> * Make sure release notes are accurate (release-notes.html)
>>
>> * Make sure you have ALL optional dependencies installed
>> so that the build works out-of-the-box with all extensions
>>
>> * Clean everything, ensure all-tests works
>>
>> * Build dists
>>
>> * Calc checksums, sign release
>> (we haven't been doing this but need to. You can find info at
>> http://www.apache.org/dev/release-signing.html)
>>
>> * Upload to /www/www.apache.org/dist/ws/axis/ (create new dir in
>> there)
>>
>> * Update the Axis web site
>>
>> * Update the Maven repository
>>
>> Jakarta has a terrific release guide at http://jakarta.apache.org/
>> commons/releases/release.html, we should have a version of that
>> for WS....
>>
>> So let's discuss my question above, and then once we decide, let
>> me/us know if you have any problems/issues, and thanks so much for
>> helping out!
>>
>> --Glen
>>
>
> <Guillaume.Sauthier.vcf>
RE: [RESULT] Release Axis 1.4 final branch
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Tue, 2006-04-04 at 08:59 -0700, Tom Jordahl wrote:
> I think we have had this discussion. Twice. Ship 1.4, then we can ship
> the HEAD. We voted.
+1 ..
Sanjiva.
RE: [RESULT] Release Axis 1.4 final branch
Posted by Tom Jordahl <tj...@adobe.com>.
I think we have had this discussion. Twice. Ship 1.4, then we can ship
the HEAD. We voted.
It takes a while to get a release done around here - enough so that
1.4.1 probably won't follow too hard on the heels of 1.4. :-)
--
Tom Jordahl
Adobe
-----Original Message-----
From: Guillaume Sauthier [mailto:Guillaume.Sauthier@objectweb.org]
Sent: Tuesday, April 04, 2006 3:32 AM
To: axis-dev@ws.apache.org
Subject: Re: [RESULT] Release Axis 1.4 final branch
Glen Daniels wrote:
> Hi David!
>
> David Blevins wrote:
>> Looks like there is more or less a consensus to release 1.4 final
>> branch. Going to get started on that then.
>
> Sounds good, though there have actually been some good fixes added to
> the trunk since the 1.4 branch.... Considering we haven't done the
> release yet, I'm doubting anyone is really using the 1.4 branch as a
> checkpoint as yet (?) - do you think it might be worth merging the
> HEAD over to 1.4 before releasing? I'd be +1 for this, but even if
> not I'd like to see the HEAD go out as 1.4.1 pretty quickly....
We (JOnAS team) are already shipping with that 1_4_FINAL version. (Are
we alone to use that version, geronimo guys ?) So we would like to have
an official release.
We know that that version is ok in regards with JOnAS test suite (and
TCK).
For us, 1.4 is what is located in that 1_4_FINAL branch.
Then, the HEAD should be 1.5 (if there are a lot of changes) or 1.4.1
(is less changes).
What do you think ?
Guillaume
>
>> Glen, as I understand it, you've done all the Axis releases to date.
>> You have a checklist or something of the steps required? Or at
>> minimum, a couple tips?
>
> Here's what I think needs doing, which has usually been some
> combination of myself and dims (he's usually done at least the last
> two steps).
>
> * Make sure version is updated (xmls/properties.xml,
> release-notes.html, changelog.html)
>
> * Make sure change log is updated (changelog.html)
>
> * Make sure release notes are accurate (release-notes.html)
>
> * Make sure you have ALL optional dependencies installed
> so that the build works out-of-the-box with all extensions
>
> * Clean everything, ensure all-tests works
>
> * Build dists
>
> * Calc checksums, sign release
> (we haven't been doing this but need to. You can find info at
> http://www.apache.org/dev/release-signing.html)
>
> * Upload to /www/www.apache.org/dist/ws/axis/ (create new dir in
there)
>
> * Update the Axis web site
>
> * Update the Maven repository
>
> Jakarta has a terrific release guide at
> http://jakarta.apache.org/commons/releases/release.html, we should
> have a version of that for WS....
>
> So let's discuss my question above, and then once we decide, let me/us
> know if you have any problems/issues, and thanks so much for helping
out!
>
> --Glen
>
Re: [RESULT] Release Axis 1.4 final branch
Posted by Guillaume Sauthier <Gu...@objectweb.org>.
Glen Daniels wrote:
> Hi David!
>
> David Blevins wrote:
>> Looks like there is more or less a consensus to release 1.4 final
>> branch. Going to get started on that then.
>
> Sounds good, though there have actually been some good fixes added to
> the trunk since the 1.4 branch.... Considering we haven't done the
> release yet, I'm doubting anyone is really using the 1.4 branch as a
> checkpoint as yet (?) - do you think it might be worth merging the
> HEAD over to 1.4 before releasing? I'd be +1 for this, but even if
> not I'd like to see the HEAD go out as 1.4.1 pretty quickly....
We (JOnAS team) are already shipping with that 1_4_FINAL version. (Are
we alone to use that version, geronimo guys ?) So we would like to have
an official release.
We know that that version is ok in regards with JOnAS test suite (and TCK).
For us, 1.4 is what is located in that 1_4_FINAL branch.
Then, the HEAD should be 1.5 (if there are a lot of changes) or 1.4.1
(is less changes).
What do you think ?
Guillaume
>
>> Glen, as I understand it, you've done all the Axis releases to date.
>> You have a checklist or something of the steps required? Or at
>> minimum, a couple tips?
>
> Here's what I think needs doing, which has usually been some
> combination of myself and dims (he's usually done at least the last
> two steps).
>
> * Make sure version is updated (xmls/properties.xml,
> release-notes.html, changelog.html)
>
> * Make sure change log is updated (changelog.html)
>
> * Make sure release notes are accurate (release-notes.html)
>
> * Make sure you have ALL optional dependencies installed
> so that the build works out-of-the-box with all extensions
>
> * Clean everything, ensure all-tests works
>
> * Build dists
>
> * Calc checksums, sign release
> (we haven't been doing this but need to. You can find info at
> http://www.apache.org/dev/release-signing.html)
>
> * Upload to /www/www.apache.org/dist/ws/axis/ (create new dir in there)
>
> * Update the Axis web site
>
> * Update the Maven repository
>
> Jakarta has a terrific release guide at
> http://jakarta.apache.org/commons/releases/release.html, we should
> have a version of that for WS....
>
> So let's discuss my question above, and then once we decide, let me/us
> know if you have any problems/issues, and thanks so much for helping out!
>
> --Glen
>
Re: [RESULT] Release Axis 1.4 final branch
Posted by Bjorn Townsend <bj...@sourcelabs.com>.
On Mar 31, 2006, at 9:26 AM March 31, Glen Daniels wrote:
> Sounds good, though there have actually been some good fixes added
> to the trunk since the 1.4 branch.... Considering we haven't done
> the release yet, I'm doubting anyone is really using the 1.4 branch
> as a checkpoint as yet (?) - do you think it might be worth merging
> the HEAD over to 1.4 before releasing? I'd be +1 for this, but
> even if not I'd like to see the HEAD go out as 1.4.1 pretty
> quickly....
Glen,
I wrote up a summary of major changes between 1.4-FINAL and the trunk
a couple of weeks ago -- if it would be helpful I'd be happy to
resend it offlist. Let me know. I got the impression that most people
wanted to release 1.4-FINAL right now, without any changes, and worry
about 1.4.1 later.
Thanks,
Bjorn
Re: [RESULT] Release Axis 1.4 final branch
Posted by David Blevins <da...@visi.com>.
On Mar 31, 2006, at 9:26 AM, Glen Daniels wrote:
> Hi David!
>
> David Blevins wrote:
>> Looks like there is more or less a consensus to release 1.4 final
>> branch. Going to get started on that then.
>
> Sounds good, though there have actually been some good fixes added
> to the trunk since the 1.4 branch.... Considering we haven't done
> the release yet, I'm doubting anyone is really using the 1.4 branch
> as a checkpoint as yet (?) - do you think it might be worth merging
> the HEAD over to 1.4 before releasing? I'd be +1 for this, but
> even if not I'd like to see the HEAD go out as 1.4.1 pretty
> quickly....
>
I'm happy to work on releasing either the existing 1.4 branch or a
new one made from trunk.
-David
Re: [RESULT] Release Axis 1.4 final branch
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi David!
David Blevins wrote:
> Looks like there is more or less a consensus to release 1.4 final
> branch. Going to get started on that then.
Sounds good, though there have actually been some good fixes added to
the trunk since the 1.4 branch.... Considering we haven't done the
release yet, I'm doubting anyone is really using the 1.4 branch as a
checkpoint as yet (?) - do you think it might be worth merging the HEAD
over to 1.4 before releasing? I'd be +1 for this, but even if not I'd
like to see the HEAD go out as 1.4.1 pretty quickly....
> Glen, as I understand it, you've done all the Axis releases to date.
> You have a checklist or something of the steps required? Or at minimum,
> a couple tips?
Here's what I think needs doing, which has usually been some combination
of myself and dims (he's usually done at least the last two steps).
* Make sure version is updated (xmls/properties.xml,
release-notes.html, changelog.html)
* Make sure change log is updated (changelog.html)
* Make sure release notes are accurate (release-notes.html)
* Make sure you have ALL optional dependencies installed
so that the build works out-of-the-box with all extensions
* Clean everything, ensure all-tests works
* Build dists
* Calc checksums, sign release
(we haven't been doing this but need to. You can find info at
http://www.apache.org/dev/release-signing.html)
* Upload to /www/www.apache.org/dist/ws/axis/ (create new dir in there)
* Update the Axis web site
* Update the Maven repository
Jakarta has a terrific release guide at
http://jakarta.apache.org/commons/releases/release.html, we should have
a version of that for WS....
So let's discuss my question above, and then once we decide, let me/us
know if you have any problems/issues, and thanks so much for helping out!
--Glen
Re: [RESULT] Release Axis 1.4 final branch
Posted by Franz Fehringer <fe...@isogmbh.de>.
Will there also be a release (1.4.1?) from the trunk?
Greetings
Franz
David Blevins schrieb:
> Looks like there is more or less a consensus to release 1.4 final
> branch. Going to get started on that then.
>
> There were 5 +1s and no other votes.
>
> Glen, as I understand it, you've done all the Axis releases to date.
> You have a checklist or something of the steps required? Or at
> minimum, a couple tips?
>
> -David
>
> On Mar 13, 2006, at 7:50 PM, David Blevins wrote:
>
>> Dims created an Axis 1.4 final branch in early Dec at:
>>
>> http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
>>
>> There was a vote to release this that went through but the binaries
>> were never produced. Geronimo, Jonas and others are using this code
>> and it would be great to see it made official. I am volunteering as
>> Release Manager and would like to kicked this release out the door
>> before the month is through.
>>
>> Here is my +1 for me as Release Manager and seeing 1.4 released this
>> month.
>>
>> -David
>>
>
[RESULT] Release Axis 1.4 final branch
Posted by David Blevins <da...@visi.com>.
Looks like there is more or less a consensus to release 1.4 final
branch. Going to get started on that then.
There were 5 +1s and no other votes.
Glen, as I understand it, you've done all the Axis releases to date.
You have a checklist or something of the steps required? Or at
minimum, a couple tips?
-David
On Mar 13, 2006, at 7:50 PM, David Blevins wrote:
> Dims created an Axis 1.4 final branch in early Dec at:
>
> http://svn.apache.org/repos/asf/webservices/axis/branches/
> AXIS_1_4_FINAL
>
> There was a vote to release this that went through but the binaries
> were never produced. Geronimo, Jonas and others are using this
> code and it would be great to see it made official. I am
> volunteering as Release Manager and would like to kicked this
> release out the door before the month is through.
>
> Here is my +1 for me as Release Manager and seeing 1.4 released
> this month.
>
> -David
>
Re: [VOTE] Release Axis 1.4 final branch
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me. +1 to backport whatever needed at the discretion of the
Release Manager.
thanks,
dims
On 3/17/06, Bjorn Townsend <bj...@sourcelabs.com> wrote:
>
> Hello all,
>
> I'm interested in seeing an official 1.4 release, so I took some time
> and looked at the diffs and svn logs between 1.3, 1.4-FINAL and
> trunk. I thought summarizing what I found might help people decide
> whether they want to vote in favor of releasing 1.4-FINAL as is, or
> support a release from trunk.
>
> Fixes in 1.4-FINAL branch (that are not present in 1.3-FINAL):
>
> No JIRA issue: Prevent an NPE when curMsg is null
> AXIS-2314 - Axis leaking Session objects
> AXIS-2267 - incorrect type serialization
> AXIS-2232 - mappings in TypeDesc can't be GC'd
> AXIS-2013 - deserialization of exception fails
> AXIS-2281 - (docs fix)
> AXIS-2278 - fix for memory leak caused by JavaUtils.enumMap
> AXIS-2264 - org.apache.axis.client.Call implementation Bug =>
> CurrentModificationException if an other VM is used (e.g. http://
> www.cacaojvm.org)
> AXIS-2236 - Bad constructor with derived classes that inherit xs:any
> members
>
>
> Fixes added in trunk:
>
> AXIS-2365 - SOAPDocumentImpl calls MessageElement constructor with
> wrong arguments
> AXIS-1995 - ServiceLifecycle.destroy() never called
> AXIS-2347 - detatching the body of a soap envelope and trying to set
> its body with a new soap body results in a DOMException
> AXIS-2346 - Issue with the way the localNames are created in WSDL2Java
>
> Notable improvements in trunk:
> (no JIRA issue cited) - changes to avoid using enum as a variable name
> (no JIRA issue cited) - Add WS-Addr support; looks like the W3C level
> is still in progress
> (no JIRA issue cited) - Fixed TCK test
> (no JIRA issue cited) - use new clover jar
> (no JIRA issue cited) - allow non-Axis code to set the current
> messagecontext
> (no JIRA issue cited) - allow SOAP processors that return 200 instead
> of 202
> (no JIRA issue cited) - allow services to make operations one-way
> (no JIRA issue cited) - more logic for msgProvider method search
> (no JIRA issue cited) - turn off XML pretty print by default
> (no JIRA issue cited) - various MessageContext logic improvements
> (no JIRA issue cited) - allow clients to set the client engine's
> config file directly without manually creating a new FileProvider
> (no JIRA issue cited) - de/serialization support for messageContext
> (no JIRA issue cited) - Sample using XmlBeans serializer/deserializer
>
>
> I noticed that there didn't seem to be any major improvements in 1.4-
> FINAL, only bugfixes. My thought is that since it contains new
> features, trunk might need more review before it can be released,
> especially since things like WSA support are still in progress and
> have checkins from as recently as yesterday. It also looks to me
> like most of the important fixes - like the NPE and the memory leaks
> - are already in 1.4-FINAL. So I give my +1 for releasing 1.4-FINAL
> as it stands as soon as possible since it would help Geronimo, with
> the caveat that it might be worth backporting AXIS-1995 since it
> looks like a memory leak and the change is fairly minor.
>
> Regards,
> Bjorn Townsend
>
--
Davanum Srinivas : http://wso2.com/blogs/
RE: [VOTE] Release Axis 1.4 final branch
Posted by Tom Jordahl <tj...@adobe.com>.
+1 to release 1.4 as it stands. +0 to backport memory leak patch.
--
Tom Jordahl
Adobe ColdFusion Team
-----Original Message-----
From: Bjorn Townsend [mailto:bjorn@sourcelabs.com]
Sent: Friday, March 17, 2006 6:19 PM
To: axis-dev@ws.apache.org
Subject: Re: [VOTE] Release Axis 1.4 final branch
Hello all,
I'm interested in seeing an official 1.4 release, so I took some time
and looked at the diffs and svn logs between 1.3, 1.4-FINAL and
trunk. I thought summarizing what I found might help people decide
whether they want to vote in favor of releasing 1.4-FINAL as is, or
support a release from trunk.
Fixes in 1.4-FINAL branch (that are not present in 1.3-FINAL):
No JIRA issue: Prevent an NPE when curMsg is null
AXIS-2314 - Axis leaking Session objects
AXIS-2267 - incorrect type serialization
AXIS-2232 - mappings in TypeDesc can't be GC'd
AXIS-2013 - deserialization of exception fails
AXIS-2281 - (docs fix)
AXIS-2278 - fix for memory leak caused by JavaUtils.enumMap
AXIS-2264 - org.apache.axis.client.Call implementation Bug =>
CurrentModificationException if an other VM is used (e.g. http://
www.cacaojvm.org)
AXIS-2236 - Bad constructor with derived classes that inherit xs:any
members
Fixes added in trunk:
AXIS-2365 - SOAPDocumentImpl calls MessageElement constructor with
wrong arguments
AXIS-1995 - ServiceLifecycle.destroy() never called
AXIS-2347 - detatching the body of a soap envelope and trying to set
its body with a new soap body results in a DOMException
AXIS-2346 - Issue with the way the localNames are created in WSDL2Java
Notable improvements in trunk:
(no JIRA issue cited) - changes to avoid using enum as a variable name
(no JIRA issue cited) - Add WS-Addr support; looks like the W3C level
is still in progress
(no JIRA issue cited) - Fixed TCK test
(no JIRA issue cited) - use new clover jar
(no JIRA issue cited) - allow non-Axis code to set the current
messagecontext
(no JIRA issue cited) - allow SOAP processors that return 200 instead
of 202
(no JIRA issue cited) - allow services to make operations one-way
(no JIRA issue cited) - more logic for msgProvider method search
(no JIRA issue cited) - turn off XML pretty print by default
(no JIRA issue cited) - various MessageContext logic improvements
(no JIRA issue cited) - allow clients to set the client engine's
config file directly without manually creating a new FileProvider
(no JIRA issue cited) - de/serialization support for messageContext
(no JIRA issue cited) - Sample using XmlBeans serializer/deserializer
I noticed that there didn't seem to be any major improvements in 1.4-
FINAL, only bugfixes. My thought is that since it contains new
features, trunk might need more review before it can be released,
especially since things like WSA support are still in progress and
have checkins from as recently as yesterday. It also looks to me
like most of the important fixes - like the NPE and the memory leaks
- are already in 1.4-FINAL. So I give my +1 for releasing 1.4-FINAL
as it stands as soon as possible since it would help Geronimo, with
the caveat that it might be worth backporting AXIS-1995 since it
looks like a memory leak and the change is fairly minor.
Regards,
Bjorn Townsend
Re: [VOTE] Release Axis 1.4 final branch
Posted by Bjorn Townsend <bj...@sourcelabs.com>.
Hello all,
I'm interested in seeing an official 1.4 release, so I took some time
and looked at the diffs and svn logs between 1.3, 1.4-FINAL and
trunk. I thought summarizing what I found might help people decide
whether they want to vote in favor of releasing 1.4-FINAL as is, or
support a release from trunk.
Fixes in 1.4-FINAL branch (that are not present in 1.3-FINAL):
No JIRA issue: Prevent an NPE when curMsg is null
AXIS-2314 - Axis leaking Session objects
AXIS-2267 - incorrect type serialization
AXIS-2232 - mappings in TypeDesc can't be GC'd
AXIS-2013 - deserialization of exception fails
AXIS-2281 - (docs fix)
AXIS-2278 - fix for memory leak caused by JavaUtils.enumMap
AXIS-2264 - org.apache.axis.client.Call implementation Bug =>
CurrentModificationException if an other VM is used (e.g. http://
www.cacaojvm.org)
AXIS-2236 - Bad constructor with derived classes that inherit xs:any
members
Fixes added in trunk:
AXIS-2365 - SOAPDocumentImpl calls MessageElement constructor with
wrong arguments
AXIS-1995 - ServiceLifecycle.destroy() never called
AXIS-2347 - detatching the body of a soap envelope and trying to set
its body with a new soap body results in a DOMException
AXIS-2346 - Issue with the way the localNames are created in WSDL2Java
Notable improvements in trunk:
(no JIRA issue cited) - changes to avoid using enum as a variable name
(no JIRA issue cited) - Add WS-Addr support; looks like the W3C level
is still in progress
(no JIRA issue cited) - Fixed TCK test
(no JIRA issue cited) - use new clover jar
(no JIRA issue cited) - allow non-Axis code to set the current
messagecontext
(no JIRA issue cited) - allow SOAP processors that return 200 instead
of 202
(no JIRA issue cited) - allow services to make operations one-way
(no JIRA issue cited) - more logic for msgProvider method search
(no JIRA issue cited) - turn off XML pretty print by default
(no JIRA issue cited) - various MessageContext logic improvements
(no JIRA issue cited) - allow clients to set the client engine's
config file directly without manually creating a new FileProvider
(no JIRA issue cited) - de/serialization support for messageContext
(no JIRA issue cited) - Sample using XmlBeans serializer/deserializer
I noticed that there didn't seem to be any major improvements in 1.4-
FINAL, only bugfixes. My thought is that since it contains new
features, trunk might need more review before it can be released,
especially since things like WSA support are still in progress and
have checkins from as recently as yesterday. It also looks to me
like most of the important fixes - like the NPE and the memory leaks
- are already in 1.4-FINAL. So I give my +1 for releasing 1.4-FINAL
as it stands as soon as possible since it would help Geronimo, with
the caveat that it might be worth backporting AXIS-1995 since it
looks like a memory leak and the change is fairly minor.
Regards,
Bjorn Townsend
Re: [VOTE] Release Axis 1.4 final branch
Posted by David Blevins <da...@visi.com>.
On Mar 15, 2006, at 8:38 AM, Sanjiva Weerawarana wrote:
> On Mon, 2006-03-13 at 19:50 -0800, David Blevins wrote:
>> Dims created an Axis 1.4 final branch in early Dec at:
>>
>> http://svn.apache.org/repos/asf/webservices/axis/branches/
>> AXIS_1_4_FINAL
>>
>> There was a vote to release this that went through but the binaries
>> were never produced. Geronimo, Jonas and others are using this code
>> and it would be great to see it made official. I am volunteering as
>> Release Manager and would like to kicked this release out the door
>> before the month is through.
>>
>> Here is my +1 for me as Release Manager and seeing 1.4 released this
>> month.
>
> Isn't it a bit weird to release a branch from December in March? I
> know
> the situation is weird but it feels a bit wrong to me :(.
>
> Or maybe not.
>
Whatever is fine with me. This is where the discussion happened:
Thread 1
http://www.mail-archive.com/axis-dev@ws.apache.org/msg14431.html
Sub-thread 2
http://www.mail-archive.com/axis-dev@ws.apache.org/msg14438.html
Read those and follow up. As I say, I'm fine with whatever as long
as there is any sort of logical reason and people more or less agree.
Thanks,
David
RE: [VOTE] Release Axis 1.4 final branch
Posted by rmkellogg <rm...@comcast.net>.
At least a known distribution would have a name. That would be the only
real advantage. Our next release could be 1.4.1 or something along those
lines.
Rick Kellogg
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
Sent: Wednesday, March 15, 2006 11:38 AM
To: axis-dev@ws.apache.org
Subject: Re: [VOTE] Release Axis 1.4 final branch
On Mon, 2006-03-13 at 19:50 -0800, David Blevins wrote:
> Dims created an Axis 1.4 final branch in early Dec at:
>
> http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
>
> There was a vote to release this that went through but the binaries
> were never produced. Geronimo, Jonas and others are using this code
> and it would be great to see it made official. I am volunteering as
> Release Manager and would like to kicked this release out the door
> before the month is through.
>
> Here is my +1 for me as Release Manager and seeing 1.4 released this
> month.
Isn't it a bit weird to release a branch from December in March? I know
the situation is weird but it feels a bit wrong to me :(.
Or maybe not.
Sanjiva.
Re: [VOTE] Release Axis 1.4 final branch
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Mon, 2006-03-13 at 19:50 -0800, David Blevins wrote:
> Dims created an Axis 1.4 final branch in early Dec at:
>
> http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
>
> There was a vote to release this that went through but the binaries
> were never produced. Geronimo, Jonas and others are using this code
> and it would be great to see it made official. I am volunteering as
> Release Manager and would like to kicked this release out the door
> before the month is through.
>
> Here is my +1 for me as Release Manager and seeing 1.4 released this
> month.
Isn't it a bit weird to release a branch from December in March? I know
the situation is weird but it feels a bit wrong to me :(.
Or maybe not.
Sanjiva.
Re: [VOTE] Release Axis 1.4 final branch
Posted by David Blevins <da...@visi.com>.
Excellent.
I'll hook up with you on IRC and see what else we need to do to
button this up.
Thanks,
David
On Apr 21, 2006, at 8:01 AM, Davanum Srinivas wrote:
> David,
>
> I've just run the saaj tck and jaxrpc tck (both standalone) on the
> branch mentioned below. All Green.
>
> Thanks,
> dims
>
> On 3/13/06, David Blevins <da...@visi.com> wrote:
>> Dims created an Axis 1.4 final branch in early Dec at:
>>
>> http://svn.apache.org/repos/asf/webservices/axis/branches/
>> AXIS_1_4_FINAL
>>
>> There was a vote to release this that went through but the binaries
>> were never produced. Geronimo, Jonas and others are using this code
>> and it would be great to see it made official. I am volunteering as
>> Release Manager and would like to kicked this release out the door
>> before the month is through.
>>
>> Here is my +1 for me as Release Manager and seeing 1.4 released this
>> month.
>>
>> -David
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
Re: [VOTE] Release Axis 1.4 final branch
Posted by Davanum Srinivas <da...@gmail.com>.
David,
I've just run the saaj tck and jaxrpc tck (both standalone) on the
branch mentioned below. All Green.
Thanks,
dims
On 3/13/06, David Blevins <da...@visi.com> wrote:
> Dims created an Axis 1.4 final branch in early Dec at:
>
> http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
>
> There was a vote to release this that went through but the binaries
> were never produced. Geronimo, Jonas and others are using this code
> and it would be great to see it made official. I am volunteering as
> Release Manager and would like to kicked this release out the door
> before the month is through.
>
> Here is my +1 for me as Release Manager and seeing 1.4 released this
> month.
>
> -David
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [VOTE] Release Axis 1.4 final branch
Posted by Guillaume Sauthier <Gu...@objectweb.org>.
Here is my +1
Guillaume
David Blevins wrote:
> Dims created an Axis 1.4 final branch in early Dec at:
>
> http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
>
> There was a vote to release this that went through but the binaries
> were never produced. Geronimo, Jonas and others are using this code
> and it would be great to see it made official. I am volunteering as
> Release Manager and would like to kicked this release out the door
> before the month is through.
>
> Here is my +1 for me as Release Manager and seeing 1.4 released this
> month.
>
> -David
>
>
Re: [VOTE] Release Axis 1.4 final branch
Posted by Davanum Srinivas <da...@gmail.com>.
David,
I've just run the saaj tck and jaxrpc tck (both standalone) on the
branch mentioned below. All Green.
Thanks,
dims
On 3/13/06, David Blevins <da...@visi.com> wrote:
> Dims created an Axis 1.4 final branch in early Dec at:
>
> http://svn.apache.org/repos/asf/webservices/axis/branches/AXIS_1_4_FINAL
>
> There was a vote to release this that went through but the binaries
> were never produced. Geronimo, Jonas and others are using this code
> and it would be great to see it made official. I am volunteering as
> Release Manager and would like to kicked this release out the door
> before the month is through.
>
> Here is my +1 for me as Release Manager and seeing 1.4 released this
> month.
>
> -David
>
>
--
Davanum Srinivas : http://wso2.com/blogs/