Return-Path: 
 <felix-dev-return-2499-apmail-incubator-felix-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-felix-dev-archive@www.apache.org
Received: (qmail 52520 invoked from network); 25 Jul 2006 11:16:23 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 25 Jul 2006 11:16:23 -0000
Received: (qmail 28184 invoked by uid 500); 25 Jul 2006 11:16:22 -0000
Delivered-To: apmail-incubator-felix-dev-archive@incubator.apache.org
Received: (qmail 28146 invoked by uid 500); 25 Jul 2006 11:16:22 -0000
Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:felix-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:felix-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:felix-dev@incubator.apache.org>
List-Id: <felix-dev.incubator.apache.org>
Reply-To: felix-dev@incubator.apache.org
Delivered-To: mailing list felix-dev@incubator.apache.org
Received: (qmail 28129 invoked by uid 99); 25 Jul 2006 11:16:22 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 04:16:22 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [66.111.4.29] (HELO out5.smtp.messagingengine.com)
 (66.111.4.29)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 04:16:21 -0700
Received: from frontend3.internal (frontend3.internal [10.202.2.152])
	by frontend1.messagingengine.com (Postfix) with ESMTP id 3BDF7D919BE
	for <felix-dev@incubator.apache.org>; Tue, 25 Jul 2006 07:16:00 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
  by frontend3.internal (MEProxy); Tue, 25 Jul 2006 07:16:03 -0400
X-Sasl-enc: 7qx4hNYpsDd4hXh13O+fr4+zRlJ0kxPffAHGjL8MvPhp 1153826160
Received: from [10.0.0.3] (host-87-74-127-123.bulldogdsl.com [87.74.127.123])
	by www.fastmail.fm (Postfix) with ESMTP id E312092B8
	for <felix-dev@incubator.apache.org>; Tue, 25 Jul 2006 07:15:59 -0400 (EDT)
Message-ID: <44C5FD6B.5080904@odoko.co.uk>
Date: Tue, 25 Jul 2006 12:15:55 +0100
From: Upayavira <uv@odoko.co.uk>
Organization: Odoko Ltd
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: felix-dev@incubator.apache.org
Subject: Re: Tagging Felix Bundles
References: <44C5FC3A.4070304@isti.cnr.it>
In-Reply-To: <44C5FC3A.4070304@isti.cnr.it>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Francesco Furfari wrote:
> Hi all,
> I'm going to commit a new version of the UPnP base driver that requires
> a new patched version of  the CyberLink library.
> The library is embedded in the the bundle and I should delete the old
> version from the resources of the project.
> Is this the case in which I should create a Tag for the current bundle
> before to proceed with the update?
> 
> In your opinion which is the best structure for the tags?
> trunk
> <bundle project (i)>
> tags
>    <bundle project (i)>
>          <bundle project(i)>-<version>

Why do you want the tag? Are you ever going to want to get back to the
old version?

Also, remember, you can always get to it via revision ID if you don't
create a tag.

So unless you've got a compelling reason for creating a tag, I'd just
get on and delete it. It'll still be there :-)

Regards, Upayavira