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 Eran Chinthaka <ch...@opensource.lk> on 2007/07/01 05:53:15 UTC

Re: [Axis2] Please VOTE for your favorite bug to be fixed.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michele Mazzucco wrote:
> Dims,
> 
> what about postponing the 1.3 release and fixing (at least) all the
> blockers? ;)

Michele,

I do not see a point in that. If we have a deadline then everyone is
encouraged to work. If just postpone then we will lose the momentum. And
also of there are significant improvements over the last release then it
is the best to think about a release. I think what we need is to set
realistic goals with deadlines which is what Dims had done.

Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
NT3qeHhTTHvqsM0uzVuo5Xo=
=QTbK
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry for hijacking this thread.


Can we please also remove the documentation links for our older releases
from the left tool bar of the site. For me it is irritating to see 0.94
documentation still in Axis2 main page.

Can we please move it to some other place?

Deepal Jayasinghe wrote:
> Hi robert,
> 
> good point  , I will update the site with the RC this time.
> 
> Thanks
> Deepal
>> Lack of getting the RC's being used by end users has I think been one
>> of the main causes for instability. I'd really like to try something
>> new this time around that might get more users using them.
>>
>> I'm all for  "Release early and often" - in fact arguably we don't do
>> enough point releases. I realize though that there are lots of deps
>> and its hard to coordinate all the releases.
>>
>> Anyways, IIRC the RC's never got put on the download page. The only
>> announcement is to the list. Other projects have better usage of their
>> RC's and I think it'd be worth exploring what could be done
>> differently to get more RC usage of axis2.
>>
>> I've noticed xmlbeans, for example, has been broken on every release
>> so far. And while I tested svn in the middle of dev, I never did test
>> the RC's so I accept part of the blame. This time around I plan on
>> testing xmlbeans on some of my complex schemas, and the other things I
>> personally use like spring and the soapmonitor.
>>
>> Michele, from what I've seen you're had some of the most advanced use
>> cases of axis2. If you could do some RC testing with some of your use
>> cases I'd think that'd go a long way to making 1.3 the most stable yet.
>>
>> No one uses 100% of axis2, but I'd think that if we got more people
>> using the RC's on _their_ code, it'd help plenty.
>>
>> Robert
>>
>> On 7/2/07, * Davanum Srinivas* <davanum@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>>     no it doesnt. this is a classic chicken and egg issue. thats why we
>>     make so many RC's but still end users dont play enough with RC's as
>>     much as we'd like them to :)
>>
>>     thx,
>>     dims
>>
>>     On 7/2/07, Michele Mazzucco < Michele.Mazzucco@ncl.ac.uk
>>     <ma...@ncl.ac.uk>> wrote:
>>     > Eran,
>>     >
>>     > On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
>>     > > I do agree with you that we need a reliable Axis2, but that
>>     doesn't
>>     > > mean
>>     > > we need to keep on postponing releases "until" we fix everything.
>>     >
>>     >
>>     > there was no insult in my comments. My point, instead, is that
>>     if you
>>     > want new features you can download the last nightly build. If
>>     you want
>>     > something which works *properly* you download a release. Does it
>>     make
>>     > sense to release a new version and then ask to people to
>>     download the
>>     > next nightly build because the release is "broken"?
>>     >
>>     >
>>     > Michele
>>     >
>>     >
>>     >
>>     ---------------------------------------------------------------------
>>     > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>     <ma...@ws.apache.org>
>>     > For additional commands, e-mail: axis-user-help@ws.apache.org
>>     <ma...@ws.apache.org>
>>     >
>>     >
>>
>>
>>     --
>>     Davanum Srinivas :: http://davanum.wordpress.com
>>     <http://davanum.wordpress.com>
>>
>>     ---------------------------------------------------------------------
>>     To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>     <ma...@ws.apache.org>
>>     For additional commands, e-mail: axis-user-help@ws.apache.org
>>     <ma...@ws.apache.org>
>>
>>
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGjF/TjON2uBzUhh8RAgUdAKCrmwNQ3dUTzlYHVDXTjFUXwheWqQCgmFfk
RfjfwueVngzd2898nHoFits=
=RRmr
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi robert,

good point  , I will update the site with the RC this time.

