Pae Choi wrote: > > Just because we are playing in the bleeding edge of open-source development > and heading to new and emerging standards, the dev. team should not drop the > existing and running product. In addition to that, the migration should not > be forced to the "alpha-staged" product neither. Those decisions must be > influenced by the user community and left to them to make their decision. > And they will do when they feel and ready to do so bsed on the various > reasons. It has been in that way and it will be so at least for a while.
Relax. By and large, patches submitted against SOAP 2.x have been incorporated. Occasionally, we need a gentle nudge or reminder. Meanwhile daily builds are made and posted. A SOAP 2.3 release is likely at some point to incorporate these patches. Occasionally, there will be a request for a feature for which the response will be "fixed in next release". That is to be expected. That doesn't affect users of the current release one bit. You want to be adventurous and try out some of the new features? We will welcome you. You don't feel so adventurous at the moment and want to stick with what you have got? That's fine too. - Sam Ruby
