incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Li Feng Wang <phoenix.wan...@gmail.com>
Subject Re: [DISCUSS]What is the criteria for 3.4.1 release blocker?
Date Thu, 21 Jun 2012 05:50:44 GMT
I think release blocker include crash, regression and data loss.

A more better definition of show stopper criteria can be found in the wiki
http://wiki.services.openoffice.org/wiki/Showstopper

2012/6/21 Dennis E. Hamilton <dennis.hamilton@acm.org>

> I think safety is of high value.
>
> That includes security issues and also data loss/corruption.  The last
> includes crashers that result in unrecoverable loss of work.  Hidden loss
> of work and document corruption that does not appear until the document is
> opened later is particularly serious.
>
>  - Dennis
>
> -----Original Message-----
> From: dongjun zong [mailto:zongdj001@gmail.com]
> Sent: Wednesday, June 20, 2012 20:31
> To: ooo-dev@incubator.apache.org
> Subject: Re: [DISCUSS]What is the criteria for 3.4.1 release blocker?
>
> I think high severity regression issue, common usage function related issue
> should be considered as release blocker.
>
> 2012/6/21 Ji Yan <yanji.yj@gmail.com>
>
> > From my point of view, security and high usability issue should be set as
> > blocker
> >
> > 2012/6/21 debin lei <leidb@apache.org>
> >
> > > Hi, All
> > > I noticed that there are some issues, which are proposed as 3.4.1
> release
> > > blocker recently. However, I am not sure what is the criteria for the
> > > release blocker?
> > > Is it regression or impact serious ? Or high benefit to risk ratio from
> > dev
> > > view ?
> > > I think maybe consider more things, but not sure.
> > > So if you can give your criteria and discuss here to make the things
> more
> > > clear will be very helpful.
> > > Thanks.
> > >
> > > Best regards.
> > > Lei De Bin
> > >
> >
> >
> >
> > --
> >
> >
> > Thanks & Best Regards, Yan Ji
> >
>
>


-- 
Best Wishes, LiFeng Wang

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message