create new tag
, view all tags

TWiki DEVELOP Branch

ALERT! NOTE: The DEVELOP branch has been discontinued, it is replaced by the svn trunk.

  • All code development is done in twiki/trunk/core of the TWiki SVN repository
  • All plugin development is done in the twiki/trunk
  • Access the twiki/trunk at http://svn.twiki.org/svn/twiki/trunk
  • All major and minor releases are tagged and branched off the truk
  • After each major or minor release a TWikiRelease##x## branch is created from which patch releases are tagged. Very urgent bugfixes for core and default plugins are merged from the trunk to Release branch.
  • The DEVELOP and TWikiRelease04x00 branches are discontinued and blocked for further checkins
  • Report bugs using create new Bug report - DEVELOP Bug system
  • TWiki's Subversion requires all changes to be logged against Items in the Bugs system above. see SubversionReadme

ALERT! NOTE: Below content is no longer relevant

TWiki DEVELOP Branch

The DEVELOP branch is focused on taking TWiki into the future. To do this we require a strong focus on TestCases, UnitTests and Documentation, and the strength to ignore the possibility of breaking something (unless TestCases/UnitTests are provided). We cannot continue to avoid making radical changes for fear of possibly breaking legacy code. We must focus on dealing more effectivly with legacy TestCases, while moving forward towards a faster, more deterministic, lighter TWikiCore.

Read HowDoesTheDEVELOPBranchWork to check out the DevelopBranch via SVN or see a live demo from the current branch.

As code and ideas mature, they will be moved into the MAIN TWiki branch (preferably by people who maintain legacy TWiki Applications). In the process we should be able to provide conversion tools for any radically changed syntax or semantics.

Because there will be some diversion between the functionality of MAIN and DEVELOP, it is important to realise that the Documentation on twiki.org is for the MAIN codebase, while that in DEVELOP will need to be elsewhere.

I would prefer to use SVN for everything, Tests, Documentation and Code, as that will improve the repeatibility and maintenence of the solution, but this is a long term goal, requiring a number of system configuration changes, and the writing of a SVN based Store.

In the short term, we should move aggressively in the direction of moving documentation and testcases into subversion, and using a scripted install to maintain the developer environment using these topics. This is relatively trivial to do.

I propose we:

  1. move a copy of the Cairo release files into DEVELOP SVN (without ,v) - DONE
  2. move the TestCases into a TestCases Web in DEVELOP SVN - DONE
  3. at the end of every SvnUpdate (every 5 minutes) run "perl test/runtest.pl %outputDir%" from the DEVELOP directory (results will be put in http://develop.twiki.org/users/develop/pub/TestOutput/runtest.html) - DONE
  4. run GenDocs - e.g. shows smellyiness - CodevDocumentationProject style
  5. every 12 hours, "perl tools/builddistros.pl %outputDir%" will be run, with output files expected in http://develop.twiki.org/users/develop/pub/BuildDistros/index.html - DONE
  6. remove the copies of CPAN from SVN, and replace them with a script that can be run from builddistros.pl (with roll back to a previous version if tests fail?)

Constant work for all DEVELOP'ers

  1. Developers on DEVELOP use this setup, allowing them to edit and commit DEVELOP topics, code and tests from that CheckOut
  2. work to validate and simplify that docco (while writing TestCases and UnitTests for those feature)
  3. continue to allow the re-development of existing features, and the addition of new ones, with a focus to implementing a small tight, generic TWikiCore, while moving lesser used, or customisable, or legacy, or contentious features into Plugins
  4. provide migration tools for TestCases from Legacy TWikiApplications
  5. pursue Web based configuration tools (preferably as a TWikiApplication based on Plugins)
  6. pursue Web deployment of TWikiApplications with dependancies

  • develop a spell checker that fixes Sven's bad grammar and spelling

Want to take part in development?

Go to HowCanIContribute and check out HowDoesTheDEVELOPBranchWork.

ALERT! Create TWikiGuestWouldLikeToCheckIn to ask for SVN access; give a short introduction of yourself.

Edit | Attach | Watch | Print version | History: r35 < r34 < r33 < r32 < r31 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r35 - 2008-02-17 - SvenDowideit
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.