1 #!perl

     2 # Copyright (c) 2000-2009 Nokia Corporation and/or its subsidiary(-ies).

     3 # All rights reserved.

     4 # This component and the accompanying materials are made available

     5 # under the terms of the License "Eclipse Public License v1.0"

     6 # which accompanies this distribution, and is available

     7 # at the URL "http://www.eclipse.org/legal/epl-v10.html".

     8 # 

     9 # Initial Contributors:

    10 # Nokia Corporation - initial contribution.

    11 # 

    12 # Contributors:

    13 # 

    14 # Description:

    15 # 

    16 #

    17 # Description:

    18 # MakingReleases

    19 #

    20 

    21 =head1 Overview

    22 

    23 

    24 

    25 =head1 Fundamental Concepts

    26 

    27 Consider a project that is being developed by three geographically separated sites (A, B and C). Each site is contributes various pieces of software. Site A is responsible for coordinating the software deliveries between all sites. It is critical that all sites develop against a common environment.

    28 

    29 The release tools provide an efficient means for the different sites to share environments with one another. Each site defines its deliverables as components (a single site may have a single component, or several smaller ones). B<Arrrgggg, this section needs more thought!!>

    30 

    31 =head1 Considerations Before Making a Release

    32 

    33 Component releases are fundamentally mechanism for distributing binary files. Source files may also be distributed, but the binary files are the key focus. The release tools are not intended to be a replacement for conventional source control systems. However they do allow sites to store in their source control system only the files that they actually own, and rely on the binaries distributed by the release tools to complete their environment. Source for these binaries may be available for debugging purposes according to licensing agreements.

    34 

    35 So the release tools are generally used in conjunction with a source control system during development. Individual developers will use the command C<GetEnv> to install a particual environment onto their workstation. They would then check out of the source control system the components they plan to work on, make changes and perform builds to test those changes.

    36 

    37 =head1 COPYRIGHT

    38 

    39  Copyright (c) 2000-2009 Nokia Corporation and/or its subsidiary(-ies).

    40  All rights reserved.

    41  This component and the accompanying materials are made available

    42  under the terms of the License "Eclipse Public License v1.0"

    43  which accompanies this distribution, and is available

    44  at the URL "http://www.eclipse.org/legal/epl-v10.html".

    45  

    46  Initial Contributors:

    47  Nokia Corporation - initial contribution.

    48  

    49  Contributors:

    50  

    51  Description:

    52  

    53 

    54 =cut