-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Mise à jour de la traduction du site web de Slony.
- Loading branch information
Showing
10 changed files
with
492 additions
and
53 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,207 @@ | ||
| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> | ||
| <html> | ||
| <head> | ||
| <title>Slony-I Bug Processing Policy</title> | ||
| <style type="text/css"> | ||
| a:link{ | ||
| font-family:lucida,arial,helvetica; font-size: 11px; font-style:normal; font-weight:bold; color:#003399; text-decoration:none; | ||
| } | ||
| a:visited{ | ||
| font-family:lucida,arial,helvetica; font-size: 11px; font-style:normal; font-weight:bold; color:#003399; text-decoration:none; | ||
| } | ||
| a:hover{ | ||
| color:"red"; text-decoration:underline; | ||
| } | ||
| .text TD { | ||
| font-family:lucida,arial,helvetica; font-size: 11px; font-style:normal; | ||
| } | ||
| .footerText TD { | ||
| font-family:lucida,arial,helvetica; font-size: 11px; font-style:normal; color:#FFFFFF; | ||
| } | ||
| </style> | ||
| </head> | ||
|
|
||
| <body> | ||
| <table border="0" cellpadding="2" cellspacing="0" width="100%"> | ||
| <tbody> | ||
| <tr> | ||
| <td> | ||
| <table border="0"> | ||
| <tbody> | ||
| <tr> | ||
| <td align="left" valign="top"><img src= | ||
| "images/Slon_450x320.jpg" align="left"></td> | ||
|
|
||
| <td align="left" valign="top"></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| <table border="0" cellpadding="2" cellspacing="0" width= | ||
| "100%"> | ||
| <!-- if proj id not empty display proj nav --> | ||
|
|
||
| <tbody> | ||
| <tr bgcolor="#000000"> | ||
| <td colspan="2"><img src="images/shim.gif" height= | ||
| "1" width="1"></td> | ||
|
|
||
| <td><img src="images/shim.gif" height="1" width= | ||
| "1"></td> | ||
| </tr> | ||
|
|
||
| <tr bgcolor="#EEEEEE"> | ||
| <td nowrap="nowrap"><img src="images/shim.gif" | ||
| height="1" width="1"><b><a class="adminNav" href= | ||
| "admin.html">Project Admin Area</a></b></td> | ||
|
|
||
| <td align="right" nowrap="nowrap" width="100%"> | ||
| <b><a class="projNav" href= | ||
| "http://main.slony.info">slony1 Home</a> | | ||
| <a class="projNav" href= | ||
| "http://slony.info/">Slony-I Website</a> | | ||
| <a class="projNav" href="git.html">Git Info</a> | ||
| | <a class="projNav" href= | ||
| "http://lists.slony.info/mailman/listinfo">Mailing | ||
| Lists</a></b></td> | ||
|
|
||
| <td><img src="images/shim.gif" height="1" width= | ||
| "1"></td> | ||
| </tr> | ||
|
|
||
| <tr bgcolor="#000000"> | ||
| <td colspan="2"><img src="images/shim.gif" height= | ||
| "1" width="1"></td> | ||
|
|
||
| <td><img src="images/shim.gif" height="1" width= | ||
| "1"></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| <h1>Slony-I Bug Processing</h1> | ||
|
|
||
| <p> Slony bug tracking is being managed using <a | ||
| href="http://www.bugzilla.org/"> Bugzilla.</a></p> | ||
|
|
||
| <p> Here is the <a href="http://www.slony.info/bugzilla/"> Slony-I | ||
| Bugzilla Instance </a>. | ||
|
|
||
| <h1> Bug Management Process </h1> | ||
|
|
||
| <p> <a href= | ||
| "http://www.slony.info/bugzilla/docs/en/html/lifecycle.html"> Bug | ||
| Lifecycle Documentation </a> uses the following image <img | ||
| src="http://www.slony.info/bugzilla/docs/en/images/bzLifecycle.png"> | ||
| to characterize the flow of work on bugs, through various states, as | ||
| they (hopefully!) get fixed. | ||
|
|
||
| <p> The following interpretations are suggested. | ||
|
|
||
| <h2> NEW </h2> | ||
| <a name="NEW"> | ||
|
|
||
| <P> When a bug is created, it is created with <B>NEW</B> state, is | ||
| assigned to <tt>slony1-bugs@lists.slony.info</tt>, and an email is | ||
| sent to the bug tracking list. | ||
|
|
||
| <P> At this point, someone on the Slony development team should | ||
| examine the bug to ascertain what, if anything, should be done with | ||
| it. | ||
|
|
||
| <P> It may be appropriate to: | ||
| <ul> | ||
|
|
||
| <li> Assign it to someone that is expected to work on it, changing the | ||
| owner, and change the status to <a href="#ASSIGNED">ASSIGNED</A>. | ||
|
|
||
| <li> Perhaps the bug is trivially resolved, in which case, it is | ||
| reasonable to jump straight to marking it <a | ||
| href="#RESOLVED">RESOLVED</a>. | ||
|
|
||
| <li> Perhaps the bug is invalid. Jump straight to <a href= | ||
| "#RESOLVED">RESOLVED</a>. | ||
|
|
||
| <li> Perhaps it is unclear who should work on it. Perhaps the bug | ||
| should be left alone, or perhaps it should be <a | ||
| href="#ASSIGNED">ASSIGNED</A> to someone who might know who | ||
| <i>should</i> do the work. | ||
|
|
||
| </ul> | ||
|
|
||
| <h2> ASSIGNED </h2> | ||
| <a name="ASSIGNED"> | ||
|
|
||
| <P> This is the state of bugs that belong to <i>someone</i>. That | ||
| someone should presumably be a human, and not | ||
| <tt>slony1-bugs@lists.slony.info</tt>. | ||
|
|
||
| <h2> RESOLVED </h2> | ||
| <a name="RESOLVED"> | ||
|
|
||
| <P> This is the state of bugs that have been addressed, after some | ||
| fashion. | ||
|
|
||
| <P> There are several possible resolutions: | ||
| <ul> | ||
| <li> <B>FIXED</B> - believed to be resolved | ||
| <li> <B>DUPLICATE</B> - this apparently duplicates some previous bug | ||
| <li> <B>WONTFIX</B> - a problem that we don't plan to address | ||
| <li> <B>WORKSFORME</B> - the developer can't duplicate the issue | ||
| <li> <B>INVALID</B> - the problem is considered part of the proper behaviour of Slony | ||
| </ul> | ||
|
|
||
| <P> Note that this is <i>not the end</i> of the lifecycle! | ||
|
|
||
| <P> If a developer has a patch for a complex issue, it is appropriate to: | ||
| <ul> | ||
| <li> Attach a patch, or perhaps a reference to a Git commit for the proposed fix. | ||
| <li> Mark the bug <B>RESOLVED/FIXED</B> | ||
| <li> Reassign the bug, either to: | ||
| <ul> | ||
| <li> The person that reported the bug | ||
| <li> The <tt>slony1-bugs@lists.slony.info</tt> user | ||
| <li> A specific Slony developer that is to validate the fix as <a name="#VERIFIED"> VERIFIED</a> | ||
| </ul> | ||
|
|
||
| <h2> VERIFIED </h2> | ||
| <a name="VERIFIED"> | ||
|
|
||
| <P> A developer (or user) takes a <a href="#RESOLVED">RESOLVED</a> bug, and evaluates | ||
| whether the resolution provided is proper. | ||
|
|
||
| <P> The same resolution values apply: | ||
| <ul> | ||
| <li> <B>FIXED</B> - believed to be resolved | ||
| <li> <B>DUPLICATE</B> - this apparently duplicates some previous bug | ||
| <li> <B>WONTFIX</B> - a problem that we don't plan to address | ||
| <li> <B>WORKSFORME</B> - the developer can't duplicate the issue | ||
| <li> <B>INVALID</B> - the problem is considered part of the proper behaviour of Slony | ||
| </ul> | ||
|
|
||
| <P> At this point, for complex patches, we can consider that the patch | ||
| has been <B>verified</B> to be valid to be committed and released. | ||
|
|
||
| <P> The bug might be re-assigned back to the original developer to do | ||
| the commit. But wait, it's not <a href="#CLOSED">CLOSED</a> yet... | ||
|
|
||
| <H2> CLOSED </h2> | ||
| <a name="CLOSED"> | ||
|
|
||
| <P> The final destination for a Slony bug is for it to be closed. The | ||
| fix should have passed through phases of being <a href="#ASSIGNED"> | ||
| ASSIGNED</a> <a href="#RESOLVED"> RESOLVED</a> <a name="#VERIFIED"> | ||
| VERIFIED</a>. For particularly simple bugs, or for issues considered | ||
| to <i>not really be bugs</i>, these phases may be rather brief. | ||
|
|
||
| <P> A bug being marked <B>CLOSED</B> should indicate that we have put | ||
| it into some specific release, and placed a suitable reference into | ||
| the release notes. | ||
|
|
||
| <H2> REOPENED </h2> | ||
|
|
||
| <P> Oh, no, the <b>zombie bug!</b> | ||
|
|
||
| <P> Sometimes bugs aren't solved in the first attempt, and need to be | ||
| reopened. This is pretty much equivalent to <a href="#ASSIGNED"> | ||
| ASSIGNED</a>. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,32 +1,42 @@ | ||
| Slony-I cvs | ||
| # | ||
| <h1>Accès Anonyme au CVS</h1> | ||
| <h1>CVS EST MAINTENANT OBSOLETE</h1> | ||
|
|
||
| <p>Notez que le contenu suivant <b>est obsolète</b> car le code source de | ||
| Slony-I est géré avec <a href="http://slony.info/git.html">Git</a> depuis le | ||
| 15 juillet 2010. Merci d'utiliser le dépôt à présent. | ||
|
|
||
| <h1>Accès Anonyme au CVS</h1> | ||
|
|
||
| <p>Vous pouvez accéder au code source de Slony-I via un CVS anonyme en | ||
| utilisant les commandes suivantes :</p> | ||
|
|
||
| <p>Vous pouvez accéder au code source de Slony-I via un CVS anonyme en | ||
| utilisant les commandes suivantes :</p> | ||
| <pre> | ||
| CVSROOT=":pserver:anonymous@main.slony.info:/slony1" cvs login | ||
| </pre> | ||
| (un mot de passe est demandé : pressez simplement [entrée]) | ||
|
|
||
| <p>Un mot de passe est demandé, pressez simplement [enter].</p> | ||
|
|
||
| <pre> | ||
| CVSROOT=":pserver:anonymous@main.slony.info:/slony1" cvs co slony1-engine | ||
| </pre> | ||
|
|
||
| <h1>Accès au CVS pour les développeurs</h1> | ||
| <h1>Accès au CVS pour les développeurs</h1> | ||
|
|
||
| <p>Si vous êtes un des développeurs et que votre clef SSH a été ajoutée sur le | ||
| serveur, vous pouvez accéder en tant qu'utilisateur avec les droits de | ||
| modification :</p> | ||
|
|
||
| <p>Si vous êtes un des développeurs, et que votre clef SSH a été ajoutée | ||
| sur le serveur, vous pouvez accéder en tant qu'utilisateur avec les | ||
| droits de modification : </p> | ||
| <pre> | ||
| MYSLONYNAME=cbbrowne CVS_RSH=ssh CVSROOT=":ext:${MYSLONYNAME}@main.slony.info:/home/cvsd/slony1" cvs co slony1-engine | ||
| </pre> | ||
|
|
||
| <h1>Modules disponibles</h1> | ||
|
|
||
| <ul> | ||
| <li><a href="http://main.slony.info/viewcvs/viewvc.cgi/slony1-engine/"> slony1-engine</a> - le système de réplication</li> | ||
| <p>Néanmoins, comme le dépôt CVS <tt>slony1-engine</tt> <b>est obsolète</b>, | ||
| vous ne devez plus l'utiliser.</p> | ||
|
|
||
| <li><a href="http://main.slony.info/viewcvs/viewvc.cgi/slony1-www/">slony1-www</a> - le site web | ||
| main.slony.info</li> | ||
| <h1>Modules disponibles</h1> | ||
|
|
||
| </ul> | ||
| <ul> | ||
| <li><a href="http://main.slony.info/viewcvs/viewvc.cgi/slony1-www/">slony1-www</a> | ||
| - le site web main.slony.info</li> | ||
| </ul> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,24 +1,24 @@ | ||
| Slony-I - introduction | ||
| # | ||
| <p><b>Slony-I</b> est un système de réplication entre "un maître et plusieurs esclaves" | ||
| qui supporte les architectures en cascade ( un noeud pour être maitre d'un noeud qui est lui-même maitre d'un autre noeud ) | ||
| et les bascules sur panne ( "failover" ).</p> | ||
| <p><b>Slony-I</b> est un système de réplication entre un maître et plusieurs | ||
| esclaves qui supporte les architectures en cascade (un nœud peut être | ||
| maitre d'un noeud qui est lui-même maitre d'un autre noœud) et les | ||
| bascules sur panne (failover).</p> | ||
|
|
||
| <p>Le <i>principe de base</i> qui guide les développements de Slony-I | ||
| est de réaliser un système de réplication avec toutes les fonctionnalités | ||
| et les capacités nécessaires pour dupliquer de grandes bases de données | ||
| vers un nombre raisonablement limité de serveurs esclaves. | ||
| </p> | ||
| <p>Le <i>principe de base</i> qui guide les développements de Slony-I est de | ||
| réaliser un système de réplication avec toutes les fonctionnalités et les | ||
| capacités nécessaires pour dupliquer de grandes bases de données vers un | ||
| nombre raisonablement limité de serveurs esclaves.</p> | ||
|
|
||
| <p>Slony-I est conçu pour les centre d'hébergement ("data centers") et | ||
| les sites de sauvegarde. Son mode d'opération normal prévoit que | ||
| tous les noeuds soient disponibles.</p> | ||
| <p>Slony-I est conçu pour les centre d'hébergement (data centers) et les sites | ||
| de sauvegarde. Son mode d'opération normal prévoit que tous les nœuds | ||
| soient disponibles.</p> | ||
|
|
||
| <p>Un "guide d'administration" assez complet, basé sur le contenu de | ||
| du dépôt CVS tree, est disponible <a href= | ||
| "http://linuxdatabases.info/info/slony.html" title="guide administration de Slony">ici</a>. | ||
| Il existe également une <a href="/documentation/">copie locale</a>.</p> | ||
| <p>Un guide d'administration assez complet, basé sur le contenu du dépôt GIT, | ||
| est disponible <a href="http://linuxdatabases.info/info/slony.html" | ||
| title="guide administration de Slony">ici</a>. Il existe également une <a | ||
| href="/documentation/">copie locale</a>.</p> | ||
|
|
||
| <p>Les spécifications initiales sont disponible <a href= | ||
| "http://developer.postgresql.org/%7Ewieck/slony1/Slony-I-concept.pdf"> | ||
| ici</a> (en anglais).</p> | ||
| <p>Les spécifications initiales sont disponible <a | ||
| href="http://developer.postgresql.org/%7Ewieck/slony1/Slony-I-concept.pdf">ici</a> | ||
| (en anglais).</p> |
Oops, something went wrong.