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 Deepal Jayasinghe <de...@opensource.lk> on 2006/03/20 12:48:53 UTC
[Axis2] Release plan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all;
As you all know Axis2 has been around for about two years and we are
still patiently waiting for the magical 1.0. As far as I can see Axis2
is feature complete and it seems to me that the time has come to
seriously consider the 1.0 release.
I had to postpone 0.95 release due to few blockers and I hope that we
will be able to fix those soon and will be able to release 0.95 before
the end of this week.
And there are few dependencies and tasks that need to be fulfilled
before we declare 1.0
1.The list dims suggested
(http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0)
2.AXIOM release , I think its better if we can do Axis2 1.0 with
AXIOM release rather than SNAPSHOT
3.JIRA fixing
4.code clean up
5.I18n
There is a number of JIRAs on code generation and ADB and I think it
is better if we can fix them after 0.95. We will need to do another
quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that
boils down to the following release plan,
1.Axis2 0.95 in this week (20-25)
2.Axis2 0.96 first week of the April
3.If we dont find any major issues then we mark 0.96 as Axis2 1.0
Comments and suggestions are warmly welcome !!!!
- --
Thanks,
Deepal
................................................................
~Future is Open~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+
g9YUcE97iKPFKXcjVC7xT8E=
=MIjV
-----END PGP SIGNATURE-----
Re: [Axis2] Release plan
Posted by Steve Loughran <st...@apache.org>.
Ajith Ranabahu wrote:
> Hi Steve,
> I know the exact problem and we are planning to address it. We have
> already planned the major components (such as axiom and policy) to be
> released before the 1.0. These components are fairly stable and can be
> released without a problem.
> So it's going to be based on some standard versions rather than snapshots
>
that's great!
Re: [Axis2] Release plan
Posted by Franz Fehringer <fe...@isogmbh.de>.
Where do i find the Maven 1.1 release?
On maven.apache.org i only see Maven 1.1 Beta 2?
And will the Axis2 build be based on Maven 2? 8-)
Greetings
Franz
Eran Chinthaka schrieb:
> What is the dependency we have on maven snapshots ? ;-)
> And maven released 1.1 and even 2.0 long time back.
>
> Franz Fehringer wrote:
>> Perhaps the Maven folks could be triggered for a 1.1 release also?
>>
>> regards
>>
>> Franz
>>
>> Ajith Ranabahu schrieb:
>>> Hi Steve,
>>> I know the exact problem and we are planning to address it. We have
>>> already planned the major components (such as axiom and policy) to be
>>> released before the 1.0. These components are fairly stable and can be
>>> released without a problem.
>>> So it's going to be based on some standard versions rather than
>>> snapshots
>>>
>>> Ajith
>>>
>>> On 3/22/06, Steve Loughran <st...@apache.org> wrote:
>>>
>>>> Sanjiva Weerawarana wrote:
>>>>
>>>> OK. The other thing is that you can't do a release that depend on
>>>> -SNAPSHOT versions of things.
>>>>
>>>> Because doing so makes it impossible for anyone to ever recreate your
>>>> initial state once the stuff in the maven scratch repositories changes
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Ajith Ranabahu
>>>
>>>
>>>
>>
>
Re: [Axis2] Release plan
Posted by Steve Loughran <st...@apache.org>.
Eran Chinthaka wrote:
> What is the dependency we have on maven snapshots ? ;-)
> And maven released 1.1 and even 2.0 long time back.
I updated the dependency settings last week to the main releases of stuff.
one funny is that there is an XmlSchema1.0 in the m2 repository, but not
the maven1 one; somebody needs to push for that.
Re: [Axis2] Release plan
Posted by Eran Chinthaka <ch...@opensource.lk>.
What is the dependency we have on maven snapshots ? ;-)
And maven released 1.1 and even 2.0 long time back.
Franz Fehringer wrote:
> Perhaps the Maven folks could be triggered for a 1.1 release also?
>
> regards
>
> Franz
>
> Ajith Ranabahu schrieb:
>> Hi Steve,
>> I know the exact problem and we are planning to address it. We have
>> already planned the major components (such as axiom and policy) to be
>> released before the 1.0. These components are fairly stable and can be
>> released without a problem.
>> So it's going to be based on some standard versions rather than snapshots
>>
>> Ajith
>>
>> On 3/22/06, Steve Loughran <st...@apache.org> wrote:
>>
>>> Sanjiva Weerawarana wrote:
>>>
>>> OK. The other thing is that you can't do a release that depend on
>>> -SNAPSHOT versions of things.
>>>
>>> Because doing so makes it impossible for anyone to ever recreate your
>>> initial state once the stuff in the maven scratch repositories changes
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Ajith Ranabahu
>>
>>
>>
>
Re: [Axis2] Release plan
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi Steve,
I know the exact problem and we are planning to address it. We have
already planned the major components (such as axiom and policy) to be
released before the 1.0. These components are fairly stable and can be
released without a problem.
So it's going to be based on some standard versions rather than snapshots
Ajith
On 3/22/06, Steve Loughran <st...@apache.org> wrote:
> Sanjiva Weerawarana wrote:
>
> OK. The other thing is that you can't do a release that depend on
> -SNAPSHOT versions of things.
>
> Because doing so makes it impossible for anyone to ever recreate your
> initial state once the stuff in the maven scratch repositories changes
>
>
>
--
Ajith Ranabahu
Re: [Axis2] Release plan
Posted by Steve Loughran <st...@apache.org>.
Sanjiva Weerawarana wrote:
> On Tue, 2006-03-21 at 21:55 +0000, Steve Loughran wrote:
>> One caveat. Once you get to 1.0, you are making some promise of stability.
>>
>> I am still trying to get code that worked with 0.93 working on 0.95
>> snapshot, it looks like the dynamic classloading stuff is using the
>> wrong classloader. that's the price of being bleeding edge, and once I
>> check in the extra diagnostics everyone will benefit.
>>
>> But once you go to 1.0, you are committing to keep things stable, both
>> in signature and semantics, or risk alienating a larger audience.
>
> Absolutely +1 Steve. Once we go to 1.0, the externally visible parts are
> frozen .. all we can do is improve/add and possibly deprecate if a big
> problem has been found.
>
> I'm personally confident we're ready to go there.
>
> Sanjiva.
>
OK. The other thing is that you can't do a release that depend on
-SNAPSHOT versions of things.
Because doing so makes it impossible for anyone to ever recreate your
initial state once the stuff in the maven scratch repositories changes
Re: [Axis2] Release plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Tue, 2006-03-21 at 21:55 +0000, Steve Loughran wrote:
> One caveat. Once you get to 1.0, you are making some promise of stability.
>
> I am still trying to get code that worked with 0.93 working on 0.95
> snapshot, it looks like the dynamic classloading stuff is using the
> wrong classloader. that's the price of being bleeding edge, and once I
> check in the extra diagnostics everyone will benefit.
>
> But once you go to 1.0, you are committing to keep things stable, both
> in signature and semantics, or risk alienating a larger audience.
Absolutely +1 Steve. Once we go to 1.0, the externally visible parts are
frozen .. all we can do is improve/add and possibly deprecate if a big
problem has been found.
I'm personally confident we're ready to go there.
Sanjiva.
Re: [Axis2] Release plan
Posted by Steve Loughran <st...@apache.org>.
Sanjiva Weerawarana wrote:
> Most definitely +1! Axis2 is now ready for prime time .. and we need
> much wider user feedback to make it move to the next level. We won't get
> that until we release 1.0.
>
> I propose we change 0.96 below to the label 1.0RC to signal to everyone
> that this is our planned 1.0 release. That will get more attention IMO.
>
> Sanjiva.
One caveat. Once you get to 1.0, you are making some promise of stability.
I am still trying to get code that worked with 0.93 working on 0.95
snapshot, it looks like the dynamic classloading stuff is using the
wrong classloader. that's the price of being bleeding edge, and once I
check in the extra diagnostics everyone will benefit.
But once you go to 1.0, you are committing to keep things stable, both
in signature and semantics, or risk alienating a larger audience.
-steve
Re: [Axis2] Release plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Most definitely +1! Axis2 is now ready for prime time .. and we need
much wider user feedback to make it move to the next level. We won't get
that until we release 1.0.
I propose we change 0.96 below to the label 1.0RC to signal to everyone
that this is our planned 1.0 release. That will get more attention IMO.
Sanjiva.
On Mon, 2006-03-20 at 17:48 +0600, Deepal Jayasinghe wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all;
>
> As you all know Axis2 has been around for about two years and we are
> still patiently waiting for the magical 1.0. As far as I can see Axis2
> is feature complete and it seems to me that the time has come to
> seriously consider the 1.0 release.
>
> I had to postpone 0.95 release due to few blockers and I hope that we
> will be able to fix those soon and will be able to release 0.95 before
> the end of this week.
>
> And there are few dependencies and tasks that need to be fulfilled
> before we declare 1.0
> 1.The list dims suggested
> (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0)
> 2.AXIOM release , I think its better if we can do Axis2 1.0 with
> AXIOM release rather than SNAPSHOT
> 3.JIRA fixing
> 4.code clean up
> 5.I18n
>
> There is a number of JIRAs on code generation and ADB and I think it
> is better if we can fix them after 0.95. We will need to do another
> quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that
> boils down to the following release plan,
> 1.Axis2 0.95 in this week (20-25)
> 2.Axis2 0.96 first week of the April
> 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0
>
> Comments and suggestions are warmly welcome !!!!
>
> - --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+
> g9YUcE97iKPFKXcjVC7xT8E=
> =MIjV
> -----END PGP SIGNATURE-----
>
>
Re: [Axis2] Release plan
Posted by Ajith Ranabahu <aj...@gmail.com>.
Ok I volunteer to do it :)
On 3/21/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> On Mon, 2006-03-20 at 13:57 +0100, Franz Fehringer wrote:
> > Will the TCP monitor be factored out (-> ws-commons) in release 1.0?
>
> This is an excellent idea. However, can someone offer to do the work?
> Its not a huge amount but it does require refactoring the code to change
> Java package names etc..
>
> Sanjiva.
>
>
--
Ajith Ranabahu
Re: [Axis2] Release plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Mon, 2006-03-20 at 13:57 +0100, Franz Fehringer wrote:
> Will the TCP monitor be factored out (-> ws-commons) in release 1.0?
This is an excellent idea. However, can someone offer to do the work?
Its not a huge amount but it does require refactoring the code to change
Java package names etc..
Sanjiva.
Re: [Axis2] Release plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Mon, 2006-03-20 at 13:57 +0100, Franz Fehringer wrote:
> Will the TCP monitor be factored out (-> ws-commons) in release 1.0?
This is an excellent idea. However, can someone offer to do the work?
Its not a huge amount but it does require refactoring the code to change
Java package names etc..
Sanjiva.
Re: [Axis2] Release plan
Posted by Franz Fehringer <fe...@isogmbh.de>.
Will the TCP monitor be factored out (-> ws-commons) in release 1.0?
Greetings
Franz
Deepal Jayasinghe schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all;
>
> As you all know Axis2 has been around for about two years and we are
> still patiently waiting for the magical 1.0. As far as I can see Axis2
> is feature complete and it seems to me that the time has come to
> seriously consider the 1.0 release.
>
> I had to postpone 0.95 release due to few blockers and I hope that we
> will be able to fix those soon and will be able to release 0.95 before
> the end of this week.
>
> And there are few dependencies and tasks that need to be fulfilled
> before we declare 1.0
> 1.The list dims suggested
> (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0)
> 2.AXIOM release , I think its better if we can do Axis2 1.0 with
> AXIOM release rather than SNAPSHOT
> 3.JIRA fixing
> 4.code clean up
> 5.I18n
>
> There is a number of JIRAs on code generation and ADB and I think it
> is better if we can fix them after 0.95. We will need to do another
> quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that
> boils down to the following release plan,
> 1.Axis2 0.95 in this week (20-25)
> 2.Axis2 0.96 first week of the April
> 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0
>
> Comments and suggestions are warmly welcome !!!!
>
> - --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+
> g9YUcE97iKPFKXcjVC7xT8E=
> =MIjV
> -----END PGP SIGNATURE-----
>
>
>
Re: [Axis2] Release plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Most definitely +1! Axis2 is now ready for prime time .. and we need
much wider user feedback to make it move to the next level. We won't get
that until we release 1.0.
I propose we change 0.96 below to the label 1.0RC to signal to everyone
that this is our planned 1.0 release. That will get more attention IMO.
Sanjiva.
On Mon, 2006-03-20 at 17:48 +0600, Deepal Jayasinghe wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all;
>
> As you all know Axis2 has been around for about two years and we are
> still patiently waiting for the magical 1.0. As far as I can see Axis2
> is feature complete and it seems to me that the time has come to
> seriously consider the 1.0 release.
>
> I had to postpone 0.95 release due to few blockers and I hope that we
> will be able to fix those soon and will be able to release 0.95 before
> the end of this week.
>
> And there are few dependencies and tasks that need to be fulfilled
> before we declare 1.0
> 1.The list dims suggested
> (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0)
> 2.AXIOM release , I think its better if we can do Axis2 1.0 with
> AXIOM release rather than SNAPSHOT
> 3.JIRA fixing
> 4.code clean up
> 5.I18n
>
> There is a number of JIRAs on code generation and ADB and I think it
> is better if we can fix them after 0.95. We will need to do another
> quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that
> boils down to the following release plan,
> 1.Axis2 0.95 in this week (20-25)
> 2.Axis2 0.96 first week of the April
> 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0
>
> Comments and suggestions are warmly welcome !!!!
>
> - --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+
> g9YUcE97iKPFKXcjVC7xT8E=
> =MIjV
> -----END PGP SIGNATURE-----
>
>
Re: [Axis2] Release plan
Posted by Franz Fehringer <fe...@isogmbh.de>.
Will the TCP monitor be factored out (-> ws-commons) in release 1.0?
Greetings
Franz
Deepal Jayasinghe schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all;
>
> As you all know Axis2 has been around for about two years and we are
> still patiently waiting for the magical 1.0. As far as I can see Axis2
> is feature complete and it seems to me that the time has come to
> seriously consider the 1.0 release.
>
> I had to postpone 0.95 release due to few blockers and I hope that we
> will be able to fix those soon and will be able to release 0.95 before
> the end of this week.
>
> And there are few dependencies and tasks that need to be fulfilled
> before we declare 1.0
> 1.The list dims suggested
> (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0)
> 2.AXIOM release , I think its better if we can do Axis2 1.0 with
> AXIOM release rather than SNAPSHOT
> 3.JIRA fixing
> 4.code clean up
> 5.I18n
>
> There is a number of JIRAs on code generation and ADB and I think it
> is better if we can fix them after 0.95. We will need to do another
> quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that
> boils down to the following release plan,
> 1.Axis2 0.95 in this week (20-25)
> 2.Axis2 0.96 first week of the April
> 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0
>
> Comments and suggestions are warmly welcome !!!!
>
> - --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+
> g9YUcE97iKPFKXcjVC7xT8E=
> =MIjV
> -----END PGP SIGNATURE-----
>
>
>
Re: [Axis2] Release plan
Posted by Anthony Elder <an...@uk.ibm.com>.
Ok thanks. Actually its fine if it doesn't get in 0.95 if I know it will
get in later. I've created a new JIRA, AXIS2-507, so its not forgotten.
...ant
Sanjiva Weerawarana <sa...@opensource.lk> on 21/03/2006 01:40:47
Please respond to axis-dev@ws.apache.org
To: axis-dev@ws.apache.org
cc:
Subject: Re: [Axis2] Release plan
On Mon, 2006-03-20 at 12:42 +0000, Anthony Elder wrote:
> Could a createClientSideAxisService method be added to AxisService that
> uses a WSDL Definition object for 0.95?
>
> See:
>
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200603.mbox/%3cOF68F5FB94.1B30D7D1-ON80257135.00382A59-80257135.003
> C4493@uk.ibm.com%3e
I'm not sure whether its too late for 0.95 now but absolutely +1 for
going forward. Anyway if possilbe let's do it immediately; its a fairly
trivial case!
Sanjiva.
Re: [Axis2] Release plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Mon, 2006-03-20 at 12:42 +0000, Anthony Elder wrote:
> Could a createClientSideAxisService method be added to AxisService that
> uses a WSDL Definition object for 0.95?
>
> See:
> http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200603.mbox/%3cOF68F5FB94.1B30D7D1-ON80257135.00382A59-80257135.003
> C4493@uk.ibm.com%3e
I'm not sure whether its too late for 0.95 now but absolutely +1 for
going forward. Anyway if possilbe let's do it immediately; its a fairly
trivial case!
Sanjiva.
Re: [Axis2] Release plan
Posted by Anthony Elder <an...@uk.ibm.com>.
Could a createClientSideAxisService method be added to AxisService that
uses a WSDL Definition object for 0.95?
See:
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200603.mbox/%3cOF68F5FB94.1B30D7D1-ON80257135.00382A59-80257135.003
C4493@uk.ibm.com%3e
...ant
Deepal Jayasinghe <de...@opensource.lk> on 20/03/2006 11:48:53
Please respond to axis-dev@ws.apache.org
To: "axis-dev@ws.apache.org" <ax...@ws.apache.org>,
"axis-user@ws.apache.org" <ax...@ws.apache.org>
cc:
Subject: [Axis2] Release plan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all;
As you all know Axis2 has been around for about two years and we are
still patiently waiting for the magical 1.0. As far as I can see Axis2
is feature complete and it seems to me that the time has come to
seriously consider the 1.0 release.
I had to postpone 0.95 release due to few blockers and I hope that we
will be able to fix those soon and will be able to release 0.95 before
the end of this week.
And there are few dependencies and tasks that need to be fulfilled
before we declare 1.0
1.The list dims suggested
(http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0)
2.AXIOM release , I think its better if we can do Axis2 1.0 with
AXIOM release rather than SNAPSHOT
3.JIRA fixing
4.code clean up
5.I18n
There is a number of JIRAs on code generation and ADB and I think it
is better if we can fix them after 0.95. We will need to do another
quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that
boils down to the following release plan,
1.Axis2 0.95 in this week (20-25)
2.Axis2 0.96 first week of the April
3.If we dont find any major issues then we mark 0.96 as Axis2 1.0
Comments and suggestions are warmly welcome !!!!
- --
Thanks,
Deepal
................................................................
~Future is Open~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+
g9YUcE97iKPFKXcjVC7xT8E=
=MIjV
-----END PGP SIGNATURE-----