Can't this be handled via a patch on top of 1.2?
On 4/13/08, Dave Sowerby <[EMAIL PROTECTED]> wrote: > > +1 for a respin - I think this one's a big enough of a problem to justify > it. > > On Sun, Apr 13, 2008 at 3:56 PM, Simon Nash <[EMAIL PROTECTED]> wrote: > > I believe we now understand the impact of this problem and we > > have a fix/workaround that could be applied to the codebase > > (see [1] for details). We need to decide whether it's worth > > holding the 1.2 release for a respin to include this fix. > > > > On the pro side for holding the release: > > Problems with WSDL generation have been a frequent topic > > of posts to the list. They are very visible to beginning > > users and they damage Tuscany's credibility. > > We know of one user who has already hit this problem, and we > > don't yet know if he is able to work around it given his > > environment (Axis). > > We don't know how many users will be impacted by the problem > > (this could also be a con, depending on one's viewpoint). > > The fix/workaround is small and low risk. > > > > On the con side for holding the release: > > Extra work and delay to getting the release out. > > It's possible (but unlikely) that applying the fix/workaround > > could create other issues. > > We don't know how many users will be impacted by the problem > > (this could also be a pro, depending on one's viewpoint). > > > > My view is that the balance is on the side of holding the release > > and respinning to fix this. I'd welcome other opinions. > > > > Simon > > > > [1] https://issues.apache.org/jira/browse/TUSCANY-2220 > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Dave Sowerby MEng MBCS > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
