Changes between Version 17 and Version 18 of ShrMaintainerHowTo


Ignore:
Timestamp:
10/18/10 22:34:22 (3 years ago)
Author:
tim_abell
Comment:

info and ideas from email discussion

Legend:

Unmodified
Added
Removed
Modified

  • ShrMaintainerHowTo

    v17 v18  
    5656 * Published version should always build without error (i.e. test locally before pushing). 
    5757 * Provide smaller / alternate temporary patches that alleviate user pain when the fix on shr-unstable is too radical. 
     58 * full availability of build sources, mirrored (perhaps similar to debian's src package system) 
    5859 
    5960=== Maintenance === 
    … …  
    8586== Who's who == 
    8687 
     88=== Beta testers for shr-t === 
     89 * Nick - [http://lists.shr-project.org/pipermail/shr-user/2010-October/006482.html happy to], also interested in maintainer role but currently too short of time 
     90 * Ben Thompson - [http://lists.shr-project.org/pipermail/shr-user/2010-October/006483.html happy to test images] 
     91 
    8792=== Potential maintainers === 
    88  * [http://www.timwise.co.uk/ Tim Abell] - (active interest but nothing concrete yet) 
     93 * [http://www.timwise.co.uk/ Tim Abell] - working on guidelines, build process and community 
    8994 * Neil Jerram - [http://lists.shr-project.org/pipermail/shr-user/2010-October/006401.html expressed an interest on the mailing list] 
     95 * Thomas Zimmermann - [http://lists.shr-project.org/pipermail/shr-user/2010-October/006484.html will help after 9th nov 2010] 
    9096 
    9197=== Previous maintainers === 
    … …  
    104110due to the high right of churn it is currently hard to keep even a testing version vaguely stable, often being faced with a bugfix being presented as a complete rewrite (potentially incompatible with other items thus forcing wholesale package upgrades or introducing new bugs due to immaturity of the new code). 
    105111 
     112=== alternative approaches === 
     113 
     114It is possible that we could leverage debian's existing build systems, community structure etc by getting the debian phone working sufficiently to make shr-t irrelevant. Some work has already been undertaken along this line of work. There is however no issue with pursuing both approaches simultaneously therefore generating more choice for fso users. There is also the hackable:1 project should you particularly want to use debian. 
     115 
    106116=== Further reading === 
    107117 * Ubuntu's "stable release process" https://wiki.ubuntu.com/StableReleaseUpdates i.e. how they decide what and how updates should be provided for stable releases of Ubuntu 
     118 * Tim's rfc and subsequent thread: http://lists.shr-project.org/pipermail/shr-user/2010-October/006481.html