Return-Path: 
 <users-return-16638-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org>
X-Original-To: apmail-subversion-users-archive@minotaur.apache.org
Delivered-To: apmail-subversion-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CEF55D221
	for <apmail-subversion-users-archive@minotaur.apache.org>;
 Thu,  8 Nov 2012 23:16:20 +0000 (UTC)
Received: (qmail 74588 invoked by uid 500); 8 Nov 2012 23:16:20 -0000
Delivered-To: apmail-subversion-users-archive@subversion.apache.org
Received: (qmail 74471 invoked by uid 500); 8 Nov 2012 23:16:20 -0000
Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@subversion.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@subversion.apache.org>
List-Post: <mailto:users@subversion.apache.org>
List-Id: <users.subversion.apache.org>
Delivered-To: mailing list users@subversion.apache.org
Received: (qmail 74464 invoked by uid 99); 8 Nov 2012 23:16:20 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 23:16:20 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of richardcavell@mail.com
 designates 74.208.5.67 as permitted sender)
Received: from [74.208.5.67] (HELO mailout-us.gmx.com) (74.208.5.67)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 08 Nov 2012 23:16:10 +0000
Received: (qmail 21483 invoked by uid 0); 8 Nov 2012 23:15:48 -0000
Received: from 114.77.240.9 by rms-us002 with HTTP
Content-Type: multipart/alternative;
 boundary="========GMXBoundary238981352416545728433"
Date: Thu, 08 Nov 2012 18:15:45 -0500
From: "Richard Cavell" <richardcavell@mail.com>
Message-ID: <20121108231545.238980@gmx.com>
MIME-Version: 1.0
Subject: Re: SVN Usage Questions
To: "Ahmed, Omair (GE Oil & Gas)"
 <omair.ahmed@ge.com>,users@subversion.apache.org
X-Authenticated: #79335750
X-Flags: 0001
X-Mailer: GMX.com Web Mailer
x-registered: 0
X-GMX-UID: dljucD483zOlNSfy0XAhocB+IGRvbwAp
X-Virus-Checked: Checked by ClamAV on apache.org

--========GMXBoundary238981352416545728433
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Just my two cents, but I think that "release" should only refer to builds that have been shipped to the end-user and are in usage.

 Why not have a top-level directory:

 /build

 And if it's automated to build every night, it could have:

 /build/9 November 2012/...
 /build/8 November 2012/...
 /build/7 November 2012/...

 And dump all build artifacts in there.

 Richard

----- Original Message -----
From: Ahmed, Omair (GE Oil & Gas)
Sent: 11/09/12 08:39 AM
To: users@subversion.apache.org
Subject: SVN Usage Questions

 Hi,
 I am looking for some guidance on where to store build artifacts in SVN. Our projects are organized in the typical fashion:
 /trunk/Customer1/
 ../../src
 ../../database
 /branch
 /tags
 /release
 Our official build server is a QNX system, a Unix-like OS. 
 Our proposed process calls for the build engineer to copy the code from the SVN repo to the build server. When a build has been executed, where should we copy the artifacts (the executables) back to? Is the /release directory appropriate or is the another “standard” way to store the artifacts?
 How are other people handling this?
 Secondly, if we check-in to the /release folder, what mechanism is there to readily identify the artifacts. Do we create a /release/rel_1 type structure or is there some labeling convention available in SVN? Unless I am I missing something very obvious, I don’t see a way to apply labels in SVN.
 Please advise.

--========GMXBoundary238981352416545728433
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<span style=3D'font-family:Verdana'><span style=3D'font-size:12px'>Just my =
two cents, but I think that "release" should only refer to builds that have=
 been shipped to the end-user and are in usage.<br />=20
<br />=20
Why not have a top-level directory:<br />=20
<br />=20
/build<br />=20
<br />=20
And if it's automated to build every night, it could have:<br />=20
<br />=20
/build/9 November 2012/...<br />=20
/build/8 November 2012/...<br />=20
/build/7 November 2012/...<br />=20
<br />=20
And dump all build artifacts in there.<br />=20
<br />=20
Richard<br />=20
<br />=20
<p style=3D"margin:0px; padding:0px;" >=20
	=C2=A0</p>=20
<blockquote style=3D"border-left: 1px solid #CCC; padding-left: 5px; margin=
-left: 5px; margin-bottom: 0px; margin-top: 0px; margin-right: 0px;" type=
=3D"cite">=20
	<p style=3D"margin:0px; padding:0px;" >=20
		<span style=3D"font-family:Verdana"><span style=3D"font-size:12px">----- =
Original Message -----</span></span></p>=20
	<p style=3D"margin:0px; padding:0px;" >=20
		<span style=3D"font-family:Verdana"><span style=3D"font-size:12px">From: =
Ahmed, Omair (GE Oil &amp; Gas)</span></span></p>=20
	<p style=3D"margin:0px; padding:0px;" >=20
		<span style=3D"font-family:Verdana"><span style=3D"font-size:12px">Sent: =
11/09/12 08:39 AM</span></span></p>=20
	<p style=3D"margin:0px; padding:0px;" >=20
		<span style=3D"font-family:Verdana"><span style=3D"font-size:12px">To: us=
ers@subversion.apache.org</span></span></p>=20
	<p style=3D"margin:0px; padding:0px;" >=20
		<span style=3D"font-family:Verdana"><span style=3D"font-size:12px">Subjec=
t: SVN Usage Questions</span></span></p>=20
	<br />=20
	<div link=3D"blue" vlink=3D"purple">=20
		<div class=3D"WordSection1">=20
			<p class=3D"MsoNormal">=20
				Hi,</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				I am looking for some guidance on where to store build artifacts in SVN=
. Our projects are organized in the typical fashion:</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				/trunk/Customer1/</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				../../src</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				../../database</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				/branch</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				/tags</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				/release</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				Our official build server is a QNX system, a Unix-like OS. &nbsp;</p>=
=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				Our proposed process calls for the build engineer to copy the code from=
 the SVN repo to the build server. When a build has been executed, where sh=
ould we copy the artifacts (the executables) back to? Is the /release direc=
tory appropriate or is the another =E2=80=9Cstandard=E2=80=9D way to store =
the artifacts?</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				How are other people handling this?</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				Secondly, if we check-in to the /release folder, what mechanism is ther=
e to readily identify the artifacts. Do we create a /release/rel_1 type str=
ucture or is there some labeling convention &nbsp;available in SVN? Unless =
I am I missing something very obvious, I don=E2=80=99t see a way to apply l=
abels in SVN.</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p class=3D"MsoNormal">=20
				Please advise.</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
			<p style=3D"margin:0px; padding:0px;" >=20
				=C2=A0</p>=20
		</div>=20
	</div>=20
</blockquote>=20
<p style=3D"margin:0px; padding:0px;" >=20
	=C2=A0</p>=20
</span></span>

--========GMXBoundary238981352416545728433--