Developers information: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→development coordination: restaructure) |
||
| Line 1: | Line 1: | ||
= | = coordination = | ||
* [[ | * [[development plan]] - long term plan, notes and status of some bigger developments | ||
* [[etch-doc-todo | List of BUGS important for correct documentation for FAI in Etch]] | * [[etch-doc-todo | List of BUGS important for correct documentation for FAI in Etch]] | ||
* [[ | * [http://faiwiki.informatik.uni-koeln.de/rails/todos/list todo list] of things most important needed to be done next: | ||
* [[people branches]] - people branches and what they're aimed at | |||
= documentation = | |||
* [[fai subversion howto]] - what you need to know to develop fai within the subversion repository on alioth | * [[fai subversion howto]] - what you need to know to develop fai within the subversion repository on alioth | ||
* [[testing]] - general information on FAI development testing, and documentation of [[testcases]] and a [[test plan]] for the development - who tests what and how. Eventually we want to have a system so developers can report the results of their tests, as long as we don#t have that fully automated, which will take a while. | * [[testing]] - general information on FAI development testing, and documentation of [[testcases]] and a [[test plan]] for the development - who tests what and how. Eventually we want to have a system so developers can report the results of their tests, as long as we don#t have that fully automated, which will take a while. | ||
= communication = | |||
* [[linux-fai-devel mailing list info]] - netiquette, how to subscribe and use | |||
= FAI pages in the Debian Bug Tracking System(BTS) = | = FAI pages in the Debian Bug Tracking System(BTS) = | ||
Revision as of 09:56, 5 July 2007
coordination
- development plan - long term plan, notes and status of some bigger developments
- List of BUGS important for correct documentation for FAI in Etch
- todo list of things most important needed to be done next:
- people branches - people branches and what they're aimed at
documentation
- fai subversion howto - what you need to know to develop fai within the subversion repository on alioth
- testing - general information on FAI development testing, and documentation of testcases and a test plan for the development - who tests what and how. Eventually we want to have a system so developers can report the results of their tests, as long as we don#t have that fully automated, which will take a while.
communication
- linux-fai-devel mailing list info - netiquette, how to subscribe and use
FAI pages in the Debian Bug Tracking System(BTS)
- unstable
- testing
- stable
- http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=fai;pri0=tag:svn-trunk;pri1=severity:critical,grave,serious,important,normal,minor,wishlist - display fixed in svn-trunk bugs first, then open bugs ordered by priority
FAI pages in the Debian Quality Assurance (QA) system
Subversion repository access
- svn co svn://svn.debian.org/svn/fai/trunk fai-sources
- http://svn.debian.org/wsvn/fai
other stuff
- TODO: fill pages linked here with content:
- developer FAQ from the mailing list and irc channel