Thanks
Deepal
> Lack of getting the RC's being used by end users has I think been one
> of the main causes for instability. I'd really like to try something
> new this time around that might get more users using them.
>
> I'm all for  "Release early and often" - in fact arguably we don't do
> enough point releases. I realize though that there are lots of deps
> and its hard to coordinate all the releases.
>
> Anyways, IIRC the RC's never got put on the download page. The only
> announcement is to the list. Other projects have better usage of their
> RC's and I think it'd be worth exploring what could be done
> differently to get more RC usage of axis2.
>
> I've noticed xmlbeans, for example, has been broken on every release
> so far. And while I tested svn in the middle of dev, I never did test
> the RC's so I accept part of the blame. This time around I plan on
> testing xmlbeans on some of my complex schemas, and the other things I
> personally use like spring and the soapmonitor.
>
> Michele, from what I've seen you're had some of the most advanced use
> cases of axis2. If you could do some RC testing with some of your use
> cases I'd think that'd go a long way to making 1.3 the most stable yet.
>
> No one uses 100% of axis2, but I'd think that if we got more people
> using the RC's on _their_ code, it'd help plenty.
>
> Robert
>
> On 7/2/07, * Davanum Srinivas* <davanum@gmail.com
> <ma...@gmail.com>> wrote:
>
>     no it doesnt. this is a classic chicken and egg issue. thats why we
>     make so many RC's but still end users dont play enough with RC's as
>     much as we'd like them to :)
>
>     thx,
>     dims
>
>     On 7/2/07, Michele Mazzucco < Michele.Mazzucco@ncl.ac.uk
>     <ma...@ncl.ac.uk>> wrote:
>     > Eran,
>     >
>     > On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
>     > > I do agree with you that we need a reliable Axis2, but that
>     doesn't
>     > > mean
>     > > we need to keep on postponing releases "until" we fix everything.
>     >
>     >
>     > there was no insult in my comments. My point, instead, is that
>     if you
>     > want new features you can download the last nightly build. If
>     you want
>     > something which works *properly* you download a release. Does it
>     make
>     > sense to release a new version and then ask to people to
>     download the
>     > next nightly build because the release is "broken"?
>     >
>     >
>     > Michele
>     >
>     >
>     >
>     ---------------------------------------------------------------------
>     > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>     <ma...@ws.apache.org>
>     > For additional commands, e-mail: axis-user-help@ws.apache.org
>     <ma...@ws.apache.org>
>     >
>     >
>
>
>     --
>     Davanum Srinivas :: http://davanum.wordpress.com
>     <http://davanum.wordpress.com>
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>     <ma...@ws.apache.org>
>     For additional commands, e-mail: axis-user-help@ws.apache.org
>     <ma...@ws.apache.org>
>
>

-- 
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"




---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by robert lazarski <ro...@gmail.com>.
Lack of getting the RC's being used by end users has I think been one of the
main causes for instability. I'd really like to try something new this time
around that might get more users using them.

I'm all for  "Release early and often" - in fact arguably we don't do enough
point releases. I realize though that there are lots of deps and its hard to
coordinate all the releases.

Anyways, IIRC the RC's never got put on the download page. The only
announcement is to the list. Other projects have better usage of their RC's
and I think it'd be worth exploring what could be done differently to get
more RC usage of axis2.

I've noticed xmlbeans, for example, has been broken on every release so far.
And while I tested svn in the middle of dev, I never did test the RC's so I
accept part of the blame. This time around I plan on testing xmlbeans on
some of my complex schemas, and the other things I personally use like
spring and the soapmonitor.

Michele, from what I've seen you're had some of the most advanced use cases
of axis2. If you could do some RC testing with some of your use cases I'd
think that'd go a long way to making 1.3 the most stable yet.

No one uses 100% of axis2, but I'd think that if we got more people using
the RC's on _their_ code, it'd help plenty.

Robert

On 7/2/07, Davanum Srinivas <da...@gmail.com> wrote:
>
> no it doesnt. this is a classic chicken and egg issue. thats why we
> make so many RC's but still end users dont play enough with RC's as
> much as we'd like them to :)
>
> thx,
> dims
>
> On 7/2/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> > Eran,
> >
> > On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
> > > I do agree with you that we need a reliable Axis2, but that doesn't
> > > mean
> > > we need to keep on postponing releases "until" we fix everything.
> >
> >
> > there was no insult in my comments. My point, instead, is that if you
> > want new features you can download the last nightly build. If you want
> > something which works *properly* you download a release. Does it make
> > sense to release a new version and then ask to people to download the
> > next nightly build because the release is "broken"?
> >
> >
> > Michele
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>

Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Davanum Srinivas <da...@gmail.com>.
no it doesnt. this is a classic chicken and egg issue. thats why we
make so many RC's but still end users dont play enough with RC's as
much as we'd like them to :)

