Changeset 711 in project for README


Ignore:
Timestamp:
05/30/06 04:01:29 (12 years ago)
Author:
azul
Message:

More information for the new (backwards compatible) semantics for projects.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • README

    r121 r711  
    2222To gain write-access to the repository, contact felix@call-with-current-continuation.org,
    2323or ask on the CHICKEN mailing list.
     24
     25Each subdirectory for an egg should contain the following structure:
     26
     27- If the author doesn't want to use the Subversion eggs' repository
     28  much, just use it to occasionally upload releases, everything should
     29  go directly under eggname.  There should be a eggname/eggname.meta
     30  file with the semantics described bellow.
     31
     32- If the author does want to use the features provided by Subversion
     33  and make the eggs repository its main development repository, it
     34  should have the following structure:
     35
     36    trunk/ - Contains the latest (possibly experimental/unstable)
     37    version of the code.
     38
     39    branches/ - Contains, as subdirectories, any special branches of
     40    the code that need to be maintained apart of the trunk.
     41
     42    tags/ - Contains special tags for the code (such as those for each
     43    release).  Once created, a tag should never change (just like a
     44    release should never change).
     45
     46  This layout is explained in the book Version Control with Subversion
     47  and has become a standard for many projects.
     48
     49  To make a release the following should be done (where VERSION is of
     50  the form "1.0", "1.1", etc.):
     51
     52    svn cp eggname/trunk eggname/tags/VERSION
     53    svn ps latest VERSION eggname/tags
     54
     55  The ps (property set) sets a Subversion property on the tags
     56  directory for the egg with the name (version) of the latest release,
     57  to make it possible for tools (eg. egg-post-commit) to find it
     58  (without requiring any intelligence to compare version numbers on
     59  their part).
     60
     61  Note that every release must have the eggname.meta file with the semantics
     62  described bellow (and, for that reason, so should trunk/, even though nothing
     63  will read that file from there).
    2464
    2565If you make any changes and commit them to the repository, a script on the
Note: See TracChangeset for help on using the changeset viewer.