Loading...
 
Skip to main content

History: CvsEtiquette

Preview of version: 2

CVS Etiquette

  • after branching no reformatting of code is allowed. Developers have to live with bad identination or bad line delimiters. As soon as the code runs everywhere, it's o.k.
  • If developers use new editors/cvs tools they should ensure that the tools don't change whitespace (tabs to spaces and CR/LF to LF or vice versa)
  • New features in HEAD, fixes in BRANCH-X-X. If unsure, ask project admins on irc or in devel list.
  • If unsure, developers should do a cvs diff before cvs commit to ensure that they only commit changes they want to commit.
  • merging bugfixes to the HEAD branch should occur at least every week. If blocking bugs are fixed, merging should be done as soon as possible. Merging has to be coordinated in IRC and has to be done by special instructed persons (need some cvs understanding, that's all).

History

Information Version
Damian Parker Changed from being 1.8 specific 6
View
tro sp/gram 5
View
Mose 4
View
Florian Gleixner 3
View
Florian Gleixner 2
View