thx,
dims

On 7/2/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Eran,
>
> On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
> > I do agree with you that we need a reliable Axis2, but that doesn't
> > mean
> > we need to keep on postponing releases "until" we fix everything.
>
>
> there was no insult in my comments. My point, instead, is that if you
> want new features you can download the last nightly build. If you want
> something which works *properly* you download a release. Does it make
> sense to release a new version and then ask to people to download the
> next nightly build because the release is "broken"?
>
>
> Michele
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Eran,

On Sun, 2007-07-01 at 18:26 -0400, Eran Chinthaka wrote:
> I do agree with you that we need a reliable Axis2, but that doesn't
> mean
> we need to keep on postponing releases "until" we fix everything. 


there was no insult in my comments. My point, instead, is that if you
want new features you can download the last nightly build. If you want
something which works *properly* you download a release. Does it make
sense to release a new version and then ask to people to download the
next nightly build because the release is "broken"?


Michele


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michele Mazzucco wrote:
> Eran,
> 
> your point is "let's add new, cool features", my point is "let's build
> something reliable". 

I think you didn't get my point. " ..there are significant improvements
over the last release .." doesn't mean they are not only new cool
features.  Fault handling was not working properly in the last release
and we fixed it. If you really looked at what we did during the
hackathon then you know how we improved it and how significant was it.
That is what I meant.

I am sorry if my interpretation of "significant improvements" is wrong
coz I know and agree my English is not that good  :)

I do agree with you that we need a reliable Axis2, but that doesn't mean
we need to keep on postponing releases "until" we fix everything.

Ok, let's say we postpone the release. How can you help fixing some
blockers to make it more reliable? What is the plan you have? Just
asking to postpone thinking "some one" will fix blockers and "some day"
we will get a more stable one is nothing more than following a mirage
for me.

Thanks,
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGiCoCjON2uBzUhh8RAgg2AJ9nuKj1XGyTL95b6r/RT9RvK7eaNgCgmuxL
+ZibYf5NirmRu0x5uIlw18c=
=cqzr
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Davanum Srinivas <da...@gmail.com>.
Michele,

from prev experience it takes us at least 2-3 RC's and then final.
There is no way we can get thru all that in a couple of days. do you?
:)

-- dims

On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Dims,
>
> I disagree with what Eran says, which is "we have a deadline, so
> probably not all bugs will be fixed for the next release". I think
> people would be much more happy to wait 1 or 2 weeks more to have a
> more reliable release than having an unstable one now. Simply
> lowering bug priorities from blockers to critical (or other) doesn't
> mean the tool is bug free (this is what I understand from previous
> emails). And, of course, adding new features will probably mean
> adding new bugs as well.
>
>
> Michele
>
> On 1 Jul 2007, at 13:09, Davanum Srinivas wrote:
>
> > Michele,
> >
> > Why do you think that? Blockers are Blockers for the release. If the
> > blockers are not addressed, there will not be a release. Isn't that
> > why i sent this email about voting for your bug and adding comments to
> > make stuff blockers?
> >
> > What am i missing here?
> >
> > thanks,
> > dims
> >
> > On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> >> Eran,
> >>
> >> your point is "let's add new, cool features", my point is "let's
> >> build something reliable". I think if you want to use a tool in a
> >> production environment the second point is much more important.
> >>
> >>
> >> Michele
> >>
> >> On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:
> >>
> >> > -----BEGIN PGP SIGNED MESSAGE-----
> >> > Hash: SHA1
> >> >
> >> > Michele Mazzucco wrote:
> >> >> Dims,
> >> >>
> >> >> what about postponing the 1.3 release and fixing (at least) all
> >> the
> >> >> blockers? ;)
> >> >
> >> > Michele,
> >> >
> >> > I do not see a point in that. If we have a deadline then
> >> everyone is
> >> > encouraged to work. If just postpone then we will lose the
> >> > momentum. And
> >> > also of there are significant improvements over the last release
> >> > then it
> >> > is the best to think about a release. I think what we need is to
> >> set
> >> > realistic goals with deadlines which is what Dims had done.
> >> >
> >> > Chinthaka
> >> > -----BEGIN PGP SIGNATURE-----
> >> > Version: GnuPG v1.4.3 (GNU/Linux)
> >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >> >
> >> > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
> >> > NT3qeHhTTHvqsM0uzVuo5Xo=
> >> > =QTbK
> >> > -----END PGP SIGNATURE-----
> >> >
> >> >
> >> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Dims,

