• Software
• Assessment
• Documentation
• UpdateCycle
• step1

• To Software Software - To Software-Assessment - Software/Assessment - To Emergency Patches Process

• To Software-Assessment Documentation UpdateCycle

Software Development Update Cycle - Developer Tools Used

This page documents the proposed tools for Software Developers helping CAcerts new Software-Assessment team in fixing bugs.

This is work in progress

Step1, DevelopmentTools subpage ? instructions to create accounts/to connect to bugtracker, github, email mailing list

Documentation - Bug Tracker - bugs.cacert.org

• New bugs, feature requests and more will be documented under CAcert's bugtracker bugs.cacert.org

• If you do not have an account yet, create one to start as a developer

Source Repositories

• There is a main set of repositories with restricted access. From most of them you can download the sources.

Repository branches and the Access levels

• Developers branches	A	developers, Software-Assessment team	several
  Testserver branch	B	Software-Assessment team (only) (read/write)	cacert-devel
  Release candidate branch single bug# branch out of cacert-devel	C	Software Assessors (read,write)	cacert-devel bug-#
  production system cvs branch	cvs	Critical Sysadmins (on production system)	www.cacert.org/src-lic.php
  Production Mirror branch	D	Critical Sysadmins (write), Software Assessors (write), all (read)	cacert

Starting from current production revision

• Current production revision can be found under www.cacert.org/src-lic.php for direct download -or-

• via Git repository CACERT.git

Developer Git branches on Github

• If you don't have an account yet, goto https://github.com/plans and create a free account (0 Euro/mo - Free for open source)

Git Tutorial

• cli Tutorial

  • http://learn.github.com/p/intro.html

• a Challenage Tutorial

  • http://try.github.com/levels/1/challenges/2

• A Simple Guide in german Language

  • http://rogerdudler.github.com/git-guide/index.de.html

Email channels

Patches Delivery Channels

• Developers send their patches:

  1. thru their developers branch [A],

  2. through github developer branches
     (needs further documentation),

  3. by email (preferable as diff),
  4. by an attachment in the bug-tracker

     • by an attached diff (preferred) or updated/replacement file (deprecated) in the bug-tracker (BenBE)

  5. thru other channels

• to the Software-Assessment team.
  

• Status of bug in bugtracker switch to "Fix available"

Graphical Overview: Repository branches and the Access levels

See also: Software-Assessment Project meeting 2010-05-11

Links

• GIT Software Development Workflow (WIP)

• Software Assessment Process Cycle 2010-05-11

• CategorySoftware

• CategorySoftwareAssessment