Author: linus
Date: 2008-09-12 22:47:03-0700
New Revision: 15717
Modified:
trunk/documentation/cookbook/building.xml
trunk/documentation/cookbook/changelog.xml
trunk/documentation/cookbook/images/cookbook/IssueBigPicture.gif
trunk/documentation/cookbook/introduction.xml
trunk/documentation/cookbook/issueprocess.zargo
trunk/documentation/cookbook/process.xml
trunk/www/faqs/users.html
trunk/www/members/project_members.html
trunk/www/project_bugs.html
Log:
Commited the process change to de-emphasize the verification of issues.
Modified: trunk/documentation/cookbook/building.xml
Url: http://argouml.tigris.org/source/browse/argouml/trunk/documentation/cookbook/building.xml?view=diff&rev=15717&p1=trunk/documentation/cookbook/building.xml&p2=trunk/documentation/cookbook/building.xml&r1=15716&r2=15717
==============================================================================
--- trunk/documentation/cookbook/building.xml (original)
+++ trunk/documentation/cookbook/building.xml 2008-09-12 22:47:03-0700
@@ -3788,6 +3788,14 @@
active.
</para>
</listitem>
+ <listitem id="prepare_for_closing">
+ <para>Decide on when RESOLVED or VERIFIED issues are closed</para>
+ <para>
+Add a message of all RESOLVED or VERIFIED issues stating
+when they will be closed.
+After that period, close them unless they have been reopened.
+</para>
+ </listitem>
</orderedlist>
</listitem>
Modified: trunk/documentation/cookbook/changelog.xml
Url: http://argouml.tigris.org/source/browse/argouml/trunk/documentation/cookbook/changelog.xml?view=diff&rev=15717&p1=trunk/documentation/cookbook/changelog.xml&p2=trunk/documentation/cookbook/changelog.xml&r1=15716&r2=15717
==============================================================================
--- trunk/documentation/cookbook/changelog.xml (original)
+++ trunk/documentation/cookbook/changelog.xml 2008-09-12 22:47:03-0700
@@ -67,6 +67,23 @@
<tbody valign="top">
<row>
+ <entry>2008-09-13</entry>
+ <entry>
+The verification of issues is removed from the processes.
+(See <xref linkend="processes"/>).
+ <note>
+ <title>Design decision - Linus Tolke 2008-09-13</title>
+ <para>
+Verification is no longer encouraged.
+</para>
+ </note>
+ </entry>
+ <entry>Linus Tolke</entry>
+ </row>
+ </tbody>
+
+ <tbody valign="top">
+ <row>
<entry>2008-01-20</entry>
<entry>
Added a quick Eclipse instruction.
@@ -122,9 +139,7 @@
<entry>
Change to the process of verifying issues to allow the reporter to
more freedom.
-(See <xref linkend="rolesofworkers"/>,
-<xref linkend="verify_resolved_fixed"/>,
-<xref linkend="verify_resolved_invalid"/>, and
+(See <xref linkend="rolesofworkers"/>, and
<xref linkend="close_verified_issue"/>).
</entry>
<entry>Linus Tolke</entry>
Modified: trunk/documentation/cookbook/images/cookbook/IssueBigPicture.gif
Url: http://argouml.tigris.org/source/browse/argouml/trunk/documentation/cookbook/images/cookbook/IssueBigPicture.gif?view=diff&rev=15717&p1=trunk/documentation/cookbook/images/cookbook/IssueBigPicture.gif&p2=trunk/documentation/cookbook/images/cookbook/IssueBigPicture.gif&r1=15716&r2=15717
==============================================================================
Binary files. No diff available.
Modified: trunk/documentation/cookbook/introduction.xml
Url: http://argouml.tigris.org/source/browse/argouml/trunk/documentation/cookbook/introduction.xml?view=diff&rev=15717&p1=trunk/documentation/cookbook/introduction.xml&p2=trunk/documentation/cookbook/introduction.xml&r1=15716&r2=15717
==============================================================================
--- trunk/documentation/cookbook/introduction.xml (original)
+++ trunk/documentation/cookbook/introduction.xml 2008-09-12 22:47:03-0700
@@ -193,8 +193,8 @@
From this point on you can comment on bugs yourself directly in Issuezilla.
</para>
- <para> You can also verify issues according to the verification
- process (see <xref linkend="verify_resolved_fixed"/>).
+ <para> You can also close issues according to the verification
+ process (see <xref linkend="close_verified_issues"/>).
</para>
<para> This will help you understand the terminology used in the
project and also gives you an idea of the current quality of
Modified: trunk/documentation/cookbook/issueprocess.zargo
Url: http://argouml.tigris.org/source/browse/argouml/trunk/documentation/cookbook/issueprocess.zargo?view=diff&rev=15717&p1=trunk/documentation/cookbook/issueprocess.zargo&p2=trunk/documentation/cookbook/issueprocess.zargo&r1=15716&r2=15717
==============================================================================
Binary files. No diff available.
Modified: trunk/documentation/cookbook/process.xml
Url: http://argouml.tigris.org/source/browse/argouml/trunk/documentation/cookbook/process.xml?view=diff&rev=15717&p1=trunk/documentation/cookbook/process.xml&p2=trunk/documentation/cookbook/process.xml&r1=15716&r2=15717
==============================================================================
--- trunk/documentation/cookbook/process.xml (original)
+++ trunk/documentation/cookbook/process.xml 2008-09-12 22:47:03-0700
@@ -187,16 +187,13 @@
</para>
<sidebar>
<para>
-Rationale: Each issue have basically four states:
+Rationale: Each issue have basically three states:
<orderedlist>
<listitem>
<para>NEW/STARTED/REOPENED - To be resolved</para>
</listitem>
<listitem>
- <para>RESOLVED - To be verified</para>
- </listitem>
- <listitem>
- <para>VERIFIED - To be closed</para>
+ <para>RESOLVED/VERIFIED - To be closed</para>
</listitem>
<listitem>
<para>CLOSED - Finished.</para>
@@ -214,18 +211,13 @@
"I am now done with my work on this issue".
For a resolver this is corresponds to NEW/REOPEN for the first group,
STARTED for the second and
-RESOLVED for the third.
-For a verifier this corresponds to
-RESOLVED for the first group and
-VERIFIED for the third group.
+RESOLVED/VERIFIED/CLOSED for the third.
</para>
<para>
The RESOLVED/REMIND does not fit this.
-They risk to be verified because the rest of our process urges
-people to resolve issues that are RESOLVED
-in which case they are probably lost.
-They risk to be hanging in the RESOLVED state because nobody understands
+They risk to be hanging in the RESOLVED/VERIFIED
+state because nobody understands
where they should go from there.
It is not clear who is responsible to move them forward.
@@ -315,9 +307,8 @@
Hence, each person involved in issues for the ArgoUML project can -
at the same time - have different roles, and consequently, has
issues to report,
-issues to close,
-issues to resolve, and
-issues to verify.
+issues to close, and
+issues to resolve.
</para>
<sect2 id="rolereporter">
@@ -361,21 +352,6 @@
</listitem>
<listitem>
<para>
-Close the issue
-</para>
- <para>
-This applies to an issue that is in the resolved or verified state.
-At the end of processing the issue,
-the reporter has the final word:
-he can check the result,
-and if he agrees with the solution,
-close the issue himself.
-Closing an issue requires at least "observer" role
-in the ArgoUML project.
-</para>
- </listitem>
- <listitem>
- <para>
Reopen the issue
</para>
<para>
@@ -470,64 +446,6 @@
requirements and release plans.
</para>
</sect2>
- <sect2 id="roleverifier">
- <title>The Verifier</title>
- <para>
-The Verifier may be neither the Reporter, nor the Resolver of the issue.
-The task of the Verifier is to check the quality of the solution by
-confirming that the solution is complete, to the point, bug-free, etc.
-This is an important part of the quality assurance work we do
-in the ArgoUML project and the objective is to make sure that a resolved
-issue is in fact resolved.
-</para>
- <para>
-The test must be done on the "Target Milestone" version of the issue,
-or any later version released to the public.
-</para>
- <para>
-Responsibilities:
- <itemizedlist>
- <listitem>
- <para>
-Check that the issue is solved in the stated version of ArgoUML
-</para>
- </listitem>
- <listitem>
- <para>
-Verify the issue.
-</para>
- <para>
-If the Verifier can conclude that the problem does not exist or
-the feature/enhancement is now present.
-</para>
- </listitem>
- <listitem>
- <para>
-Close the issue.
-</para>
- <para>
-If someone else has already verified the issue then
-the issue can be closed.
-</para>
- </listitem>
- <listitem>
- <para>
-Reopen the issue if the solution is not fully correct
-</para>
- <para>
-If the solution is not correct or the feature/enhancement does not work,
-it is the duty of the Verifier to reopen the issue.
-</para>
- </listitem>
- </itemizedlist>
-</para>
- <para>
-Skills:
-The verifier needs only to focus on that issue, how the problem in it
-is formulated.
-He doesn't need to know how it is actually solved.
-</para>
- </sect2>
</sect1>
<sect1 id="resolve_issue">
@@ -665,239 +583,54 @@
</orderedlist>
</sect1>
- <sect1 id="verify_resolved_fixed">
- <title>How to verify an Issue that is FIXED</title>
- <indexterm>
- <primary>Issues</primary>
- <secondary>Verifying Fixed</secondary>
- </indexterm>
- <indexterm>
- <primary>Issues</primary>
- <secondary>Verifying WORKSFORME</secondary>
- </indexterm>
- <indexterm>
- <primary>Verifying</primary>
- <secondary>Works for me Issues</secondary>
- </indexterm>
- <para>
-This can be performed by any member of the project (any role).
-There might be special skills involved but it differs widely depending
-on the nature of the Issue.
-</para>
- <para>
-If you are the Reporter of the issue, you Close the issue instead.
-</para>
- <para>
-Do the following:
-</para>
- <orderedlist>
- <listitem id="verify_resolved_fixed_start">
- <para>
-Pick any Issue that is RESOLVED/FIXED or WORKSFORME and that you have
-not raised, nor solved and that is included in a release
-(Target milestone set to a release available on the site).
-<ulink url="http://argouml.tigris.org/issues/buglist.cgi?component=argouml&issue_status=RESOLVED&resolution=FIXED&resolution=WORKSFORME">The list of all RESOLVED/FIXED and RESOLVED/WORKSFORME issues</ulink>.
-</para>
- </listitem>
- <listitem>
- <para>
-Run the specified release of ArgoUML.
-You can also use any later release.
-Use ArgoUML provided for downloads or
-through Java Web Start.
-</para>
- </listitem>
- <listitem>
- <para>
-Test the problem in the issue and verify that the problem is no longer
-there or the feature is provided.
-</para>
- </listitem>
- <listitem>
- <para>
-Do one of the following:
-</para>
- <itemizedlist>
- <listitem>
- <para>
-If the problem is gone or the feature is present, set the Issue
-Status to VERIFIED and
-add the version of the ArgoUML used for the test in in the comment.
- </para>
- <para> Remark: As an additional activity, the
- verifier may check if the manual needs to be adapted, and if
- so, may REOPEN the issue with an explanation text, and setting
- the correct subcomponent (Documentation & Help). </para>
- </listitem>
- <listitem>
- <para>
-If the problem is still there, the feature does not work, put the
-Issue in Status REOPENED with a description of what is still there, is
-still missing.
-Also state what version of ArgoUML was used for the test in the comment.
-</para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
-If you during this, have discovered other problems than the one
-stated in the Issue, create new Issues for those new problems
-according to the rule for creating Issues.
-</para>
- </listitem>
- <listitem>
- <para>
-Do this as many times as you like until there are no Issues left.
-</para>
- </listitem>
- </orderedlist>
- </sect1>
-
- <sect1 id="verify_resolved_invalid">
- <title>How to verify an Issue that is rejected</title>
- <indexterm>
- <primary>Issues</primary>
- <secondary>Resolving Rejected</secondary>
- </indexterm>
- <indexterm>
- <primary>Issues</primary>
- <secondary>Resolving INVALID</secondary>
- </indexterm>
- <indexterm>
- <primary>Issues</primary>
- <secondary>Resolving WONTFIX</secondary>
- </indexterm>
+ <sect1 id="close_verified_issue">
+ <title>How to Close an Issue</title>
<indexterm>
<primary>Issues</primary>
- <secondary>Resolving DUPLICATE</secondary>
- </indexterm>
- <indexterm>
- <primary>Resolving</primary>
- <secondary>Rejected Issues</secondary>
- </indexterm>
- <indexterm>
- <primary>Resolving</primary>
- <secondary>Invalid Issues</secondary>
- </indexterm>
- <indexterm>
- <primary>Resolving</primary>
- <secondary>WONTFIX Issues</secondary>
- </indexterm>
- <indexterm>
- <primary>Resolving</primary>
- <secondary>DUPLICATE Issues</secondary>
+ <secondary>Closing</secondary>
</indexterm>
<para>
-This can be performed by any member of the project (any role).
-There might be special skills involved but it differs widely depending
-on the nature of the Issue.
+This is an optional step performed by
+anyone that has personal interest in the issue.
+You need to be a member of the project (any role).
</para>
<para>
-If you are the Reporter of the issue, you Close the issue instead.
-</para>
- <para>
-Do the following:
+If this is not done, all issues will be summarily closed
+by the release responsible a while after the release.
</para>
<orderedlist>
- <listitem id="verify_resolved_invalid_start">
- <para>
-Pick any issue that is RESOLVED/(INVALID, WONTFIX, or DUPLICATE) that
-you have not raised nor solved.
-The chosen issue need not be connected to an available release.
-<ulink url="http://argouml.tigris.org/issues/buglist.cgi?component=argouml&issue_status=RESOLVED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE">The list of all RESOLVED/INVALID, RESOLVED/WONTFIX and RESOLVED/DUPLICATED issues</ulink>.
-</para>
- </listitem>
<listitem>
<para>
-Read through the description provided.
+Pick any Issue that is RESOLVED or VERIFIED
+(<ulink url="http://argouml.tigris.org/issues/buglist.cgi?component=argouml&issue_status=RESOLVED&issue_status=VERIFIED">
+all RESOLVED or VERIFIED issues
+</ulink>).
</para>
</listitem>
<listitem>
<para>
-Do one of the following:
-</para>
- <itemizedlist>
- <listitem>
- <para>
-If you agree with the statement and feel that the rejection
-is done for correct reasons,
-put the Issue in Status VERIFIED.
-</para>
- </listitem>
- <listitem>
- <para>
-If you don't agree, put the Issue in status REOPENED and give a
-description as to why you don't agree.
-</para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
-Do this as many times as you like until there are no Issues left.
-</para>
- </listitem>
- </orderedlist>
- </sect1>
-
- <sect1 id="close_verified_issue">
- <title>How to Close an Issue</title>
- <indexterm>
- <primary>Issues</primary>
- <secondary>Closing</secondary>
- </indexterm>
- <para>
-This is performed by the person that originally raised the Issue,
-by the QA responsible for that area,
-or by anyone for issues that are verified.
-You need to be a member of the project (any role).
-This can also be done by someone who would have raised the issue but
-did not because it was already present in Issuezilla.
-</para>
- <orderedlist>
- <listitem>
- <para>
-Pick any Issue that is Verified
-(<ulink url="http://argouml.tigris.org/issues/buglist.cgi?component=argouml&issue_status=VERIFIED">
-all VERIFIED issues
-</ulink>)
-or that you have raised or refrained from raising because
-somebody else already had written it.
+If you are satisfied, Close the issue.
</para>
</listitem>
<listitem>
<para>
-See that you are satisfied with the solution.
-This could involve reading through the resolution and
-starting the tool to verify it.
+If you are satisfied and want to support the closing but not confident
+enough to close the issue, verify the issue with your comments.
</para>
</listitem>
<listitem>
<para>
-Do one of the following:
-</para>
- <itemizedlist>
- <listitem>
- <para>
-If you are satisfied, Close the issue.
-</para>
- </listitem>
- <listitem>
- <para>
If you are not satisfied but the problem is solved as it is written in
the Issue, Close the issue and open a new Issue with
the rest of the problem.
</para>
- </listitem>
- <listitem>
- <para>
+ </listitem>
+ <listitem>
+ <para>
If you are not satisfied and the problem is not solved, put the Issue
in status REOPENED with a description on what you are not satisfied
with.
</para>
- </listitem>
- </itemizedlist>
</listitem>
</orderedlist>
</sect1>
@@ -1121,10 +854,6 @@
</listitem>
<listitem>
- <para>As reference points when verifying issues.</para>
- </listitem>
-
- <listitem>
<para>
As reference points and convenient downloads for persons working with modules.
</para>
@@ -1258,7 +987,7 @@
</listitem>
<listitem>
<para>
-Verify issues that are resolved.
+Test and close issues that are resolved to make sure the problem is gone.
</para>
</listitem>
<listitem>
@@ -1349,8 +1078,7 @@
<para>
Each release is a release candidate.
-When we have reached the point where no more issues are verified
-and we are confident that there are no more problems in this release
+When we are confident that there are no more problems in this release
we make the stable release without code changes compared to the last beta.
</para>
</listitem>
Modified: trunk/www/faqs/users.html
Url: http://argouml.tigris.org/source/browse/argouml/trunk/www/faqs/users.html?view=diff&rev=15717&p1=trunk/www/faqs/users.html&p2=trunk/www/faqs/users.html&r1=15716&r2=15717
==============================================================================
--- trunk/www/faqs/users.html (original)
+++ trunk/www/faqs/users.html 2008-09-12 22:47:03-0700
@@ -224,7 +224,6 @@
<li>Test it!</li>
<li>Find bugs!</li>
<li>Report bugs!</li>
-<li>Verify resolved issues!</li>
</ul>
<p>
Modified: trunk/www/members/project_members.html
Url: http://argouml.tigris.org/source/browse/argouml/trunk/www/members/project_members.html?view=diff&rev=15717&p1=trunk/www/members/project_members.html&p2=trunk/www/members/project_members.html&r1=15716&r2=15717
==============================================================================
--- trunk/www/members/project_members.html (original)
+++ trunk/www/members/project_members.html 2008-09-12 22:47:03-0700
@@ -526,6 +526,8 @@
<li>Doing the actual release work.</li>
+<li>Close RESOLVED or VERIFIED issues a time after the release.</li>
+
</ul>
</div>
Modified: trunk/www/project_bugs.html
Url: http://argouml.tigris.org/source/browse/argouml/trunk/www/project_bugs.html?view=diff&rev=15717&p1=trunk/www/project_bugs.html&p2=trunk/www/project_bugs.html&r1=15716&r2=15717
==============================================================================
--- trunk/www/project_bugs.html (original)
+++ trunk/www/project_bugs.html 2008-09-12 22:47:03-0700
@@ -91,7 +91,7 @@
something with your issue.
If nothing happens, you can solve the issue yourself and describe
the solution in the issue.
- When the issue is resolved and verified,
+ When the issue is resolved or verified,
close it after you have accepted the solution.
<p>
The life-cycle of issues and the roles of people handling them
@@ -158,8 +158,7 @@
future version of ArgoUML.
<p>
If you want to contribute even more to the project
-you could start solving and verifying issues.
-No java knowledge is needed for verifying issues.
+you could start solving issues.
For details read through the <a href="/dev.html">Developer Zone</a> and
especially the <a href="http://argouml-stats.tigris.org/documentation/defaulthtml/cookbook/">Cookbook</a>
<a href="http://argouml-stats.tigris.org/documentation/defaulthtml/cookbook/ch01s03.html">Section 1.3</a>.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.