Gentoo Archives: gentoo-dev

From: Christian Faulhammer <opfer@g.o>
To: "gentoo-dev@l.g.o" <gentoo-dev@l.g.o>
Cc: x86@g.o, hppa@g.o, alpha@g.o, amd64@g.o, sparc@g.o, ppc@g.o, ppc64@g.o, ia64@g.o, bsd@g.o, mips@g.o
Subject: [gentoo-dev] Help for arch teams
Date: Fri, 07 Dec 2007 00:04:44
Message-Id: 20071207010241.01aa1868@gentoo.org
1 Hi,
2
3 [CC some arch teams, too, as not all devs read -dev]
4
5 As promised [1] about two months ago, the template for Gatt, that
6 handles all the commit stuff for architecture developers, is now ready
7 to be used by the public. Some bugs in Gatt needed to be resolved and
8 heavy testing has been done.
9
10 1. Emerge the package with Gatt
11 2. Test the software
12 3. Use the template named "keywords" shipped with Gatt to create a
13 script for stabilisation Execute it on the system you have commit
14 access from
15
16 All needed commands are given in the TUTORIAL file, so I concentrate on
17 what the script can do for you:
18
19 * determine if it is a keywording or stabilisation request
20 * determine if it is a security stabilisation and set ChangeLog/commit
21 message plus Bugzilla handling correctly
22 * update of cvs tree before doing any work
23 * setting needed keyword
24 * setting ChangeLog scan for QA errors (repoman)
25 * commit it to the repository
26 * uncc arch from bug including message "arch stable"
27 * and close bug if needed (not when security related) always
28 with confirmation
29
30 Test it and report back. Thanks.
31
32 V-Li
33
34 [1]
35 <URL:http://www.faulhammer.org/index.php?option=com_content&task=view&id=198>
36
37 --
38 Christian Faulhammer, Gentoo Lisp project
39 <URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
40
41 <URL:http://www.faulhammer.org/>

Attachments

File name MIME type
signature.asc application/pgp-signature