Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates
 209.85.198.246 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=uhJfqR5r4flbMenO0DaVkgo/f0GDdEE5S+RSCpvmqjOLLcs1rqq6gUuz2B96HPO3Up
         z7E0ZwLXfuumiUATJuy8Ln+0RukevVwJTnnHBfWv5mato2NvwJGErOtyHZoJ/mZQ5Kgp
         0D/3ApxuEttV7DX2jkEorlUQpyT69R4F0SwT0=
Message-ID: <31cc37360811070728lecd2120ib2aac9e482db07c@mail.gmail.com>
Date: Fri, 7 Nov 2008 09:28:03 -0600
From: "Henri Yandell" <flamefew@gmail.com>
To: "Commons Developers List" <dev@commons.apache.org>
Subject: [all] Marking components as inactive
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

(From the Jelly thread)

With Jelly as an first use case I'd like to propose a process for
marking a component as inactive. Said process being:

1) Vote on commons-dev. 7 days minimum (though there's no real rush).

2) Make inactive:
  a) remove from trunks-proper
  b) Update the homepage to say "Not Actively Maintained"
  c) Update the Commons homepage to put this into a release
subcategory of "Not Actively Maintained"
  d) Put said N.A.M. note on the JIRA page.

This is very close to the process Taglibs have used (with a much
looser step #1 as we know there are only 4 people there :) ), though
there they are deprecated rather than not actively maintained.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org