openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1010077 [21/31] - in /websites/staging/ooo-site/trunk: cgi-bin/ content/ content/pl/ content/pl/Archive/ content/pl/Archive/apps/ content/pl/Archive/apps/hr5000/ content/pl/Archive/grafika/ content/pl/Archive/info/ content/pl/Archive/marke...
Date Sat, 08 Apr 2017 23:00:14 GMT
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsmanaging.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsmanaging.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsmanaging.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,215 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<TITLE>Managing project files with CVS</TITLE>
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+  <TR>
+    <SPAN CLASS="Header">Managing project files and directories with command line CVS</SPAN>
+<P>
+<SPAN CLASS="PlainText"><B>CVS tool documents: Index</B>
+<UL>
+<DL>
+<DT><A HREF="ddCVS.html">About source code version control with CVS</A>
+<DT><A HREF="ddCVS_cvsglossary.html">A version control glossary</A>
+<DD><A HREF="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</A>
+<DD><A HREF="ddCVS_cvscontributing.html">Contributing source code changes with CVS</A>
+<DD><B>You are here: Managing project files and directories with CVS
+<UL>
+  <LI><A HREF="#cvsrelease">Releasing files</A>
+  <LI><A HREF="#cvsremove">Removing files</A>
+  <LI><A HREF="#cvsrename&move">Renaming and moving files</A>
+  <LI><A HREF="#cvsimport">Importing existing source files</A>
+  <LI><A HREF="#cvsandrcs">CVS and RCS</A>
+  <LI><A HREF="#keywords">Using keywords</A>
+  <LI><A HREF="#aboutbranching">Tagging and branching</A></B>
+</UL>
+<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
+</DL>
+</UL>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="cvsrelease"></A><SPAN CLASS="InputHeader">Releasing files and directories</SPAN>
+<P>
+At certain point in a project's development cycle, managing your project's source repository invariably involves dealing with files and directories that have become deprecated or obsolete. The decision is made to abandon a certain piece of functionality within a module, for example. Or perhaps an change in infrastructure demands getting rid of some files and moving others. This section deals with several methods for dealing with such file management issues in CVS.
+<P>
+<I>Releasing</I> refers to a way of designating certain directories or modules that will no longer to be used in the project. The command to release is invoked within a working copy and effectively cancels cvs checkouts for the designated directories and their files. Unless these are expressly deleted, the files and directories actually remain intact within the repository, including all file revision history, but are no longer included in when working copies are checked out.
+<P>
+The command to release a file or directory is:
+<BLOCKQUOTE>
+<B>cvs rel filename</B> (or <B>/directory_name</B>)
+</BLOCKQUOTE>
+<P>
+<A HREF="http://www.gnu.org/manual/cvs/html_chapter/cvs_20.html#SEC122" TARGET="_new">More about releasing</A>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="cvsremove"></A><span class="InputHeader">Removing files</SPAN>
+<P>
+<I>Removing</I> is another way to get rid of files when you no longer want or need them to be part of the project's source repository. To do this, you must first delete the file from the working copy you have checked out on your local system.
+<P>
+Then, to remove a file from the shared repository, type: <BR>
+<BLOCKQUOTE>
+          <B>cvs remove filename</B>
+</BLOCKQUOTE>
+After you have removed one or more files, you must commit your changes. 
+<P>
+With &quot;<B>cvs remove</B>&quot (or &quot;<B>cvs rm</B>&quot), the old file is not completely eradicated but rather stored in CVS' so-called "attic" along with its complete revision history.
+<P>
+<A HREF="http://www.gnu.org/manual/cvs/html_chapter/cvs_12.html#SEC62" TARGET="_new">More about removing files</A><BR>
+<A HREF="http://cvsbook.red-bean.com/cvsbook.html#What_Happens_When_You_Remove_A_File" TARGET="_new">What happens when you remove a file</A>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="cvsrename&move"></A><SPAN CLASS="InputHeader">Renaming and moving files and directories</SPAN>
+
+<P>If you have imported some existing source code into your repository, you may have files and directories you want to rename or or move.
+
+<P>The best way to rename a file in your working copy involves a series of steps. Use:
+<BLOCKQUOTE>
+<B>cvs rm old_filename</B>
+</BLOCKQUOTE>
+to remove the old name, then 
+<BLOCKQUOTE>
+<B>cvs add new_filename</B> 
+</BLOCKQUOTE>
+and finally,
+<BLOCKQUOTE>
+<B>cvs commit new_filename</B>
+</BLOCKQUOTE>
+
+<P>
+There really is no specific way in CVS to remove or rename directories. However, you can produce that effect by creating a new directory, moving the files you need into it, removing unwanted files from the old directory, and then simply no longer using it. Later, you can "prune" these empty directories the next time you a check out a working copy by using:
+<BLOCKQUOTE>
+<B>cvs checkout -P</B>
+</BLOCKQUOTE>
+Another way to prune directories with no more files is to update with:
+<BLOCKQUOTE>
+<B>cvs update -dP</B>
+</BLOCKQUOTE>
+
+<P>
+<A HREF="http://www.gnu.org/manual/cvs/html_chapter/cvs_14.html#SEC67" TARGET="_new">More about moving and renaming files</A><BR>
+<A HREF="http://www.gnu.org/manual/cvs/html_chapter/cvs_15.html#SEC71" TARGET="_new">More about moving and renaming directories</A>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="cvsimport"></A><SPAN CLASS="InputHeader">Importing existing code?</SPAN>
+<P>
+If you have existing files to add to the project, you can import these into CVS using the following command:
+<BLOCKQUOTE>
+    <B>cvs import filename</B>
+</BLOCKQUOTE>
+
+<P>
+Importing allows you to add a lot of files at once, something like a super "cvs add." To import <I>all</I> existing directories and files, in your top level directory type:
+<P>
+<B>cvs import -m &quot;log message&quot projectname</B>
+<P>
+This creates the files and directories in the CVS repository for your project on this site. If you want to preserve these files and directories in their original state, you may want to tag or archive this set of original files before you or any other developers begin checking out working copies of project files.
+<P>
+If your existing files are already under versioning control -- either in another CVS repository or in a versioning different system such as RCS -- there is no automated method for importing existing files that retains file histories. Using the cvs import command, copying files over, or creating them as new files does not retain these histories.
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="cvsandrcs"></A><SPAN CLASS="InputHeader">CVS and RCS</SPAN>
+<P>
+If you're already familiar with RCS, both RCS and CVS use a similar format for storing the version control histories of individual files. But you should be aware of at least two critical differences in adapting CVS:
+<P>
+<UL>
+<LI>One of the central principals in RCS is file locking, which prevents other developers from checking out or modifying a file when you have checked it out. The benefit to file locking is that developers never have to deal with conflicting modifications within files. RCS protects files by only allowing them to be modified by one person at a time. Therefore, the drawback to RCS is: you can't commit your changes to a file while another developer has it checked out.
+<LI>The central tenant of CVS is to allow developers to check out, modify, and commit files concurrently, truly a benefit to projects with remote, geographically dispersed developers. The tradeoff is that on a CVS version controlled project, you can count on dealing with merge conflicts in files. The only method for resolving such conflicts is by hand-editing the file. Thus, project workflow with CVS ends up being a little different.
+</UL>
+<P>
+<A HREF="http://www.cvshome.org/cyclic/cyclic-pages/rcs.html" TARGET="_new">More about RCS and CVS</A>
+<P>
+
+<HR noShade SIZE=1>
+<A NAME="keywords"></A><SPAN CLASS="InputHeader">Keyword substitution</SPAN>
+<P>
+Keyword substitution (a.k.a keyword expansion) is an RCS holdover that may be useful to you as a developer. Keywords essentially let you embed version information permanently in source files. A string containing the full version information associated with a particular keyword is substituted whenever the file is subsequently revised. 
+<P>
+As an example, including:
+<BLOCKQUOTE>
+<B>$Author: mellonedain $</B>
+</BLOCKQUOTE>
+within the files permanently retains the login name of the user who checked in that revision.
+<P>Keyword substitution is a method for tracking file versions once the files are no longer part of a CVS repository. Keyword substitution can also be configured and suppressed.
+<P>
+<A HREF="http://cvshome.org/docs/manual/cvs_12.html#SEC98" TARGET="_new">More about keywords (including a list of common keywords)</A>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="aboutbranching"></A><SPAN CLASS="InputHeader">Tagging and branching </SPAN>
+<P>
+The CVS repository for your project hosted on this site supports branching and tagging your source files. At certain points in your project, you may want to enable development work in your project to progress in more than one direction simultaneously. Instead of maintaining a singular, linear path of development, CVS branching provides a way to divert or split the source tree for ancillary development activities without impacting progress of the project's primary effort. Examples of reasons to branch include:
+<UL>
+<LI>to distinguish a clearly defined set of functionality in project source files for QA and testing, or
+<LI>when you want to try an experiment such as added features or functionality without affecting the project's progress.
+</UL>
+<P>
+Tagging is included in the discussion about branching because the two operations are used in conjunction. Tagging allows you to "take a snapshot" of the overall project's state at a certain point in time, for example, to preserve a build with some particular characteristic. Because CVS manages individual file revisions, tagging is an important option for benchmarking the overall state of project source code. Files included in a tag will most likely be at different points in their respective revision numbering.
+<P>
+The critical difference between branching and tagging is the reason they are complimentary operations:
+<BLOCKQUOTE>
+Branching affects <I>individual files'</I> revision numbering, whereas tagging assigns a common identifying marker <I>across all project files</I> at a fixed point in time.
+</BLOCKQUOTE>
+So, for example, project files are often tagged at the point where branches are created.
+<P>
+Ultimately, branches in your project with successful outcomes get incorporated or merged back in to the main development trunk. When that happens -- and it may occur repeatedly on large or long-term projects -- identifying the point where this merge occurs is another reason to create a tag.
+<P>
+<A NAME="cvstag"></A>To tag project files, type:
+<BLOCKQUOTE>
+<B>cvs tag unique_tag_name</B>
+</BLOCKQUOTE>
+<P>
+Your tag name can be a release name or date, a product version identifier, or whatever you choose.
+<P>
+<A NAME="cvsbranch"></A>To create a branch, type:
+<BLOCKQUOTE>
+<B>cvs tag -b unique_tag_name </B>
+</BLOCKQUOTE>
+<P>
+Branching and tagging are complex topics with many considerations and  options. You can find more comprehensive information and instructions in the following resources:
+<P> 
+<UL>
+<DL>
+<DT><LI>cvshome.org: <A HREF="http://www.cvshome.org/docs/manual/cvs_4.html#SEC48" TARGET="_new">"More about branching and tagging"</A><BR>
+<DT><LI>The Cederqvist Manual: <A HREF="http://www.gnu.org/manual/cvs/html_chapter/cvs_8.html#SEC50" TARGET="_new">"Branches"</A><BR>
+<DT><LI><I>Open Source Development with CVS</I>:<BR>
+<DD><A HREF="http://cvsbook.red-bean.com/cvsbook.html#Marking_A_Moment_In_Time__Tags_" TARGET="_new">"Marking A Moment In Time (Tags)"</A>
+<DD><A HREF="http://cvsbook.red-bean.com/cvsbook.html#Branches" TARGET="_new">"Branches"</A>
+</UL>
+</DL>
+<P>
+
+<HR NOSHADE SIZE=1>
+<A HREF="/servlets/HelpTOC">Back to main Help index</A></P></SPAN>
+
+</SPAN> 
+</TR>
+</TABLE>
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsmanaging.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsmanaging.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsmanaging.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,214 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Managing project files and directories</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="ddcvscvsmanaging">
+   <h2>Managing project files and directories with command line CVS</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      <a href="/nonav/docs/ddCVS.html">About source code version control with CVS</a> 
+
+      <ul>
+       <li><a href="/nonav/docs/ddCVS_cvsglossary.html">A version control glossary</a></li>
+
+       <li><a href="/nonav/docs/ddUsingCVS_command-line.html">Using command-line CVS to access project source files</a></li>
+
+       <li><a href="/nonav/docs/ddCVS_cvscontributing.html">Contributing source code changes with CVS</a></li>
+
+       <li>
+        Managing project files and directories with CVS 
+
+        <ul>
+         <li><a href="#cvsrelease">Releasing files</a></li>
+
+         <li><a href="#cvsremove">Removing files</a></li>
+
+         <li><a href="#cvsrenameandmove">Renaming and moving files</a></li>
+
+         <li><a href="#cvsimport">Importing existing source files</a></li>
+
+         <li><a href="#cvsandrcs">CVS and RCS</a></li>
+
+         <li><a href="#keywords">Using keywords</a></li>
+
+         <li><a href="#aboutbranching">Tagging and branching</a></li>
+        </ul>
+       </li>
+      </ul>
+     </li>
+    </ul>
+   </div>
+
+   <h3><a id="cvsrelease" name="cvsrelease">Releasing files and directories</a></h3>
+
+   <p>At certain point in a project's development cycle, managing your project's source repository invariably involves dealing with files and directories that have become deprecated or obsolete. The decision is made to abandon a certain piece of functionality within a module, for example. Or perhaps an change in infrastructure demands getting rid of some files and moving others. This section deals with several methods for dealing with such file management issues in CVS.</p>
+
+   <p><i>Releasing</i> refers to a way of designating certain directories or modules that will no longer to be used in the project. The command to release is invoked within a working copy and effectively cancels cvs checkouts for the designated directories and their files. Unless these are expressly deleted, the files and directories actually remain intact within the repository, including all file revision history, but are no longer included in when working copies are checked out.</p>
+
+   <p>The command to release a file or directory is:</p>
+
+   <p><code>cvs rel filename</code> (or <code>/directory_name</code>)</p>
+
+   <p><a href="http://www.gnu.org/manual/cvs/html_chapter/cvs_20.html#SEC122">More about releasing</a></p>
+
+   <h3><a id="cvsremove" name="cvsremove">Removing files</a></h3>
+
+   <p><i>Removing</i> is another way to get rid of files when you no longer want or need them to be part of the project's source repository. To do this, you must first delete the file from the working copy you have checked out on your local system.</p>
+
+   <p>Then, to remove a file from the shared repository, type:</p>
+
+   <p><code>cvs remove filename</code></p>
+
+   <p>After you have removed one or more files, you must commit your changes.</p>
+
+   <p>With "<b>cvs remove</b>" (or "<b>cvs rm</b>"), the old file is not completely eradicated but rather stored in CVS' so-called "attic" along with its complete revision history.</p>
+
+   <ul>
+    <li><a href="http://www.gnu.org/manual/cvs/html_chapter/cvs_12.html#SEC62">More about removing files</a></li>
+
+    <li><a href="http://cvsbook.red-bean.com/cvsbook.html#What_Happens_When_You_Remove_A_File">What happens when you remove a file</a></li>
+   </ul>
+
+   <h3><a id="cvsrenameandmove" name="cvsrenameandmove">Renaming and moving files and directories</a></h3>
+
+   <p>If you have imported some existing source code into your repository, you may have files and directories you want to rename or or move.</p>
+
+   <p>The best way to rename a file in your working copy involves a series of steps. Use:</p>
+
+   <p><code>cvs rm old_filename</code></p>
+
+   <p>to remove the old name, then</p>
+
+   <p><code>cvs add new_filename</code></p>
+
+   <p>and finally,</p>
+
+   <p><code>cvs commit new_filename</code></p>
+
+   <p>There really is no specific way in CVS to remove or rename directories. However, you can produce that effect by creating a new directory, moving the files you need into it, removing unwanted files from the old directory, and then simply no longer using it. Later, you can "prune" these empty directories the next time you a check out a working copy by using:</p>
+
+   <p><code>cvs checkout -P</code></p>
+
+   <p>Another way to prune directories with no more files is to update with:</p>
+
+   <p><code>cvs update -dP</code></p>
+
+   <ul>
+    <li><a href="http://www.gnu.org/manual/cvs/html_chapter/cvs_14.html#SEC67">More about moving and renaming files</a></li>
+
+    <li><a href="http://www.gnu.org/manual/cvs/html_chapter/cvs_15.html#SEC71">More about moving and renaming directories</a></li>
+   </ul>
+
+   <h3><a id="cvsimport" name="cvsimport">Importing existing code?</a></h3>
+
+   <p>If you have existing files to add to the project, you can import these into CVS using the following command:</p>
+
+   <p><code>cvs import filename</code></p>
+
+   <p>Importing allows you to add a lot of files at once, something like a super "cvs add." To import <i>all</i> existing directories and files, in your top level directory type:</p>
+
+   <p><code>cvs import -m "log message" projectname</code></p>
+
+   <p>This creates the files and directories in the CVS repository for your project on this site. If you want to preserve these files and directories in their original state, you may want to tag or archive this set of original files before you or any other developers begin checking out working copies of project files.</p>
+
+   <p>If your existing files are already under versioning control -- either in another CVS repository or in a versioning different system such as RCS -- there is no automated method for importing existing files that retains file histories. Using the cvs import command, copying files over, or creating them as new files does not retain these histories.</p>
+
+   <h3><a id="cvsandrcs" name="cvsandrcs">CVS and RCS</a></h3>
+
+   <p>If you're already familiar with RCS, both RCS and CVS use a similar format for storing the version control histories of individual files. But you should be aware of at least two critical differences in adapting CVS:</p>
+
+   <ul>
+    <li>One of the central principals in RCS is file locking, which prevents other developers from checking out or modifying a file when you have checked it out. The benefit to file locking is that developers never have to deal with conflicting modifications within files. RCS protects files by only allowing them to be modified by one person at a time. Therefore, the drawback to RCS is: you can't commit your changes to a file while another developer has it checked out.</li>
+
+    <li>The central tenant of CVS is to allow developers to check out, modify, and commit files concurrently, truly a benefit to projects with remote, geographically dispersed developers. The tradeoff is that on a CVS version controlled project, you can count on dealing with merge conflicts in files. The only method for resolving such conflicts is by hand-editing the file. Thus, project workflow with CVS ends up being a little different.</li>
+   </ul>
+
+   <p><a href="http://www.cvshome.org/cyclic/cyclic-pages/rcs.html">More about RCS and CVS</a></p>
+
+   <h3><a id="keywords" name="keywords">Keyword substitution</a></h3>
+
+   <p>Keyword substitution (a.k.a keyword expansion) is an RCS holdover that may be useful to you as a developer. Keywords essentially let you embed version information permanently in source files. A string containing the full version information associated with a particular keyword is substituted whenever the file is subsequently revised.</p>
+
+   <p>As an example, including:</p>
+
+   <p><code>$Author: mellonedain $</code></p>
+
+   <p>within the files permanently retains the login name of the user who checked in that revision.</p>
+
+   <p>Keyword substitution is a method for tracking file versions once the files are no longer part of a CVS repository. Keyword substitution can also be configured and suppressed.</p>
+
+   <p><a href="http://cvshome.org/docs/manual/cvs_12.html#SEC98">More about keywords (including a list of common keywords)</a></p>
+
+   <h3><a id="aboutbranching" name="aboutbranching">Tagging and branching</a></h3>
+
+   <p>The CVS repository for your project hosted on this site supports branching and tagging your source files. At certain points in your project, you may want to enable development work in your project to progress in more than one direction simultaneously. Instead of maintaining a singular, linear path of development, CVS branching provides a way to divert or split the source tree for ancillary development activities without impacting progress of the project's primary effort. Examples of reasons to branch include:</p>
+
+   <ul>
+    <li>to distinguish a clearly defined set of functionality in project source files for QA and testing, or</li>
+
+    <li>when you want to try an experiment such as added features or functionality without affecting the project's progress.</li>
+   </ul>
+
+   <p>Tagging is included in the discussion about branching because the two operations are used in conjunction. Tagging allows you to "take a snapshot" of the overall project's state at a certain point in time, for example, to preserve a build with some particular characteristic. Because CVS manages individual file revisions, tagging is an important option for benchmarking the overall state of project source code. Files included in a tag will most likely be at different points in their respective revision numbering.</p>
+
+   <p>The critical difference between branching and tagging is the reason they are complimentary operations:</p>
+
+   <p>Branching affects <i>individual files'</i> revision numbering, whereas tagging assigns a common identifying marker <i>across all project files</i> at a fixed point in time.</p>
+
+   <p>So, for example, project files are often tagged at the point where branches are created.</p>
+
+   <p>Ultimately, branches in your project with successful outcomes get incorporated or merged back in to the main development trunk. When that happens -- and it may occur repeatedly on large or long-term projects -- identifying the point where this merge occurs is another reason to create a tag.</p>
+
+   <p><a id="cvstag" name="cvstag">To tag project files, type:</a></p>
+
+   <p><code>cvs tag unique_tag_name</code></p>
+
+   <p>Your tag name can be a release name or date, a product version identifier, or whatever you choose.</p>
+
+   <p><a id="cvsbranch" name="cvsbranch">To create a branch, type:</a></p>
+
+   <p><code>cvs tag -b unique_tag_name</code></p>
+
+   <p>Branching and tagging are complex topics with many considerations and options. You can find more comprehensive information and instructions in the following resources:</p>
+
+   <ul>
+    <li>cvshome.org: <a href="http://www.cvshome.org/docs/manual/cvs_4.html#SEC48">"More about branching and tagging"</a></li>
+
+    <li>The Cederqvist Manual: <a href="http://www.gnu.org/manual/cvs/html_chapter/cvs_8.html#SEC50">"Branches"</a></li>
+
+    <li>
+     Open Source Development with CVS: 
+
+     <ul>
+      <li><a href="http://cvsbook.red-bean.com/cvsbook.html#Marking_A_Moment_In_Time__Tags_">"Marking A Moment In Time (Tags)"</a></li>
+
+      <li><a href="http://cvsbook.red-bean.com/cvsbook.html#Branches">"Branches"</a></li>
+     </ul>
+    </li>
+   </ul>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsprimer.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsprimer.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsprimer.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,125 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<TITLE>Version Control Primer</TITLE>
+
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+  <TR>
+    <TD class="Header" nowrap>A version control primer</TD>  
+  </TR>
+</TABLE>
+
+<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
+  <TR>
+    <TD class=PlainText>
+     <P>A version control system maintains an organized set of all the
+     versions of files that are made over time. Version control
+     systems allow people to go back to previous versions, and to
+     compare any two versions to see what changes were made between
+     them. In this way, version control keeps a historically accurate
+     (and retrievable!) log of a file's evolution. More importantly,
+     version control systems help several people (even in
+     geographically disparate locations) work together on a
+     development project over the Internet or private network to make
+     changes to the same file over time.
+
+     <P><span class="InputHeader">Key concepts in version control:</span>
+     <DL>
+      <DT><span class="PlainTextBold">Repository</span>: 
+      <DD>a shared database the the complete version history of all
+      files under version control.
+
+     <P>
+      <DT><span class="PlainTextBold">Workspace</span>: 
+      <DD>a copy of the files you want to edit on your local hard disk
+      or Unix user account. When you edit files in your workspace,
+      they will become out of sync with the repository. That's
+      progress!  Then you need to get your changes back into the
+      repository so that everyone else can see them.
+
+     <P>
+      <DT><span class="PlainTextBold">Checking out a file or directory</span>: 
+      <DD>this copies a version (usually the latest version) of a file
+      from the repository to your workspace. When you check out a
+      directory, you check out all files and subdirectories under it.
+
+     <P>
+      <DT><span class="PlainTextBold">Checking in a file or directory</span>: 
+      <DD>this copies your working directory back into the repository
+      as a new version.
+
+     <P>
+      <DT><span class="PlainTextBold">Committing a file or directory</span>: 
+      <DD>is the same as checking it in. Often version control users
+      will say that the have "committed a change"; this means that
+      they made changes and committed these back to the repository.
+
+     <P>
+      <DT><span class="PlainTextBold">Version</span>: 
+      <DD>a numbered draft of a file, e.g., 1.1, 1.2, 1.3, 1.4, 2.0,
+      2.1. Each time you edit a file and commit it back to the
+      repository, its version number increases. You can change the
+      first digit of the number any time you like.
+
+     <P>
+      <DT><span class="PlainTextBold">Conflict</span>: 
+      <DD>When two people make changes to the same file at the same
+      time, their work may conflict. There are two ways to address
+      conflicts: locks and merging.
+
+     <P>
+      <DT><span class="PlainTextBold">Locks</span>: 
+     <DD>one strategy for managing conflicts in version control is to
+     lock files so that only one person can check out a read-write
+     copy at a time. Other users can only get read-only copies. This
+     prevents two people from ever working on the same file at the
+     same time. It is safe, but not very efficient in practice. Also,
+     if one person locks a file and then leaves for the day or the
+     week, no one else can work with that file, so they are needlessly
+     blocked. 
+
+    <P> <DT><span class="PlainTextBold">Merging</span>:
+      <DD>another strategy for managing conflict is to let multiple
+      people work at the same time (with no locks) and then try to
+      merge their results into one combined version. This is closer to
+      the way that intelligent people tend to work together in
+      parallel if they had no version control tools. Merging works
+      well when two sets of changes can be combined, and poorly when
+      it is impossible to combine changes. CVS uses merging.
+     </DL>
+
+     <P>More information: <A
+     HREF="http://www.cvshome.org/new_users.html">CVS for New
+     Users</A> (an article)
+
+<HR noShade SIZE=1>
+<a href="Help.html">Back to main Help index</a></p></span>
+
+    </TD>
+  </TR>
+</TABLE>
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsprimer.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsprimer.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddCVS_cvsprimer.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,70 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Version control primer</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="ddcvscvsprimer">
+   <h2>A version control primer</h2>
+
+   <p>A version control system maintains an organized set of all the versions of files that are made over time. Version control systems allow people to go back to previous versions, and to compare any two versions to see what changes were made between them. In this way, version control keeps a historically accurate (and retrievable!) log of a file's evolution. More importantly, version control systems help several people (even in geographically disparate locations) work together on a development project over the Internet or private network to make changes to the same file over time.</p>
+
+   <h3>Key concepts in version control:</h3>
+
+   <dl>
+    <dt>Repository:</dt>
+
+    <dd>a shared database the the complete version history of all files under version control.</dd>
+
+    <dt>Workspace:</dt>
+
+    <dd>a copy of the files you want to edit on your local hard disk or Unix user account. When you edit files in your workspace, they will become out of sync with the repository. That's progress! Then you need to get your changes back into the repository so that everyone else can see them.</dd>
+
+    <dt>Checking out a file or directory:</dt>
+
+    <dd>this copies a version (usually the latest version) of a file from the repository to your workspace. When you check out a directory, you check out all files and subdirectories under it.</dd>
+
+    <dt>Checking in a file or directory:</dt>
+
+    <dd>this copies your working directory back into the repository as a new version.</dd>
+
+    <dt>Committing a file or directory:</dt>
+
+    <dd>is the same as checking it in. Often version control users will say that the have "committed a change"; this means that they made changes and committed these back to the repository.</dd>
+
+    <dt>Version:</dt>
+
+    <dd>a numbered draft of a file, e.g., 1.1, 1.2, 1.3, 1.4, 2.0, 2.1. Each time you edit a file and commit it back to the repository, its version number increases. You can change the first digit of the number any time you like.</dd>
+
+    <dt>Conflict:</dt>
+
+    <dd>When two people make changes to the same file at the same time, their work may conflict. There are two ways to address conflicts: locks and merging.</dd>
+
+    <dt>Locks:</dt>
+
+    <dd>one strategy for managing conflicts in version control is to lock files so that only one person can check out a read-write copy at a time. Other users can only get read-only copies. This prevents two people from ever working on the same file at the same time. It is safe, but not very efficient in practice. Also, if one person locks a file and then leaves for the day or the week, no one else can work with that file, so they are needlessly blocked.</dd>
+
+    <dt>Merging:</dt>
+
+    <dd>another strategy for managing conflict is to let multiple people work at the same time (with no locks) and then try to merge their results into one combined version. This is closer to the way that intelligent people tend to work together in parallel if they had no version control tools. Merging works well when two sets of changes can be combined, and poorly when it is impossible to combine changes. CVS uses merging.</dd>
+   </dl>
+
+   <p>More information: <a href="http://www.cvshome.org/new_users.html">CVS for New Users</a> (an article)</p>
+
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_EnterModify.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_EnterModify.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_EnterModify.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,280 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Entering and Modifying Issues</title>
+
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+
+    <span class="Header" nowrap>Entering and modifying issues</span>  
+
+<p>
+<span class="PlainText"><strong>More help on IssueZilla: Index</strong>
+<p>
+
+<ul>
+<dl>
+<dt><a href="ProjectIssues.html">Project issue tracking</a>
+  <dd><strong>You are here: Entering and modifying issues</a>
+    <ul>
+    <li><a href="#enterissue">Entering a new issue</a>
+    <li><a href="#entryfields">Issue entry field descriptions</a>
+      <li><a href="#editissue">Viewing and modifying issues</a>
+    </ul></strong>
+  <dd><a href="ddIssues_Query.html">Querying and tracking issues</a>
+  <dd><a href="ddIssues_Reports.html">Generating status reports about project issues</a>
+<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
+</dl>
+</ul>
+
+<span class="PlainText">
+  
+<p>
+<strong>More help about issues</strong>
+<ul>
+  <dl>  
+   <dt><a href="issuewritinghelp.html">Issue writing guidelines</a><br>
+   <dt><a href="contributing_patches.html">Contributing patches</a>
+   <dt><a href="issue_lifecycle.html">The lifecycle of an issue</a><br>
+   <dt><a href="issues_unconfirmedhelp.html">Understanding the UNCONFIRMED issue state</a>
+  </dl> 
+</ul>
+     <p>
+<hr noshade size=1>
+<a name="enterissue"></a><span class="InputHeader">Entering a new issue</span>
+     <ul>
+      <li>Choose the appropriate link in the "Enter An Issue" section of the Project Issues page. Once you have invoked IssueZilla, a secondary "Issue Tracking" tool bar appears on this page and you can also enter an issue by clicking the <i>New</i> link in the IssueZilla tool bar.
+<p>
+      <li>Choose the appropriate project component.
+<p>
+      <li>Selected the appropriate options or input information for each field before using the <i>Commit</i> button to enter your issue.
+     </ul>
+     <p>
+      The information you provide here significantly determines the effectiveness of your issue reports and the response to them. Descriptions for each of these fields follow to help you optimize your issue reports.
+<p>
+<b>Important note</b>: When you first enter a new issue, you cannot set a target milestone date, nor can you assign dependencies (flag other issues that depend on this new issue or those that it depends upon). To designate a target milestone or dependencies, you must first submit the new issue successfully, then retrieve it to access fields for setting a target milestone and creating dependencies.
+<p>
+
+<hr noshade size=1>
+<p>
+<a name="entryfields"></a><span class="InputHeader">Issue entry field descriptions</span>
+     <dl>
+      <dt><span class="InputHeader">Version</span>
+      <dd>The release in which you identified this issue or found the defect. 
+      <p>
+      <dt><span class="InputHeader">Component/Sub Component</span>
+      <dd>Identify area within the project that this issue is associated with. Only one selection is permitted.
+      <p>
+      <dt><a name="rep_platform"><span class="InputHeader">Platform</span></a>
+      <dd>This corresponds to <i>your</i> hardware platform when you are reporting a defect. Options include:
+      <ul>
+       <li> All (happens on all platform; cross-platform issue)
+       <li> Macintosh
+       <li> PC
+       <li> Sun
+       <li> HP
+      </ul>
+      <b>Note:</b> Selecting the option "All" does not select issues assigned against all platforms.  It merely selects issues that <i>occur</i> on all platforms.
+      <p>
+      <dt><a name="op_sys"><span class="InputHeader">Operating System</span></a>
+       <dd>This is the operating system against which the issue is being reported. Legal operating systems include:
+      <ul>
+       <li> All (happens on all operating systems, making this a cross-platform issue)
+       <li> Windows 95
+       <li> Mac System 8.0
+       <li> Linux
+      </ul>
+
+       Note that the operating system implies the platform, but not always. For example, Linux can run on PC, Macintosh, and others.
+      <p>
+      <dt><a name="priority"><span class="InputHeader">Priority</span></a>
+       <dd>This field let you assign a level of importance to help determine when this issue should be addressed relative to other issues. This field is utilized by the programmers/engineers to prioritize their work.
+      <p>
+      <table>
+       <tr><th>P1</th><td>Most important
+       <tr><th>P2</th><td>
+       <tr><th>P3</th><td>
+       <tr><th>P4</th><td>
+       <tr><th>P5</th><td>Least important
+      </table>
+      <p>
+      <dt><a name="issue_type"><span class="InputHeader">Issue Type</span></a>
+      <blockquote>
+       <p><b><i>Defect</i></b> is a problem with an existing feature that is either not developed to spec or does not work as designed. These are often referred to as "bugs."
+       <p><b><i>Enhancement</i></b> is an improvement to an existing feature.
+       <p><b><i>Feature</i></b> is an addition to the software to add a piece of functionality that does not yet exist.
+       <p><b><i>Task</i></b> is an activity to be done on behalf or in support of a feature or enhancement. Tasks do not typically require direct changes to the code base.
+     <p><b><i>Patch</i></b> is a special kind of issue, a section of code to be applied or attached to existing software, often to fix a defect.
+      </blockquote>
+      <p>
+
+      <dt><span class="InputHeader">Initial state</span>
+       <dd>Newly entered issues are either "new" or "unconfirmed." Marking an issue <a  href="/docs/issues_unconfirmedhelp.html">unconfirmed</a> means you have not yet determined whether it is true or valid. Read more about "state" in the <a href="issue_lifecycle.html">lifecycle of an issue</a>.
+
+
+       <p>
+       <dt><a name="assigned_to"><span class="InputHeader">Assigned To</span></a>
+        <dd>Enter the email address of the one individual who is in charge of resolving the issue. If this field is left blank, the issue by default is assigned to the component/sub component owner. Every time this field changes, the status changes to <b>NEW</b> to make it visible in the assignee's list of issues.
+       <dt><p><span class="InputHeader">Cc:</span>
+    <dd>Add email addresses of other individuals who need email notification when this issue changes status or when there is other activity on this issue. Delimit multiple email addressees by single spaces only -- no commas or semi-colons are necessary.
+       <p>Note: Assign cc addresses sparingly. Project participants whose interest or involvement in this issue is peripheral should be encouraged to use IssueZilla to check and track issues rather than to rely on automatic email notification.
+
+       <p>
+       <dt><span class="InputHeader">URL</span>
+        <dd>How to use this field depends on the issue type:
+       <p>
+       <ul>
+        <li>For defects, URL should lead to a fairly stable system where the the problem is obvious or can be easily reproduced.
+        <li>For enhancements, URL should provide details pertaining to the improvement, such as mockups.
+        <li>For features, URL should link to any web-based form of material explaining the improvement such as mockups or design specs.
+        <li>For tasks, URL is optional and may include linking to the associated feature or enhancement.
+       </ul>
+       <p>
+       <dt><span class="InputHeader">Summary</span>
+        <dd>A terse, specific statement to describe this issue. This should a few unique, self-explanatory words to identify this issue easily in reports and short lists. Limiting your entry to the width of the field is best for the columnar display of query results.
+       <p>
+       <dt><span class="InputHeader">Description</span>
+        <dd>Provide a full description of the issue including any pertinent history or activity around this issue. Because this field is additive, it serves as the knowledge base and means of communicating through this issue's life cycle. Other project participants view and add comments or information using this field.
+       <p>
+     </dl><span class="InputHeader">After completing all necessary fields: </span>
+     <p>
+     <blockquote>
+      <i>Commit</i> enters this issue into the project's issue database.
+      <p><i>Reset</i> returns all field values to their default or blank settings.
+      <p><i>Remember values as bookmark template</i> lets you save your input settings to save keystrokes when entering multiple issues for the same project component.
+    </blockquote>
+
+    <p>For more information about entering issues into IssueZilla, see also <a href="issuewritinghelp.html">Issue Writing Guidelines</a>.
+<p>
+
+<hr noshade size=1>
+<a name="editissue"><span class="InputHeader">Viewing and modifying issues</span></a>
+
+    <p>Existing issues may be accessed in two different ways:
+    <ul>
+     <li>Entering a specific issue number in the "Find" field located in the IssueZilla tool bar displays the "Issue View" page. 
+     <li>Querying for issues either by clicking the "Query database" button in the Project Issues page, or by clicking the "Query" link in the IssueZilla tool bar displays an "Issue List" page of your results. (See <a href="ddIssues_Query.html">Querying and tracking issues</a>.)
+    </ul>
+
+    <p>The Issue View page is similar to the Issue Entry page and contains many of the same fields, but there are several important additions:
+
+    <p>
+    <dl>
+     <dt><span class="InputHeader">Target Milestone</span>
+      <dd>If your project has designated milestones, this field can be used to associated issues with those milestones, such as version releases. A milestone plan enumerates when different features are expected to be completed. If an issue has a target date or version release, this means the work on this issue must be completed by that date. This field should only be set or changed by the person responsible for the issue. 
+     <p>
+
+     <dt><span class="InputHeader">Add/Remove CC:</span>
+      <dd>You can add additional email addresses to this issue to alert other project members when activity occurs on this issue. If you are adding multiple addresses, delimit these with single spaces; do not use commas or semi-colons. You can also <i>remove</i> one or more email address listed by selecting it and checking the "Remove selected Cc's" box below.
+     <p>
+     <dt><span class="InputHeader">QA Contact</span>
+      <dd>This field should contain an email address or alias for the person(s) responsible for quality control of this issue.
+     <p>
+
+     <dt><span class="InputHeader">URL</span>
+      <dd>If this field is populated, clicking the field label links directly to the designated URL.
+     <p>
+
+     <dt><span class="InputHeader">Status Whiteboard</span>
+      <dd>The purpose of this generic field can be user-defined and project-specific. (In BugZilla, this field is used for writing short, one-line notes about the bug.)
+     <p>
+
+     <dt><span class="InputHeader">Attachments</span>
+      <dd>Adding attachment to an issue can be very useful. For defects, appending test cases, screen shots and/or editor logs to the issue can help pinpoint the problem to help the developer reproduce it.
+
+     <p> <p>For features, enhancements, and tasks, you can attach screen shots, mockups, and other files to provide supplemental information to illustrate the issue.
+  <p>You can also used this field to attach a patch related to the issue when appropriate. Read more about <a href="contributing_patches.html">contributing patches</a>.
+    
+     <p>
+     <dt><span class="InputHeader">Dependencies</span>
+      <dd>When an issue can't be addressed until one or more other issues are resolved, these are dependencies. Each issue can have other issues it depends upon , as well as issues that depend upon it, that is, other issues that this issue "blocks" while being unresolved. The links next to these fields display a tree and graph illustrating the dependencies associated with the issue currently being viewed.
+     <p>
+
+
+   <dt><span class="InputHeader">Vote for this issue</span> 
+      <dd>
+<!-- (adapted from bugzilla.mozilla.org's "Bugzilla Voting" page) -->
+
+IssueZilla's "voting" feature allows project members to have a certain number of votes in their project to use toward issues. Project owners set the number of votes allowed per issue, as well as the number of votes allowed per member. Some projects/components may not allow any, which means you can't vote on those issues at all. Your vote indicates which issues you believe are the most important to be addressed. 
+     <p>
+You may vote for the same bug more than once, however, you have a limited number of total votes allocated to you. You can either vote once for many issues, or use multiple votes for a fewer issues that you think are particularly critical.
+     <p>
+If an issue has received votes, the total number appears next to "Votes for this issue", or "0" if no votes have been logged. Clicking on this number displays the Show Votes page. If there are votes, names and their associated number of votes are listed.
+     <p>
+To view a list of issues that have received votes, use the IssueZilla Query page, and enter the numeral "1" in the "At least ___ votes" field. This returns issues in your query results with at least one vote.
+
+     <p>To vote for an issue: 
+     <ul>
+      <li>Open the issue (using the "Find" link in the tool bar or by clicking the issue from a list or report).
+      <li>Click on the "Vote for this issue" link just above the "Additional Comments" field. (If no such link appears, then voting may not be allowed for this issue's project/component.) 
+      <li>Indicate the number of votes you want to log for this issue. This page also displays how many votes you've given to other bugs, allowing you may reallocate your votes as necessary.
+      <li>You receive automatic email notification anytime changes occur on issues you have voted for. 
+      <li>You may review your votes at any time by clicking the "Change your password or preferences" link in the IssueZilla tool bar or at the bottom of the query page.
+     </ul>
+     <p>
+What's the purpose of this voting feature? Read about the important role of <a href="http://www.tigris.org/editorial/safetynet.html" target="_new">consensus voting in open source projects</a>.
+     <p>
+
+     <dt><span class="InputHeader">Groups</span>
+      <dd>If one or more drop boxes appear identifying project-defined groups to be included in or excluded from viewing an issue, this indicates that the project/component owner has created groups within the project. You should contact this person to determine how to use these fields.
+     <p>
+
+     <dt><span class="InputHeader">Leave as NEW</span>
+      <dd>If you are viewing an issue with the status NEW but it is not assigned to you, leave this default as checked. When the issue <i>is</i> assigned to you, you should accept it by changing its status to "Started."
+     <p>
+
+     <dt><span class="InputHeader">Resolve issue</span> 
+      <dd>Once an issue is resolved, this is where to designate the type of resolution. Changing an issue to "Resolved" means that as far as the assignee is concerned, this issue is completed. <a href="issue_lifecycle.html#resolvedissues">Read more</a> about the multiple options in this field's pull-down menu. <b>Note: Changing an issue's status to FIXED signals all other project members that any source file changes associated with this issue have been checked into the CVS repository.</b>
+     <p>
+
+     <dt><span class="InputHeader">Reassign</span>
+      <dd>The person responsible for the issue can be changed here by entering a new email address, or reassigned to the component/sub component owner. 
+     <p>
+
+     <dt><span class="InputHeader">View Issue Activity</span>
+      <dd>This link displays a snapshot page of changes made to an issue.
+     <p>
+
+     <dt><span class="InputHeader">Format For Printing</span>
+      <dd>This links redisplays the Issue View in a format for printing out. 
+
+     <p>
+     <dt><span class="InputHeader">Commit</span>
+      <dd>This button saves any modifications made to this issue. <b>Caution! When viewing an issue, the "Enter" key works like the <i>Commit</i> button. Any modifications you may have made (accidentally or otherwise) are saved and the issue's assignee and cc list receive email notification of activity on this issue.</b>
+
+     <p><b><i>To exit out of viewing this issue without making any changes</i></b>, use the links at the top of this page or in the IssueZilla tool bar to view other issues, or the <i>Back</i> button in your browser. Even when you have changed fields, as long as you do not use the <i>Commit</i> button or the "Enter" key, the issue remains unchanged in the database.
+     <p>
+
+     <dt><span class="InputHeader">Reset</span>
+      <dd>Returns all fields to their <i>previously committed</i> values.
+    </dl>
+<p>
+
+<hr noshade size=1>
+<a href="ProjectIssues.html">Back to Project Issues help</a><br>
+<a href="/servlets/HelpTOC">Back to main Help index</a></p></span>
+</span>
+
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_EnterModify.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_EnterModify.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_EnterModify.html.en Sat Apr  8 23:00:09 2017
@@ -0,0 +1,340 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+  <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+  <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+  <title>Project File sharing</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+  <div class="docs" id="ddissuesentermodify">
+   <h2>Entering and modifying issues</h2>
+
+   <div id="toc">
+    <ul>
+     <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+    </ul>
+
+    <ul>
+     <li>
+      <a href="/nonav/docs/ProjectIssues.html">Project issue tracking</a> 
+
+      <ul>
+       <li>
+        Entering and modifying issues 
+
+        <ul>
+         <li><a href="#enterissue">Entering a new issue</a></li>
+
+         <li><a href="#entryfields">Issue entry field descriptions</a></li>
+
+         <li><a href="#editissue">Viewing and modifying issues</a></li>
+         <li><a href="#xml">Generating issues as XML</a></li>
+	 <li><a href="#export">Exporting issues to another project</a></li> 
+
+        </ul>
+       </li>
+
+       <li><a href="/nonav/docs/ddIssues_Query.html">Querying and tracking issues</a></li>
+
+       <li><a href="/nonav/docs/ddIssues_Reports.html">Generating status reports about project issues</a></li>
+      </ul>
+     </li>
+    </ul>
+
+    <ul>
+     <li><a href="/nonav/docs/issuewritinghelp.html">Issue writing guidelines</a></li>
+
+     <li><a href="/nonav/docs/contributing_patches.html">Contributing patches</a></li>
+
+     <li><a href="/nonav/docs/issue_lifecycle.html">The lifecycle of an issue</a></li>
+
+     <li><a href="/nonav/docs/issues_unconfirmedhelp.html">Understanding the UNCONFIRMED issue state</a></li>
+    </ul>
+   </div>
+
+   <h3><a id="enterissue" name="enterissue">Entering a new issue</a></h3>
+
+   <ul>
+    <li>Choose the appropriate link in the "Enter An Issue" section of the Project Issues page.</li>
+
+    <li>Choose the appropriate project component.</li>
+
+    <li>Selected the appropriate options or input information for each field before using the <i>Commit</i> button to enter your issue.</li>
+   </ul>
+
+   <p>The information you provide here significantly determines the effectiveness of your issue reports and the response to them. Descriptions for each of these fields follow to help you optimize your issue reports.</p>
+
+   <p><b>Important note</b>: When you first enter a new issue, you cannot set a target milestone date, nor can you assign dependencies (flag other issues that depend on this new issue or those that it depends upon). To designate a target milestone or dependencies, you must first submit the new issue successfully, then retrieve it to access fields for setting a target milestone and creating dependencies.</p>
+
+   <h3><a id="entryfields" name="entryfields">Issue entry field descriptions</a></h3>
+
+   <dl>
+    <dt><a id="version" name="version"></a>Version</dt>
+
+    <dd>The release in which you identified this issue or found the defect.</dd>
+
+    <dt><a id="sub" name="sub"></a>Component/Sub Component</dt>
+
+    <dd>Identify area within the project that this issue is associated with. Only one selection is permitted.</dd>
+
+    <dt><a id="platform" name="platform">Platform</a></dt>
+
+    <dd>
+     This corresponds to <i>your</i> hardware platform when you are reporting a defect. Options include: 
+
+     <ul>
+      <li>All (happens on all platform; cross-platform issue)</li>
+
+      <li>Macintosh</li>
+
+      <li>PC</li>
+
+      <li>Sun</li>
+
+      <li>HP</li>
+     </ul>
+     <b>Note:</b> Selecting the option "All" does not select issues assigned against all platforms. It merely selects issues that <i>occur</i> on all platforms.
+    </dd>
+
+    <dt><a id="operatingsystem" name="operatingsystem">Operating System</a></dt>
+
+    <dd>
+     This is the operating system against which the issue is being reported. Legal operating systems include: 
+
+     <ul>
+      <li>All (happens on all operating systems, making this a cross-platform issue)</li>
+
+      <li>Windows 95</li>
+
+      <li>Mac System 8.0</li>
+
+      <li>Linux</li>
+     </ul>
+     Note that the operating system implies the platform, but not always. For example, Linux can run on PC, Macintosh, and others.
+    </dd>
+
+    <dt><a id="priority" name="priority"></a>Priority</dt>
+
+    <dd>
+     This field let you assign a level of importance to help determine when this issue should be addressed relative to other issues. This field is utilized by the programmers/engineers to prioritize their work. 
+
+     <ul>
+      <li>P1 - Most important</li>
+
+      <li>P2</li>
+
+      <li>P3</li>
+
+      <li>P4</li>
+
+      <li>P5 - Least important</li>
+     </ul>
+    </dd>
+
+    <dt><a id="issuetype" name="issuetype"></a>Issue Type</dt>
+
+    <dd>
+     <p><em>Defect</em> is a problem with an existing feature that is either not developed to spec or does not work as designed. These are often referred to as "bugs."</p>
+
+     <p><em>Enhancement</em> is an improvement to an existing feature.</p>
+
+     <p><em>Feature</em> is an addition to the software to add a piece of functionality that does not yet exist.</p>
+
+     <p><em>Task</em> is an activity to be done on behalf or in support of a feature or enhancement. Tasks do not typically require direct changes to the code base.</p>
+
+     <p><em>Patch</em> is a special kind of issue, a section of code to be applied or attached to existing software, often to fix a defect.</p>
+    </dd>
+
+    <dt>Initial state</dt>
+
+    <dd>Newly entered issues are either "new" or "unconfirmed." Marking an issue <a href="/nonav/docs/issues_unconfirmedhelp.html">unconfirmed</a> means you have not yet determined whether it is true or valid. Read more about "state" in the <a href="/nonav/docs/issue_lifecycle.html">lifecycle of an issue</a>.</dd>
+
+    <dt><a id="assignedto" name="assignedto">Assigned To</a></dt>
+
+    <dd>Enter the userid of the one individual who is in charge of resolving the issue. If this field is left blank, the issue by default is assigned to the component/sub component owner. Every time this field changes, the status changes to <b>NEW</b> to make it visible in the assignee's list of issues.</dd>
+
+    <dt>Cc:</dt>
+
+    <dd>
+     Add userids of other individuals who need notification when this issue changes status or when there is other activity on this issue. Delimit multiple userids by single spaces only -- no commas or semi-colons are necessary. 
+
+     <p>Note: Assign cc addresses sparingly. Project participants whose interest or involvement in this issue is peripheral should be encouraged to use IssueZilla to check and track issues rather than to rely on automatic email notification.</p>
+    </dd>
+
+    <dt>URL</dt>
+
+    <dd>
+     How to use this field depends on the issue type: 
+
+     <ul>
+      <li>For defects, URL should lead to a fairly stable system where the the problem is obvious or can be easily reproduced.</li>
+
+      <li>For enhancements, URL should provide details pertaining to the improvement, such as mockups.</li>
+
+      <li>For features, URL should link to any web-based form of material explaining the improvement such as mockups or design specs.</li>
+
+      <li>For tasks, URL is optional and may include linking to the associated feature or enhancement.</li>
+     </ul>
+    </dd>
+
+    <dt>Summary</dt>
+
+    <dd>A terse, specific statement to describe this issue. This should a few unique, self-explanatory words to identify this issue easily in reports and short lists. Limiting your entry to the width of the field is best for the columnar display of query results.</dd>
+
+    <dt>Description</dt>
+
+    <dd>Provide a full description of the issue including any pertinent history or activity around this issue. Because this field is additive, it serves as the knowledge base and means of communicating through this issue's life cycle. Other project participants view and add comments or information using this field.</dd>
+   </dl>
+
+   <h3>After completing all necessary fields:</h3>
+
+   <p><em>Commit</em> enters this issue into the project's issue database.</p>
+
+   <p><em>Reset</em> returns all field values to their default or blank settings.</p>
+
+   <p><em>Remember values as bookmark template</em> lets you save your input settings to save keystrokes when entering multiple issues for the same project component.</p>
+
+   <p>For more information about entering issues into Issuezilla, see also <a href="/nonav/docs/issuewritinghelp.html">Issue Writing Guidelines</a>.</p>
+
+   <h3><a id="editissue" name="editissue">Viewing and modifying issues</a></h3>
+
+   <p>Existing issues may be accessed in two different ways:</p>
+
+   <ul>
+    <li>Entering a specific issue number in the "Find" field located on the <strong>Issues</strong> page displays the "Issue View" page.</li>
+
+    <li>Querying for issues either by clicking the "Query database" button in the Project Issues page displays an "Issue List" page of your results. (See <a href="/nonav/docs/ddIssues_Query.html">Querying and tracking issues</a>.)</li>
+   </ul>
+
+   <p>The Issue View page is similar to the Issue Entry page and contains many of the same fields, but there are several important additions:</p>
+
+   <dl>
+    <dt>Target Milestone</dt>
+
+    <dd>If your project has designated milestones, this field can be used to associated issues with those milestones, such as version releases. A milestone plan enumerates when different features are expected to be completed. If an issue has a target date or version release, this means the work on this issue must be completed by that date. This field should only be set or changed by the person responsible for the issue.</dd>
+
+    <dt>Add/Remove CC:</dt>
+
+    <dd>You can add additional email addresses to this issue to alert other project members when activity occurs on this issue. If you are adding multiple addresses, delimit these with single spaces; do not use commas or semi-colons. You can also <i>remove</i> one or more email address listed by selecting it and checking the "Remove selected Cc's" box below.</dd>
+
+    <dt>QA Contact</dt>
+
+    <dd>This field should contain an email address or alias for the person(s) responsible for quality control of this issue.</dd>
+
+    <dt>URL</dt>
+
+    <dd>If this field is populated, clicking the field label links directly to the designated URL.</dd>
+
+    <dt>Status Whiteboard</dt>
+
+    <dd>The purpose of this generic field can be user-defined and project-specific. (In BugZilla, this field is used for writing short, one-line notes about the bug.)</dd>
+
+    <dt>Attachments</dt>
+
+    <dd>
+     Adding attachment to an issue can be very useful. For defects, appending test cases, screen shots and/or editor logs to the issue can help pinpoint the problem to help the developer reproduce it. 
+
+     <p>For features, enhancements, and tasks, you can attach screen shots, mockups, and other files to provide supplemental information to illustrate the issue.</p>
+
+     <p>You can also used this field to attach a patch related to the issue when appropriate. Read more about <a href="/nonav/docs/contributing_patches.html">contributing patches</a>.</p>
+    </dd>
+
+    <dt>Dependencies</dt>
+
+    <dd>When an issue can't be addressed until one or more other issues are resolved, these are dependencies. Each issue can have other issues it depends upon , as well as issues that depend upon it, that is, other issues that this issue "blocks" while being unresolved. The links next to these fields display a tree and graph illustrating the dependencies associated with the issue currently being viewed.</dd>
+
+    <dt>Vote for this issue</dt>
+
+    <dd>
+     <!-- (adapted from bugzilla.mozilla.org's "Bugzilla Voting" page) -->
+     Issuezilla's "voting" feature allows project members to have a certain number of votes in their project to use toward issues. Project owners set the number of votes allowed per issue, as well as the number of votes allowed per member. Some projects/components may not allow any, which means you can't vote on those issues at all. Your vote indicates which issues you believe are the most important to be addressed. 
+
+     <p>You may vote for the same bug more than once, however, you have a limited number of total votes allocated to you. You can either vote once for many issues, or use multiple votes for a fewer issues that you think are particularly critical.</p>
+
+     <p>If an issue has received votes, the total number appears next to "Votes for this issue", or "0" if no votes have been logged. Clicking on this number displays the Show Votes page. If there are votes, names and their associated number of votes are listed.</p>
+
+     <p>To view a list of issues that have received votes, use the IssueZilla Query page, and enter the numeral "1" in the "At least ___ votes" field. This returns issues in your query results with at least one vote.</p>
+
+     <p>To vote for an issue:</p>
+
+     <ul>
+      <li>Open the issue (by clicking the issue from a list or report).</li>
+
+      <li>Click on the "Vote for this issue" link just above the "Additional Comments" field. (If no such link appears, then voting may not be allowed for this issue's project/component.)</li>
+
+      <li>Indicate the number of votes you want to log for this issue. This page also displays how many votes you've given to other bugs, allowing you may reallocate your votes as necessary.</li>
+
+      <li>You receive automatic email notification anytime changes occur on issues you have voted for.</li>
+
+      <li>You may review your votes at any time by clicking the "Change your password or preferences" on the <strong>Issues</strong> page or at the bottom of the query page.</li>
+     </ul>
+
+     <p>What's the purpose of this voting feature? Read about the important role of <a href="http://www.tigris.org/editorial/safetynet.html">consensus voting in open source projects</a>.</p>
+    </dd>
+
+    <dt>Groups</dt>
+
+    <dd>If one or more drop boxes appear identifying project-defined groups to be included in or excluded from viewing an issue, this indicates that the project/component owner has created groups within the project. You should contact this person to determine how to use these fields.</dd>
+
+    <dt>Leave as NEW</dt>
+
+    <dd>If you are viewing an issue with the status NEW but it is not assigned to you, leave this default as checked. When the issue <i>is</i> assigned to you, you should accept it by changing its status to "Started."</dd>
+
+    <dt>Resolve issue</dt>
+
+    <dd>Once an issue is resolved, this is where to designate the type of resolution. Changing an issue to "Resolved" means that as far as the assignee is concerned, this issue is completed. <a href="/nonav/docs/issue_lifecycle.html#resolvedissues">Read more</a> about the multiple options in this field's pull-down menu. <b>Note: Changing an issue's status to FIXED signals all other project members that any source file changes associated with this issue have been checked into the CVS repository.</b></dd>
+
+    <dt>Reassign</dt>
+
+    <dd>The person responsible for the issue can be changed here by entering a new email address, or reassigned to the component/sub component owner.</dd>
+
+    <dt>View Issue Activity</dt>
+
+    <dd>This link displays a snapshot page of changes made to an issue.</dd>
+
+    <dt>Format For Printing</dt>
+
+    <dd>This links redisplays the Issue View in a format for printing out.</dd>
+
+    <dt>Commit</dt>
+
+    <dd>
+     This button saves any modifications made to this issue. <b>Caution! When viewing an issue, the "Enter" key works like the <i>Commit</i> button. Any modifications you may have made (accidentally or otherwise) are saved and the issue's assignee and cc list receive email notification of activity on this issue.</b> 
+
+     <p><em>To exit out of viewing this issue without making any changes</em>, use the links at the top of this page to view other issues, or the <i>Back</i> button in your browser. Even when you have changed fields, as long as you do not use the <i>Commit</i> button or the "Enter" key, the issue remains unchanged in the database.</p>
+    </dd>
+
+    <dt>Reset</dt>
+
+    <dd>Returns all fields to their <i>previously committed</i> values.</dd>
+   </dl>
+   
+   <h3><a id="xml" name="xml">Generating issues as XML</a></h3>
+   <p>When viewing an issue, you can generate an XML representation of the issue by clicking the <b>Format as XML</b> link. This option is also available by clicking the <b>Format as XML</b> button when viewing query results.</p>
+  
+   <h3><a id="export" name="export">Exporting issues</h4>
+
+   <p>To export an issue, you must have permissions that allow you to submit issues in the project to which you want to export. You can perform the export function following these steps:</p>
+
+   <ol>
+    <li>While viewing the issue you wish to export, click the <b>Export this issue ...</b> button.</li>
+    <li>Enter the username and password for the importing user and select any data fields for suppression.</li>
+    <li>Click the <b>Export Issue</b> button.</li>
+   </ol>
+   <p>If the export was successful, after a moment the issue will be updated with a link to the issue at its imported location.</p>   
+ 
+   <div class="courtesylinks">
+    <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+   </div>
+  </div>
+ </body>
+</html>
+
+

Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_Query.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_Query.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddIssues_Query.html Sat Apr  8 23:00:09 2017
@@ -0,0 +1,201 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>IssueZilla Queries and Tracking</title>
+
+
+<!--#include virtual="/google-analytics.js" --> 
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+  <div id="topbara">
+    <!--#include virtual="/pl/topnav.html" -->
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo;&nbsp;<a href="/pl/">pl</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/">Archive</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/">trans</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/">docs</a>&nbsp;&raquo;&nbsp;<a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+  </div>
+  <div id="clear"></div>
+  
+  
+  <div id="content">
+    
+    
+    
+
+<!--
+     The contents of this file are subject to the Mozilla Public
+     License Version 1.1 (the "License"); you may not use this file
+     except in compliance with the License. You may obtain a copy of
+     the License at http://www.mozilla.org/MPL/
+    
+     Software distributed under the License is distributed on an "AS
+     IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+     implied. See the License for the specific language governing
+     rights and limitations under the License.
+    
+     The Original Code is the Issuezilla Issue Tracking System.
+    
+     The Initial Developer of the Original Code is Netscape Communications
+     Corporation. Portions created by Netscape are
+     Copyright (C) 1998 Netscape Communications Corporation. All
+     Rights Reserved.
+    
+     Contributor(s): 
+
+     Contributor(s): Terry Weissman <terry@mozilla.org>
+-->
+    <span class="Header" nowrap>Querying and tracking issues</span>
+<p>
+
+<span class="PlainText"><strong>More help on IssueZilla: Index</strong>
+<ul>
+<dl>
+<dt><a href="ProjectIssues.html">Project issue tracking</a>
+  <dd><a href="ddIssues_EnterModify.html">Entering and modifying issues</a>
+  <dd><strong>You are here: Querying and tracking issues</a>
+  <ul>
+       <li><a href="#queryfields">Issue query selection fields</a><br>
+       <li><a href="#queryresults">Sorting/customizing query results</a><br>
+       <li><a href="#customqueries">Customizing/remembering queries</a><br>
+       <li><a href="#trackissue">Tracking your own issues (or by assignee)</a><br>
+       <li><a href="#otherqueries">Running other queries</a><br>
+       <li><a href="#browserinfo">Browser information</a>
+  </ul></strong>
+  <dd><a href="ddIssues_Reports.html">Generating status reports about project issues</a>
+<dt><a href="/servlets/HelpTOC">Back to main Help index</A>
+</dl>
+</ul>
+
+<p>
+<hr noshade size=1>
+    <span class="InputHeader">First, a clue about querying ...</span>
+<span class="PlainText">
+
+     <p>The IssueZilla query form allows you to call up a subset of issues from a project's issue database. If you do not select an option, then either all values for those fields or the designated default values are included in the query. Submitting a query without setting any options at all, for example, returns <i>all</i> project issues with a status of NEW, STARTED, or REOPENED. Thus, you can narrow query results by adding more conditions, that is, by selecting options and/or entering information in the query form fields. You can save your results list in your bookmark file. You can also save your query configuration to reuse later.
+  <p>Field descriptions are provided here to help you fine tune your querying as necessary.
+<p>
+
+<hr noshade size=1>
+     <a name="queryfields"><span class="InputHeader">Issue query selection fields</span></a>
+     <p>
+     <ul>
+      <li><span class="InputHeader">Type</span> refers to the classification of issues as either <a href="/docs/DomainDocsIssues_EnterModify.html#issue_type">tasks, defects, features, or enhancements</a>. 
+      <p>
+      <li><span class="InputHeader">Component</span> is the the part of the software in development associated with the issue if you are querying to find. If you don't choose a component or subcomponent, the query addresses all issues for the <i>project</i>.
+      <p>
+      <li><span class="InputHeader">Sub Component</span> is a subset of the component you selected in the previous field. If you don't choose a sub component, the query addresses all issues for the <i>component</i>.
+      <p>
+      <li><span class="InputHeader">Status</span> is set with <a href="/docs/issue_lifecycle.html">NEW, STARTED and REOPENED</a> selected as the default. When searching for issues that are UNCONFIRMED, RESOLVED, VERIFIED, or CLOSED, remember to change this status field appropriately.
+      <p>
+      <li><span class="InputHeader">Resolution</span> is the qualification of issues with a status of <a href="/docs/issue_lifecycle.html#resolvedissues">RESOLVED, VERIFIED, OR CLOSED</a>. All resolved issues must be assigned one of these <a href="/docs/issue_lifecycle.html#resolvedissues">values</a>.
+      <p>
+      <li><span class="InputHeader">Priority</span> queries for issues by their rank of importance using the following scale: P1 is highest priority, given to issues that should be addressed as soon as possible; P5 is the lowest priority.
+      <p>
+      <li><span class="InputHeader">Platform</span> is the type of computer the issues is associated with. This field is most critical when searching for defects. When querying for other types of issues, it may not be necessary to make a selection in this field.
+      <p>
+      <li><span class="InputHeader">OS</span> is the type of operating system the issue is associated with. Again, when querying for other types of issues, it may not be necessary to make a selection in this field.
+      <p>
+      <li><span class="InputHeader">Version</span> The release of the software associated with this issue. Leaving this field unselected queries all versions of the selected project or component. 
+      <p>
+      <li><span class="InputHeader">Target Milestone</span> queries for issues associated with different project milestones, if your project has these. Milestones typically are dates when certain features or overall versions are expected to be completed.
+      <p>
+      <li><span class="InputHeader">Email</span> lets you query for issues by the email address of assignee, reporter, QA contact, cc list, or added comments. A duplicate field lets you further refine queries based on this criteria. To search for issues associated with an email address: 
+     <ul>
+       <li>Type a portion of an email address into the text field. 
+       <li>Select fields to query for association with that email address. 
+     </ul>
+     <p>The second field enables you to look for two different email addresses. If you specify both, then only issues matching both are returned in your query results. For example, this is useful to find issues "created by Ralph" and "assigned to Fred." 
+     <p>You can also use the drop down menus to specify whether you want to match addresses by doing a substring match, regular expressions, or exact match of a fully specified email address. 
+     <p>
+     <ul>
+      <li>Additional input fields let you further qualify queries by issue number(s), date changes, number of votes, and changes in field values.
+      <p>
+      <li>Summary is the one-line abbreviated description of the issue used by default in reports and query results. 
+      <p>
+      <li>A description entry enables querying by text string from the longer, detailed issue description.
+      <p>
+      <li>URL lets you query by the web page location associated with issues, when applicable.
+      <p>
+      <li>Status Whiteboard is a field defined by the project owner (or users with administrative permissions in IssueZilla).  Input values to query by this field thus depend upon how it is being used in a particular project.
+      <p>Those who prefer to devise their own query schemes beyond options provided in these from fields provided can <a href="booleanchart.html">set up Boolean chart queries</a>.
+     </ul>
+     </ul>
+    <p>
+
+<hr noshade size=1>
+     <a name="queryresults"><span class="InputHeader">Sorting and customizing query results</span></a>
+     <p>Before submitting a query, you can select to sort by issue number, importance, or assignee. After you submitted a query during a IssueZilla login session, you have the option to "Reuse the same sort as last time."
+     <p>Once you view the query results, clicking on any of the column headings will sort the displayed results within that column.<p>
+     <p>Using the links at the bottom of the query results page, you can also:
+     <p>
+     <ul>
+      <li>Switch to "long format" view of results to display complete contents of issues.
+      <li>Load a new query form.
+      <li>Enter a new issue.
+      <li>Change which columns appear in query results.
+      <li>Change several issues at once. (This option displays a page that lets you select issues from your query results list and modify specific fields in all of these simultaneously.)
+      <li>Send email to owners of issues listed.
+      <li>Edit the configuration of the last query.
+     </ul>
+     <p>
+To add the target milestone for each issue to your query results -- and you should do so when a particular issue is slated for release --
+     <p>
+      <ol>
+       <li>Do a query (or click "view assigned issues").
+       <li>Click the "change columns" link at the bottom. 
+       <li>Click the "target milestone" check box.
+       <li>Submit.  
+      </ol>
+     <p>The target milestone column will now included for all your subsequent queries because login sessions are cookie-based. You can unmark this checkbox or mark others at any time to change your customized query results.
+     <p>
+
+<hr noshade size=1>
+     <a name="customqueries"><span class="InputHeader">Remembered queries</span></a>
+     <p>Once you've set up a fairly complex query to ferret out certain issues, you can tell IssueZilla to "remember" your custom queries as a time saver. Using the options just above the <i>Submit query</i> button, you can save your most recent query under a unique name and reuse it anytime you are logged in to IssueZilla. You can also change and reset the default query that the query page loads during your login sessions.
+     <p>To include your custom, named queries in the footer of the query page, use the "Edit prefs" link in the IssueZilla tool bar, and select the "Page Footer" option.  All of your named queries have the option to be included in the IssueZilla tool bar on every page or only on the query page. 
+
+<hr noshade size=1>
+     <a name="trackissue"><span class="InputHeader">Tracking issues by assignee</span></a>
+     <p><b>To view a list of project issues assigned to you</b>, click the <i>My Issues</i> link in the Project Issues page.
+<p>One you have invoked IssueZilla, you can also click the <i>My issues</i> link in the secondary Issue Tracking tool bar.
+
+     <p><b>To view other project members' assigned issues</b>, create a query using the "search the issue database" link and search by the "assigned to" field with the person's name entered. (The default setting for the "status" in the query screen includes NEW, STARTED, and REOPENED.)
+
+     <p>You can also generate reports by user and create a page of project members listed by name, each with a link to their specific list of issues.
+     <p>
+     <p>
+
+<hr noshade size=1>
+     <a name="otherqueries"><span class="InputHeader">Running queries not supported by the pretty boxes</span></a>
+      <p>There is a hacky way to do some searches that aren't supported by the query form.  The issue list script will build queries based on the URL, so you can add other criteria.
+     <p>
+For example, if you wanted to see all issues reported against the X platform and assigned to user "jwz," you could ask for all issues assign to jwz, then edit the URL in the "Location" box, adding the clause "&rep_platform=X-Windows" to the URL.
+     <p>
+Here is a list of some of the field names you could use for additional unsupported searches ...
+     <p>
+     version<br>
+     rep_platform<br>
+     op_sys<br>
+     reporter area<br>
+     issue_file_loc<br>
+     short_desc<br>
+     <p>
+
+<hr noshade size=1>
+     <a name="browserinfo"><span class="InputHeader">Browser notes</span></a>
+     <p>IssueZilla uses several non-standard Netscape extensions, but this does not seem
+to case any problem with other browsers.  The Lynx browser does work, but Lynx seems to cache results of a .cgi.  You'll sometimes need to press CONTROL-R to reload the screen to see an update.
+<p>   
+ 
+<hr noshade size=1>
+<a href="ProjectIssues.html">Back to Project Issues help</a><br>
+<a href="/servlets/HelpTOC">Back to main Help index</a></p></span>
+</span>
+</span>
+
+  </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>



Mime
View raw message