Gentoo Archives: gentoo-commits

From: "Davide Cendron (scen)" <scen@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/security/it: vulnerability-policy.xml
Date: Fri, 22 Feb 2008 21:44:35
Message-Id: E1JSfh1-0008MT-VV@stork.gentoo.org
1 scen 08/02/22 21:44:31
2
3 Modified: vulnerability-policy.xml
4 Log:
5 Ops, missing translation updated properly
6
7 Revision Changes Path
8 1.5 xml/htdocs/security/it/vulnerability-policy.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/it/vulnerability-policy.xml?rev=1.5&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/it/vulnerability-policy.xml?rev=1.5&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/it/vulnerability-policy.xml?r1=1.4&r2=1.5
13
14 Index: vulnerability-policy.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/security/it/vulnerability-policy.xml,v
17 retrieving revision 1.4
18 retrieving revision 1.5
19 diff -u -r1.4 -r1.5
20 --- vulnerability-policy.xml 22 Feb 2008 21:41:46 -0000 1.4
21 +++ vulnerability-policy.xml 22 Feb 2008 21:44:31 -0000 1.5
22 @@ -1,6 +1,6 @@
23 <?xml version='1.0' encoding="UTF-8"?>
24 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
25 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/security/it/vulnerability-policy.xml,v 1.4 2008/02/22 21:41:46 scen Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/security/it/vulnerability-policy.xml,v 1.5 2008/02/22 21:44:31 scen Exp $ -->
27
28 <guide link="/security/it/vulnerability-policy.xml" lang="it">
29 <title>Politiche di gestione delle vulnerabilità in Gentoo Linux</title>
30 @@ -509,8 +509,9 @@
31 una volta effettuato il commit dell'ebuild, valutare le keyword necessarie
32 per l'ebuild corretto e far testare (e far contrassegnare come stabile)
33 l'ebuild contenente la correzione ai relativi team delle specifiche
34 - architetture coinvolte (i team delle architetture devono essere in cc sul
35 - bug) e impostare il campo "Status Whiteboard" a <c>stable</c>
36 + architetture coinvolte (i team delle architetture, nonchè releng durante la
37 + preparazione al rilascio, devono essere in cc sul bug) e impostare il campo
38 + "Status Whiteboard" a <c>stable</c>
39 </li>
40 <li>
41 I mantenitori delle architetture dovrebbero contrassegnare l'ebuild stabile
42
43
44
45 --
46 gentoo-commits@l.g.o mailing list