Welcome LAN Party administrators! By now you've surely joined the hundreds of LAN Parties worldwide that enjoyed the many benefits of using the Autonomous LAN Party project at their event. We hope that it has been useful in coordinating tournaments, game servers, and caffeine consumption. Unfortunately, it is with dismay that I must announce the nerdclub programming team has disbanded some time ago and will no longer be holding LAN events or developing the project. However, our love for tournaments and the competitive spirit is not dead. Many years and programming experience level-ups later, we've decided to continue the project's core focus in a new tournament administration website: Tournology.

Tournology will focus on the tournament administration and participation aspects for all types of events, as well as serving as a toolkit to be integrated into other niche software packages requiring a simple, easy, usable tournament solution.

Curious to learn more about Tournology? Check out tournology.com
coWiki 0.4.0-dev
.home .download .features .forum .help .wiki .credits
Current user:   guest    Change     Preferences 
   List directory   History   Similar   Print version   Edit 
ALP 
   Features 
ALP Documentation 
   Installation Help 
   FAQ 
   Using ALP 
   Game Server Queries 
   Tournament Checklist 
LAN Party Guide 
   Networking Tips 
   Power Tips 
Game Quick Guides 
   Demo & Screenshot Commands 
   Game & Query Port List 
   Unreal Tournament 

Referrers
znakoma.website.org
znakoq.e.gp
znakow.e.gp
znakoe.ec.gp
znakor.edu.ms
znakot.eg.gp
znakoy.ehrlos.de
znakou.eicht.de
znakoi.einbiegen.de
...koo.eingewechselt.de
ALP > Subversion Repository Design

 
rw-rw-r--   guest   guests

Subversion Repository Design

The base of the Subversion repository will probably contain the ALP root as imported from CVS. We will start with a new SVN root for ALP 2. This will be best called something like alp_project or alp_core

The heirarchy that will be used is described in detail below:

  • alp_root - the base of the repository
    • branches - sub-projects and bugfix development
      • alp_1 - alp version 1 development and bigfixes
      • 2.0.x - bugfix work on tagged releases
      • themes - bugfix work on tagged themes
    • tags - collection of snapshots for each web release
      • 2.0.xxx - tagged web releases for reference
      • STABLE - stable tag constantly updated with latest stable release
      • TESTING - latest tagged release in testing
    • trunk - current project development
      • alp - main application tree
        • htdocs - alp application files (the stuff users unzip to their server..)
          • app - alp cake app files
          • cake - cake vendor merge from /vendor/cake/current
        • docs - install, usage and license documentation
        • upgrade - potential location for upgrade files and scripts depending on install script setup we choose
      • themes - theme development tree
    • vendor - vendor code drops to be included in the main project
      • cake - cakephp vendor tree
        • current - current version, update this one then create tag
        • 1.1.15.5144 - tagged version from vendor


Reference Subversion Repository Design
http://www.nerdclub.net/alp/cowiki/ALP/SubversionRepositoryDesign

Comments: 0 New comment

Prev. Quick Refrence   CodeIgniter Planning Next


SourceForge.net Logo
 ©2004 the nerdclub programming team | nerdclub.net.
Driven by coWiki 0.4.0-dev (August 2, 2004) web collaboration tool.