I disagree with what Eran says, which is "we have a deadline, so  
probably not all bugs will be fixed for the next release". I think  
people would be much more happy to wait 1 or 2 weeks more to have a  
more reliable release than having an unstable one now. Simply  
lowering bug priorities from blockers to critical (or other) doesn't  
mean the tool is bug free (this is what I understand from previous  
emails). And, of course, adding new features will probably mean  
adding new bugs as well.


Michele

On 1 Jul 2007, at 13:09, Davanum Srinivas wrote:

> Michele,
>
> Why do you think that? Blockers are Blockers for the release. If the
> blockers are not addressed, there will not be a release. Isn't that
> why i sent this email about voting for your bug and adding comments to
> make stuff blockers?
>
> What am i missing here?
>
> thanks,
> dims
>
> On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
>> Eran,
>>
>> your point is "let's add new, cool features", my point is "let's
>> build something reliable". I think if you want to use a tool in a
>> production environment the second point is much more important.
>>
>>
>> Michele
>>
>> On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:
>>
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > Michele Mazzucco wrote:
>> >> Dims,
>> >>
>> >> what about postponing the 1.3 release and fixing (at least) all  
>> the
>> >> blockers? ;)
>> >
>> > Michele,
>> >
>> > I do not see a point in that. If we have a deadline then  
>> everyone is
>> > encouraged to work. If just postpone then we will lose the
>> > momentum. And
>> > also of there are significant improvements over the last release
>> > then it
>> > is the best to think about a release. I think what we need is to  
>> set
>> > realistic goals with deadlines which is what Dims had done.
>> >
>> > Chinthaka
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v1.4.3 (GNU/Linux)
>> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>> >
>> > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
>> > NT3qeHhTTHvqsM0uzVuo5Xo=
>> > =QTbK
>> > -----END PGP SIGNATURE-----
>> >
>> >  
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> -- 
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Davanum Srinivas <da...@gmail.com>.
Michele,

Why do you think that? Blockers are Blockers for the release. If the
blockers are not addressed, there will not be a release. Isn't that
why i sent this email about voting for your bug and adding comments to
make stuff blockers?

What am i missing here?

thanks,
dims

On 7/1/07, Michele Mazzucco <Mi...@ncl.ac.uk> wrote:
> Eran,
>
> your point is "let's add new, cool features", my point is "let's
> build something reliable". I think if you want to use a tool in a
> production environment the second point is much more important.
>
>
> Michele
>
> On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Michele Mazzucco wrote:
> >> Dims,
> >>
> >> what about postponing the 1.3 release and fixing (at least) all the
> >> blockers? ;)
> >
> > Michele,
> >
> > I do not see a point in that. If we have a deadline then everyone is
> > encouraged to work. If just postpone then we will lose the
> > momentum. And
> > also of there are significant improvements over the last release
> > then it
> > is the best to think about a release. I think what we need is to set
> > realistic goals with deadlines which is what Dims had done.
> >
> > Chinthaka
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.3 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
> > NT3qeHhTTHvqsM0uzVuo5Xo=
> > =QTbK
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [Axis2] Please VOTE for your favorite bug to be fixed.

Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Eran,

your point is "let's add new, cool features", my point is "let's  
build something reliable". I think if you want to use a tool in a  
production environment the second point is much more important.


Michele

On 1 Jul 2007, at 04:53, Eran Chinthaka wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Michele Mazzucco wrote:
>> Dims,
>>
>> what about postponing the 1.3 release and fixing (at least) all the
>> blockers? ;)
>
> Michele,
>
> I do not see a point in that. If we have a deadline then everyone is
> encouraged to work. If just postpone then we will lose the  
> momentum. And
> also of there are significant improvements over the last release  
> then it
> is the best to think about a release. I think what we need is to set
> realistic goals with deadlines which is what Dims had done.
>
> Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5
> NT3qeHhTTHvqsM0uzVuo5Xo=
> =QTbK
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org