Let me put some of my thoughts about blockers and releases.
According to the current rules, we have to have zero blockers to do a release. So sometimes what we does is downgrade some issue according to their criticalness. I think this is not a necessity. As I believe deciding a blocker or not is up to the user. if he do not have any work around and if he as block due to that issue it is ok to put this as a blocker. So another person can not change it unless he can give an valid work around or find an problem with the issue (according to some spaces). On the other hand as developers we have some limitations. i.e Sometimes we may unable to fix a blocker (i.e due to technical problems etc..) So there may be issues which are blockers but won't fix for the release. What I am basically saying is this. Lets say after an release (e.g .Axis2 1.2 ) we got 20 blockers and could fix 17 and 3 left. if the last 3 going to take lot of time are we supposed to hold the release until all are fixed? So that every one has to wait until everything fixed. My guess is we should release with the fixed blockers and with the new features have added to the release. But one thing. For any release we can not have broken features. i.e. which were worked with the earlier release but not now. This does not mean we don't do any thing about the reaming 3 blockers. we can time to time try to fix this with different ways. For an example in codegen there were some problems with the xmlbeans and adb after Axis2 1.2. I could fixed most of adb issues and add lot of new featurs as well (some issues regarding adb-codegen, codgen, wsdl) . But could not resolve some critical xmlbeans problems although I tried them. So if someone suggest to stop adding new features until fix all the xmlbeans problems, I belive that is not an efficient use of time. And also Since at close to a release everyone concentrating on fixing issues, if someone report issues on an RC there is high probability of being fixed them immediately. Finally this is what I have to say, As developers we must try our best to resolve blockers. mean time we have to add new features to the product as well. otherwise it won't evolve. Thanks. Amila. On 7/4/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
On 7/2/07, Kelvin Lin <[EMAIL PROTECTED]> wrote: > > I am really looking forwards to fixing this one: > > https://issues.apache.org/jira/browse/AXIS2-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > Second part of two-part message is ignored by WSDL2Java > > because in my project doing now, there is a this scenario: > > <wsdl:message name="createRequest"> > <wsdl:part name="header" element="abc:header"/> > <wsdl:part name="create" element="abcthis:createRequest" /> > </wsdl:message> > > It prevent me from using wsdl2c tool. > see my comment on this, this wsdl is not valid according to the WS basic profile. see http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16574232 R2210 if you use document literal binding you can not have more than one part unless you delare one in soap boady. *Ruchith Fernando <[EMAIL PROTECTED]>* wrote: > > Yes .... we will be releasing Rampart along with Axis2 as soon as 1.3goes out! > > Thanks, > Ruchith > > On 7/2/07, stlecho wrote: > > > > Is this cleaning up phase also applicable for the Rampart module or > only for > > the Axis2 framework ? > > In other words, can I vote for JIRA issues related to Rampart ? > > > > Regards, Stefan Lecho. > > > > > > dims wrote: > > > > > > Dear Axis2 Users, > > > > > > We are working hard on cleaning up the issues in JIRA. > > > > > > > -- > > View this message in context: > http://www.nabble.com/-Axis2--Please-VOTE-for-your-favorite-bug-to-be-fixed.-tf3996952.html#a11391423 > > Sent from the Axis - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > www.ruchith.org > www.wso2.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > ------------------------------ > Boardwalk for $500? In 2007? Ha! > Play Monopoly Here and Now<http://us.rd.yahoo.com/evt=48223/*http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow>(it's updated for today's economy) at Yahoo! Games. > > -- Amila Suriarachchi, WSO2 Inc.
-- Amila Suriarachchi, WSO2 Inc.
