You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Shenfeng Liu <li...@gmail.com> on 2012/08/22 16:48:23 UTC
Defect Status wiki
Thanks for Rob's defect chart!
While, I think there are more defect status worthy to trace to give people
the overall picture of AOO quality status. So I created a AOO Defect Status
Report<https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+Defect+Status+Report>wiki
to list what in my mind. I will think about how to merge the
information to the defect chart page below when I figure out how to create
multiple charts in one page.
The information can include:
(1) Snapshot data that tell us the backlog status that need developer,
tester and release manager's attention.
(2) Weekly progress similar to the defect chart page below to show our
achievements.
(3) Top contributors in different areas for recognition and to show our
appreciation. (but unfortunately I don't know how to create the queries...
:-( )
Some questions I have:
(1) I'm a poor BZ user. Those marked in red mean I don't know how to
create the query (or list corresponding columns). I wonder if any one give
the suggestion?
(2) I'm not sure what's the difference between the status *Verified* and
*Closed*. IMO all the defects verified should finally be closed.
(3) Any more queries?
Any comments are welcome!
- Simon
2012/8/16 Rob Weir <ro...@apache.org>
> On Wed, Aug 15, 2012 at 10:05 AM, Shenfeng Liu <li...@gmail.com> wrote:
> > Rob,
> > It is a great idea to put the CSV files to Subversion!
> > Attached is the file I created for issue created and fixed, taking
> > 2011-06-01 as starting point, and counting all the issue types in.
> > Please check if you have any comments or suggestion.
> >
>
> Here it is: http://www.openoffice.org/stats/defects.html
>
> If you have a better description you can edit the HTML to add it.
>
>
> -Rob
>
>
> > Thanks!
> >
> > - Shenfeng
> >
> >
> > 2012/8/15 Rob Weir <ro...@apache.org>
> >>
> >> On Wed, Aug 15, 2012 at 2:23 AM, Shenfeng Liu <li...@gmail.com>
> wrote:
> >> > Rob,
> >> > For the defect status, I created r searches and shared them:
> >> >
> >> >
> >> > - All_Closed_Since
> >> > - All_In_Resolved_Since
> >> > - All_Reported_Since
> >> > - All_Verified_Since
> >> >
> >> >
> >> > I will make out the csv files later.
> >>
> >> Great. My goal is to have the charts be based on CSV files that we
> >> store in Subversion. That way any of us can update the data with
> >> simple check-in, even using the CMS interface.
> >>
> >> -Rob
> >>
> >>
> >> > And I'm thinking of a wiki to consolidate those defect/quality
> status
> >> > summary with weekly/monthly update, as you suggested before. Also will
> >> > do
> >> > it later this week.
> >> > Thanks!
> >> >
> >> > - Shenfeng
> >> >
> >> >
> >> > 2012/8/15 Rob Weir <ro...@apache.org>
> >> >
> >> >> On Tue, Aug 14, 2012 at 7:12 PM, Kay Schenk <ka...@gmail.com>
> >> >> wrote:
> >> >> > On Tue, Aug 14, 2012 at 10:46 AM, Rob Weir <ro...@apache.org>
> >> >> > wrote:
> >> >> >
> >> >> >> http://www.openoffice.org/stats/ooo-dev-subscribers.html
> >> >> >>
> >> >> >> and
> >> >> >>
> >> >> >> http://www.openoffice.org/stats/committers.html
> >> >> >>
> >> >> >> I'm getting the hang of this, so if there is any other data that
> is
> >> >> >> easy to extract on a regular basis, I can make charts for these.
> >> >> >>
> >> >>
> >> >> OK. I fixed the typos that Andrea noted.
> >> >>
> >> >> >
> >> >> > These are great! What can we do to make them more easy to find?
> >> >> >
> >> >>
> >> >> Maybe we can turn the main ooo/stats/index.html page into a directory
> >> >> of stats, each one on its own page?
> >> >>
> >> >> But then the stats project is not prominently linked either. But
> >> >> there are ways we can fix that as well. If we can get a few good
> stats
> >> >> pages up it might even be worth having a blog post on them.
> >> >>
> >> >> >
> >> >> >>
> >> >> >> The technical requirement is that they need to be formed into a
> CSV
> >> >> >> file with each row like this:
> >> >> >>
> >> >> >> iso-date, data-1, data-2,....data-n
> >> >> >>
> >> >> >> For example see this data file:
> >> >> >> http://www.openoffice.org/stats/aoo34-downloads.txt
> >> >> >>
> >> >> >> If there are multiple data points for each date, they can be
> >> >> >> displayed
> >> >> >> on the same or separate charts.
> >> >> >>
> >> >> >> Any suggestions?
> >> >> >>
> >> >> >> Bug find/fix rates?
> >> >> >>
> >> >> >
> >> >> > This one would definitely be good to graph...but I'm not sure how
> to
> >> >> > approach it.
> >> >> > I just did a search on "bug fix rates" and well...an interesting
> cast
> >> >> > of
> >> >> > ideas....
> >> >> >
> >> >>
> >> >> If we can get a report of new bugs by creation date, and closed bugs
> >> >> by fix date, then we can get the data series we need.
> >> >>
> >> >> >
> >> >> >>
> >> >> >> Forum posts/subscribers?
> >> >> >>
> >> >> >> Commits?
> >> >> >>
> >> >> >> Regards,
> >> >> >>
> >> >> >> -Rob
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> >
> >> >>
> >> >>
> ----------------------------------------------------------------------------------------
> >> >> > MzK
> >> >> >
> >> >> > "Never express yourself more clearly than you are able to think."
> >> >> >
> >> >> --
> >> >> > Niels Bohr
> >> >>
> >
> >
>
Re: Defect Status wiki
Posted by Shenfeng Liu <li...@gmail.com>.
Andrea,
Thanks for your explanation!
I think we can just follow the original process if the development is on
a feature branch, and close the defect only when the fix is available on
main trunk or a release. While if the fix is delivered directly to trunk or
a release branch, we can take the lighter approach and go quickly to CLOSED
status.
- Simon
2012/8/25 Andrea Pescetti <pe...@apache.org>
> On 22/08/2012 Shenfeng Liu wrote:
>
>> (2) I'm not sure what's the difference between the status *Verified*
>> and
>> *Closed*. IMO all the defects verified should finally be closed.
>>
>
> In the old OpenOffice.org project, where the QA process was probably more
> formal, the meaning were the following:
> - Verified: a developer snapshot (in binary form) contains the fix
> - Closed: a stable version (in binary form) contains the fix
>
> So in theory one should now go through all the VERIFIED issues, check them
> with version 3.4.1 and set them to RESOLVED CLOSED if the fix works.
>
> In practice the code now has fewer complexities than it used to have (it
> had dozens of "Child workspaces", or CWS, where development was done) so
> it's understandable that we take a lighter approach on this too.
>
> Regards,
> Andrea.
>
Re: Defect Status wiki
Posted by Andrea Pescetti <pe...@apache.org>.
On 22/08/2012 Shenfeng Liu wrote:
> (2) I'm not sure what's the difference between the status *Verified* and
> *Closed*. IMO all the defects verified should finally be closed.
In the old OpenOffice.org project, where the QA process was probably
more formal, the meaning were the following:
- Verified: a developer snapshot (in binary form) contains the fix
- Closed: a stable version (in binary form) contains the fix
So in theory one should now go through all the VERIFIED issues, check
them with version 3.4.1 and set them to RESOLVED CLOSED if the fix works.
In practice the code now has fewer complexities than it used to have (it
had dozens of "Child workspaces", or CWS, where development was done) so
it's understandable that we take a lighter approach on this too.
Regards,
Andrea.