DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Z8MJivZntKJendPxpY9pDm8usLODywBUoaTmO0ziAw14QUzRnVH+JmKt8OIp7+T6I6Pm3JSpj8c4ZldU81WSQrnSNMfBXWtl2GbEnzvFiNx++08idJ7XxiUt2A1Z+Xf3a3FFyMS5JpmwPxTFlrT3ipBi7Ds5UPE6aTLUuHOWgek=
Message-ID: <9c23279705090810123132447d@mail.gmail.com>
Date: Thu, 8 Sep 2005 14:12:01 -0300
From: Weber Ress <ress.weber@gmail.com>
Reply-To: ress.weber@gmail.com
To: linux-kernel@vger.kernel.org
Subject: How to plan a kernel update ?
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 846
Lines: 22

Hi,

I'm responsible to planning a kernel upgrade in many servers, from 2.4
version to 2.6.13 (last stable version), using Debian 3.1r0a

My team has good technical skills, but they need to be led. I would
like know, what's the best pratices and recommendations that a project
manager need think BEFORE an kernel upgrade.

A technical guy have a particular vision about this upgrade, but I
will be very been thankful if I receive from this community another
vision.. a vision centered in the project process (planning,
executing, controlling) to make this activity successfully.

Thank's !

Weber Ress
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/