OFBIZ-3912 is a good example of an issue that is critical to an individual rather than the community I think. A good indicator is that it has been broken for 5 months before being reported, can't be that critical then huh?
Regards Scott On 31/08/2010, at 9:45 PM, Jacques Le Roux wrote: > Scott Gray wrote: >> A blocking bug IMO is nothing more than the community (rather than an >> individual) deciding that a bug is important enough that a >> release shouldn't occur until it is fixed. I don't think we need any >> criteria other than that really. > > Yes that's fine to me. And a critical (for instance at > https://issues.apache.org/jira/browse/OFBIZ-3912)? > > Jacques >> Regards >> Scott >> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote: >>> Hey Scott, that's right! >>> Happy to close this one. So eventually you were right, there are ANY >>> blocking bugs in OFBiz under our criteria ;o) >>> Though I guess we should better define our criteria for blocking. Because >>> if we allow to use blocking only for bugs blocking all >>> OFBiz there should be hardly any such bugs. I mean it would be very, very >>> quickly fixed and we would have hardly the time to >>> create a blocking bug. Notbaly because we have now BuildBot running and all >>> commiters are quickly aware of any errors they >>> woulds have made. Did you thought about it Scott, what is your perception? >>> Thanks >>> Jacques >>> Scott Gray wrote: >>>> Hi Jacques, >>>> I thought you fixed OFBIZ-3837 recently? Or was that some other shipping >>>> estimate problem you were working on? >>>> Regards >>>> Scott >>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote: >>>>> There are currently 275 UNRESOLVED bugs, 11 have patches available, 14 >>>>> are reopened. >>>>> This is againt all versions. There are only 78 for trunk but this is not >>>>> a reliable criteria (if any are) >>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as blocking. >>>>> But I guess not under Scott's criteria (it's not >>>>> blocking OFBiz, just blocking a part of it, so it's critical actually) 4 >>>>> are critical and 173 major >>>>> No needs to say that any help to clean things would be really >>>>> appreciated... >>>>> HTH >>>>> Jacques >>>>> From: "BJ Freeman" <[email protected]> >>>>>> Quick scan of Jira shows 4 open bugs not counting mine. >>>>>> ========================= >>>>>> BJ Freeman <http://bjfreeman.elance.com> >>>>>> Strategic Power Office with Supplier Automation >>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52> >>>>>> Specialtymarket.com <http://www.specialtymarket.com/> >>>>>> Systems Integrator-- Glad to Assist >>>>>> Chat Y! messenger: bjfr33man >>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM: >>>>>>> Actually I meant a response to it like there are no bugs that fit this >>>>>>> condition. >>>>>>> ========================= >>>>>>> BJ Freeman <http://bjfreeman.elance.com> >>>>>>> Strategic Power Office with Supplier Automation >>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52> >>>>>>> Specialtymarket.com <http://www.specialtymarket.com/> >>>>>>> Systems Integrator-- Glad to Assist >>>>>>> Chat Y! messenger: bjfr33man >>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM: >>>>>>>> You missed something by reading an email from a community member and >>>>>>>> interpreting it's contents as some sort of official policy. >>>>>>>> Regards >>>>>>>> Scott >>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote: >>>>>>>>> I was reffering to this: >>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote: >>>>>>>>>> I guess the basic questions might be: Did we have an official >>>>>>>>>> "freeze" >>>>>>>>>> process where we only accepted bug fixes against that branch? Do we >>>>>>>>>> have >>>>>>>>>> any open bugs that are considered "release critical"? >>>>>>>>> I agree. At least *all* bugs should be looked at, and given a target >>>>>>>>> release tag, etc. Time for some bug triage. I don't think there has >>>>>>>>> been a concerted effort like that in like, forever. >>>>>>>>> I have not seen anything that shows this as taken care of. >>>>>>>>> Have I missed something? >>>>>>>>> ========================= >>>>>>>>> BJ Freeman<http://bjfreeman.elance.com> >>>>>>>>> Strategic Power Office with Supplier >>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52> >>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/> >>>>>>>>> Systems Integrator-- Glad to Assist >>>>>>>>> Chat Y! messenger: bjfr33man >>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM: >>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote: >>>>>>>>>>> There are a number of bugs that have to be resolved before release >>>>>>>>>>> remember this is a volunteer effort so there is no full time person >>>>>>>>>>> doing the patches for the bugs. >>>>>>>>>> What are you basing this on? >>>>>>>>>>> once they are completed and testing has been done then there will >>>>>>>>>>> be a release. >>>>>>>>>>> right now we are about 4 months past the planned release date. >>>>>>>>>> What are you basing this on? Maybe there is some confusion... the >>>>>>>>>> date on a release is the date it was branched from the trunk, not >>>>>>>>>> the date that a binary release is done from the branch. >>>>>>>>>> -David >>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM: >>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected release >>>>>>>>>>>> date? >>>>>>>>>>>> Just curious. >
smime.p7s
Description: S/MIME cryptographic signature
