Changeset 685c4ef for doc


Ignore:
Timestamp:
2005-11-17T12:51:50Z (19 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
834ff44
Parents:
ea85a0b
Message:

Removed the note about version control from the FAQ

File:
1 edited

Legend:

Unmodified
Added
Removed

  • doc/FAQ

    rea85a0b r685c4ef  
    3838   artistic creativity.
    3939
    40 Q: Why is there no mailing list/CVS/<insert your favourite development tool
    41    here>?
    42 A: Short answer: we don't need it.
    43    
    44    Longer answer: and we're not completely convinced of their merits.
    45    
    46    Long answer: we currently use some shell scripts which make sure all
    47    developers' copies are in sync with Wilmer's master copy. These shell
    48    scripts also produce development "releases" and packages, as well as
    49    stick them on a http-server. Patches are sent to Wilmer who decides
    50    whether or not a patch should be applied and if it may need some
    51    additional changes. This has the consistency advantage of a one-person
    52    project while having the capacity of more people available. The system
    53    works and we are kind of attached to it.
    54    
    5540Q: When is $random_feature going to be implemented?
    5641A: Please do consult doc/TODO (preferably in a development snapshot, which
Note: See TracChangeset for help on using the changeset viewer.