Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Thu, 16 Feb 2006 18:12:51 +0100
From: "Bernt M. Johnsen" <Bernt.Johnsen@Sun.COM>
Subject: Re: Jira attachments - please don't delete
In-reply-to: <43F4B021.9020606@apache.org>
To: derby-dev@db.apache.org
Message-id: <20060216171251.GA8487@localhost.localdomain>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB"
Content-disposition: inline
User-Agent: Mutt/1.5.9i
References: <43F4B021.9020606@apache.org>


--tThc/1wpZn/ma/RB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

>>>>>>>>>>>> Daniel John Debrunner wrote (2006-02-16 09:02:25):
>=20
> I notice that some folks are deleting jira attachements when they attach
> a new version of a patch or functional/design spec. I personally think
> this should not be encouraged, it's sometimes helpful to have the
> history of the patch and especially helpful to have the history of a spec.
>=20
> Does anyone think it's a good idea to delete old attachements?

That depends. If old attchments are kept, it is verfy important with
names that clearly states wether
1) it is a new version of a patch (use e.g. v1 v2 etc in the
   name. Especially remember to use v1 in the *first* one.)
2) it is an addition to another patch or
3) it is one of several sub-patches.

Today, very often, you have to browse through the comments to figure
this out.

Also: in the comments, we should be catious to name the patch instead
of writing "this", "new" or "latest", which after som new patches and
comments are of very little value.

--=20
Bernt Marius Johnsen, Database Technology Group,=20
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway

--tThc/1wpZn/ma/RB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD9LKTlFBD9TXBAPARAjfFAJ0bKRzOihYJAUIaWVm35781rpzMFQCgrAq+
hjw3MIdpbwrDTaEvFMOpQvM=
=FNIB
-----END PGP SIGNATURE-----

--tThc/1wpZn/ma/RB--