You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Tony Opatha <to...@yahoo.com> on 2003/12/24 21:25:13 UTC
AXIS 1.2 Release Plan (Was: RE: Moving toward Axis 1.2 beta and release)
I think it is extremely important that we release:
0) AXIS 1.2 Beta by early Jan. '04
1) AXIS 1.2 Final Release by mid-Jan. '04
2) AXIS 1.3 Release by mid-Feb to mid-March '04
AXIS 1.2 should be bug-fix release of AXIS 1.1 such that we have minimal code changes in AXIS 1.1-based web services applications and clients.
AXIS 1.3 should be a WS-I BP 1.0 conformant release. The sooner we can get a beta and/or alpha version of AXIS 1.3 with BP enhancements it would be useful for the AXIS dev community to test with other WS-I BP 1.0 conforming run-times. If there are some known bug-fixes that will help in AXIS 1.3 BP 1.0 conformance, I would recommend that they be included in AXIS 1.2.
These dates seem to echo the discussions in attached e-mail.
Hence, may we get some clarification from AXIS 1.2 release coordinator that we can stick to above dates?
Is there an AXIS 1.2 Beta distribution currently available? The earlier we get that, the easier it will be to test it to confirm its stability.
Thanks.
-----Original Message-----
From: Davanum Srinivas [mailto:dims@yahoo.com]
Sent: Wednesday, December 17, 2003 3:19 AM
To: axis-dev@ws.apache.org
Subject: Re: Moving toward Axis 1.2 beta and release
At the end of the day, it's Glen's call as the Release Manager. Am +1 to 1.2 Mid Jan and 1.3 soon
after with BP. Right now the major crunch is running the TCK's.
thanks,
dims
--- Glen Daniels <gl...@thoughtcraft.com> wrote:
> To tell you the truth, I would prefer that we didn't delay the release.
>
> "Bug fixes" in the 1.2 case include vastly improved document/literal
> support, way faster WSDL processing, more logical type handling, support for
> Servlet 2.3 and session lifecycle events, cleaner code with better JavaDoc
> and fewer dead lines.... and that's not even all. Seems like enough for a
> release to me.
>
> I am very concerned tha
t if we hold off we will get into a long cycle of
> delays (as has happened before) which will hold this up until March or
> April, and I'd frankly rather move towards releases earlier and more often
> until we get the bug count down at least into the double digits.
>
> So I'm not in any way against working on all this stuff (and more besides),
> but I'd like to get 1.2 out in mid-January as planned, and I'd be more than
> happy with a BP-compliant 1.3 in March or so.
>
> --Glen
>
> ----- Original Message -----
> From: "Tom Jordahl" <to...@macromedia.com>
> To: <ax...@ws.apache.org>
> Sent: Tuesday, December 16, 2003 4:14 PM
> Subject: RE: Moving toward Axis 1.2 beta and release
>
>
> >
> > In talking with folks around here, we would be in favor of delaying the
> 1.2
> > release until we can claim WS-I Basic Profile 1.0 conformance. Macromedia
> > would be willing to help out with testing resources for this effort.
> >
> > It will be late January before there are resources here to run the TCK,
> and
> > we would very much like to get BP 1.0 as a feature of the 1.2 release.
> >
> > The question I was asked is "What does 1.2 give me?" "Bug fixes" wasn't
> > thought to be very compelling, while "WS-I BP 1.0 conformance" is
> something
> > that gets a much better reaction.
> >
> > What do you think?
> >
> > --
> > Tom Jordahl
> > Macromedia Server Development
> >
> > -----Original Message-----
> > From: Tom Jordahl [mailto:tomj@macromedia.com]
> > Sent: Tuesday, December 16, 2003 10:28 AM
> > To: 'axis-dev@ws.apache.org'
> > Subject: Moving toward Axis 1.2 beta and release
> >
> >
> > Here is a proposal (discussed with Dims) about how Axis 1.2 should proceed
> > to move toward a 1.2 release.
> >
> > - Create Axis 1.2 beta in the next 3 weeks
> > - After beta, run the JAX-RPC/SAAJ TCK 1.1 and resolve failures
> > - After we pass the TCK, we release 1.2
> >
> > I am trying to get commitments from our teams here to run our JRun and
> > ColdFusion regressions on the current 1.2 bits. And I will attempt to get
> > resources to execute the TCKs (on JRun) here as well.
> >
> > Comments?
> >
> > Can anyone else run the TCK at their organization?
> >
> > --
> > Tom Jordahl
> > Macromedia Server Development
> >
> >
---------------------------------
Do you Yahoo!?
Yahoo! Photos - Get your photo on the big screen in Times Square
Re: AXIS 1.2 Release Plan (Was: RE: Moving toward Axis 1.2 beta and
release)
Posted by Steve Loughran <st...@iseran.com>.
Tony Opatha wrote:
> I think it is extremely important that we release:
>
> 0) AXIS 1.2 Beta by early Jan. '04
>
> 1) AXIS 1.2 Final Release by mid-Jan. '04
two weeks from beta to final release? That is not enough time to get
complete feedback from users. We could target beta-1 in early jan,
beta-2 mid jan with final following, but that is glen's call.
>
> 2) AXIS 1.3 Release by mid-Feb to mid-March '04
>
> AXIS 1.2 should be bug-fix release of AXIS 1.1 such that we have minimal
> code changes in AXIS 1.1-based web services applications and clients.
>
> AXIS 1.3 should be a WS-I BP 1.0 conformant release. The sooner we can
> get a beta and/or alpha version of AXIS 1.3 with BP enhancements it
> would be useful for the AXIS dev community to test with other WS-I BP
> 1.0 conforming run-times. If there are some known bug-fixes that will
> help in AXIS 1.3 BP 1.0 conformance, I would recommend that they be
> included in AXIS 1.2.
I see where you are heading: fixes in 1.2; features in 1.3. I also
suspect that while 1.2 is in beta, the 1.3/CVS_HEAD branch will remain
fairly quiet, as most engineering effort will focus on the product, it
is only anyone who is working on new features that will touch 1.3.
Indeed, it is nice when the two branches stay close, as it makes
synchronising branches easier.
>
> These dates seem to echo the discussions in attached e-mail.
>
> Hence, may we get some clarification from AXIS 1.2 release coordinator
> that we can stick to above dates?
Remember, in open source there is no marketing mandated release
deadline. And most of the people who work on this do it in their spare
time. If you want Axis to ship early, you need to help.
> Is there an AXIS 1.2 Beta distribution currently available? The earlier
> we get that, the easier it will be to test it to confirm its stability.
>
You need to pull down the CVS builds and do nightly builds if you really
want to test thoroughly; it is the key to catching changes and notifying
the team before anything ships. Then file bugreps with reproducible tests.
-steve
Re: AXIS 1.2 Release Plan (Was: RE: Moving toward Axis 1.2 beta and release)
Posted by Davanum Srinivas <di...@yahoo.com>.
Question: Are u willing to pitch in to help? If so, please review existing bugs in bugzilla and
upload patches. The more folks pitching in, the quicker we can get out releases.
thanks,
dims
--- Tony Opatha <to...@yahoo.com> wrote:
>
> I think it is extremely important that we release:
>
> 0) AXIS 1.2 Beta by early Jan. '04
>
> 1) AXIS 1.2 Final Release by mid-Jan. '04
>
> 2) AXIS 1.3 Release by mid-Feb to mid-March '04
>
> AXIS 1.2 should be bug-fix release of AXIS 1.1 such that we have minimal code changes in AXIS
> 1.1-based web services applications and clients.
>
> AXIS 1.3 should be a WS-I BP 1.0 conformant release. The sooner we can get a beta and/or alpha
> version of AXIS 1.3 with BP enhancements it would be useful for the AXIS dev community to test
> with other WS-I BP 1.0 conforming run-times. If there are some known bug-fixes that will help in
> AXIS 1.3 BP 1.0 conformance, I would recommend that they be included in AXIS 1.2.
>
> These dates seem to echo the discussions in attached e-mail.
>
> Hence, may we get some clarification from AXIS 1.2 release coordinator that we can stick to
> above dates?
>
> Is there an AXIS 1.2 Beta distribution currently available? The earlier we get that, the easier
> it will be to test it to confirm its stability.
>
> Thanks.
>
>
>
>
>
> -----Original Message-----
>
> From: Davanum Srinivas [mailto:dims@yahoo.com]
>
> Sent: Wednesday, December 17, 2003 3:19 AM
>
> To: axis-dev@ws.apache.org
>
> Subject: Re: Moving toward Axis 1.2 beta and release
>
>
>
> At the end of the day, it's Glen's call as the Release Manager. Am +1 to 1.2 Mid Jan and 1.3
> soon
>
> after with BP. Right now the major crunch is running the TCK's.
>
> thanks,
>
> dims
>
> --- Glen Daniels <gl...@thoughtcraft.com> wrote:
>
> > To tell you the truth, I would prefer that we didn't delay the release.
>
> >
>
> > "Bug fixes" in the 1.2 case include vastly improved document/literal
>
> > support, way faster WSDL processing, more logical type handling, support for
>
> > Servlet 2.3 and session lifecycle events, cleaner code with better JavaDoc
>
> > and fewer dead lines.... and that's not even all. Seems like enough for a
>
> > release to me.
>
> >
>
> > I am very concerned tha
>
>
> t if we hold off we will get into a long cycle of
>
> > delays (as has happened before) which will hold this up until March or
>
> > April, and I'd frankly rather move towards releases earlier and more often
>
> > until we get the bug count down at least into the double digits.
>
> >
>
> > So I'm not in any way against working on all this stuff (and more besides),
>
> > but I'd like to get 1.2 out in mid-January as planned, and I'd be more than
>
> > happy with a BP-compliant 1.3 in March or so.
>
> >
>
> > --Glen
>
> >
>
> > ----- Original Message -----
>
> > From: "Tom Jordahl" <to...@macromedia.com>
>
> > To: <ax...@ws.apache.org>
>
> > Sent: Tuesday, December 16, 2003 4:14 PM
>
> > Subject: RE: Moving toward Axis 1.2 beta and release
>
> >
>
> >
>
> > >
>
> > > In talking with folks around here, we would be in favor of delaying the
>
> > 1.2
>
> > > release until we can claim WS-I Basic Profile 1.0 conformance. Macromedia
>
> > > would be willing to help out with testing resources for this effort.
>
> > >
>
> > > It will be late January before there are resources here to run the TCK,
>
> > and
>
> > > we would very much like to get BP 1.0 as a feature of the 1.2 release.
>
> > >
>
> > > The question I was asked is "What does 1.2 give me?" "Bug fixes" wasn't
>
> > > thought to be very compelling, while "WS-I BP 1.0 conformance" is
>
> > something
>
> > > that gets a much better reaction.
>
> > >
>
> > > What do you think?
>
> > >
>
> > > --
>
> > > Tom Jordahl
>
> > > Macromedia Server Development
>
> > >
>
> > > -----Original Message-----
>
> > > From: Tom Jordahl [mailto:tomj@macromedia.com]
>
> > > Sent: Tuesday, December 16, 2003 10:28 AM
>
> > > To: 'axis-dev@ws.apache.org'
>
> > > Subject: Moving toward Axis 1.2 beta and release
>
> > >
>
> > >
>
> > > Here is a proposal (discussed with Dims) about how Axis 1.2 should proceed
>
> > > to move toward a 1.2 release.
>
> > >
>
> > > - Create Axis 1.2 beta in the next 3 weeks
>
> > > - After beta, run the JAX-RPC/SAAJ TCK 1.1 and resolve failures
>
> > > - After we pass the TCK, we release 1.2
>
> > >
>
> > > I am trying to get commitments from our teams here to run our JRun and
>
> > > ColdFusion regressions on the current 1.2 bits. And I will attempt to get
>
> > > resources to execute the TCKs (on JRun) here as well.
>
> > >
>
> > > Comments?
>
> > >
>
> > > Can anyone else run the TCK at their organization?
>
> > >
>
> > > --
>
> > > Tom Jordahl
>
> > > Macromedia Server Development
>
>
=== message truncated ===
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: AXIS 1.2 Release Plan (Was: RE: Moving toward Axis 1.2 beta and release)
Posted by Davanum Srinivas <di...@yahoo.com>.
Question: Are u willing to pitch in to help? If so, please review existing bugs in bugzilla and
upload patches. The more folks pitching in, the quicker we can get out releases.
thanks,
dims
--- Tony Opatha <to...@yahoo.com> wrote:
>
> I think it is extremely important that we release:
>
> 0) AXIS 1.2 Beta by early Jan. '04
>
> 1) AXIS 1.2 Final Release by mid-Jan. '04
>
> 2) AXIS 1.3 Release by mid-Feb to mid-March '04
>
> AXIS 1.2 should be bug-fix release of AXIS 1.1 such that we have minimal code changes in AXIS
> 1.1-based web services applications and clients.
>
> AXIS 1.3 should be a WS-I BP 1.0 conformant release. The sooner we can get a beta and/or alpha
> version of AXIS 1.3 with BP enhancements it would be useful for the AXIS dev community to test
> with other WS-I BP 1.0 conforming run-times. If there are some known bug-fixes that will help in
> AXIS 1.3 BP 1.0 conformance, I would recommend that they be included in AXIS 1.2.
>
> These dates seem to echo the discussions in attached e-mail.
>
> Hence, may we get some clarification from AXIS 1.2 release coordinator that we can stick to
> above dates?
>
> Is there an AXIS 1.2 Beta distribution currently available? The earlier we get that, the easier
> it will be to test it to confirm its stability.
>
> Thanks.
>
>
>
>
>
> -----Original Message-----
>
> From: Davanum Srinivas [mailto:dims@yahoo.com]
>
> Sent: Wednesday, December 17, 2003 3:19 AM
>
> To: axis-dev@ws.apache.org
>
> Subject: Re: Moving toward Axis 1.2 beta and release
>
>
>
> At the end of the day, it's Glen's call as the Release Manager. Am +1 to 1.2 Mid Jan and 1.3
> soon
>
> after with BP. Right now the major crunch is running the TCK's.
>
> thanks,
>
> dims
>
> --- Glen Daniels <gl...@thoughtcraft.com> wrote:
>
> > To tell you the truth, I would prefer that we didn't delay the release.
>
> >
>
> > "Bug fixes" in the 1.2 case include vastly improved document/literal
>
> > support, way faster WSDL processing, more logical type handling, support for
>
> > Servlet 2.3 and session lifecycle events, cleaner code with better JavaDoc
>
> > and fewer dead lines.... and that's not even all. Seems like enough for a
>
> > release to me.
>
> >
>
> > I am very concerned tha
>
>
> t if we hold off we will get into a long cycle of
>
> > delays (as has happened before) which will hold this up until March or
>
> > April, and I'd frankly rather move towards releases earlier and more often
>
> > until we get the bug count down at least into the double digits.
>
> >
>
> > So I'm not in any way against working on all this stuff (and more besides),
>
> > but I'd like to get 1.2 out in mid-January as planned, and I'd be more than
>
> > happy with a BP-compliant 1.3 in March or so.
>
> >
>
> > --Glen
>
> >
>
> > ----- Original Message -----
>
> > From: "Tom Jordahl" <to...@macromedia.com>
>
> > To: <ax...@ws.apache.org>
>
> > Sent: Tuesday, December 16, 2003 4:14 PM
>
> > Subject: RE: Moving toward Axis 1.2 beta and release
>
> >
>
> >
>
> > >
>
> > > In talking with folks around here, we would be in favor of delaying the
>
> > 1.2
>
> > > release until we can claim WS-I Basic Profile 1.0 conformance. Macromedia
>
> > > would be willing to help out with testing resources for this effort.
>
> > >
>
> > > It will be late January before there are resources here to run the TCK,
>
> > and
>
> > > we would very much like to get BP 1.0 as a feature of the 1.2 release.
>
> > >
>
> > > The question I was asked is "What does 1.2 give me?" "Bug fixes" wasn't
>
> > > thought to be very compelling, while "WS-I BP 1.0 conformance" is
>
> > something
>
> > > that gets a much better reaction.
>
> > >
>
> > > What do you think?
>
> > >
>
> > > --
>
> > > Tom Jordahl
>
> > > Macromedia Server Development
>
> > >
>
> > > -----Original Message-----
>
> > > From: Tom Jordahl [mailto:tomj@macromedia.com]
>
> > > Sent: Tuesday, December 16, 2003 10:28 AM
>
> > > To: 'axis-dev@ws.apache.org'
>
> > > Subject: Moving toward Axis 1.2 beta and release
>
> > >
>
> > >
>
> > > Here is a proposal (discussed with Dims) about how Axis 1.2 should proceed
>
> > > to move toward a 1.2 release.
>
> > >
>
> > > - Create Axis 1.2 beta in the next 3 weeks
>
> > > - After beta, run the JAX-RPC/SAAJ TCK 1.1 and resolve failures
>
> > > - After we pass the TCK, we release 1.2
>
> > >
>
> > > I am trying to get commitments from our teams here to run our JRun and
>
> > > ColdFusion regressions on the current 1.2 bits. And I will attempt to get
>
> > > resources to execute the TCKs (on JRun) here as well.
>
> > >
>
> > > Comments?
>
> > >
>
> > > Can anyone else run the TCK at their organization?
>
> > >
>
> > > --
>
> > > Tom Jordahl
>
> > > Macromedia Server Development
>
>
=== message truncated ===
=====
Davanum Srinivas - http://webservices.apache.org/~dims/