Changes between Initial Version and Version 1 of VarNames/RoadMap


Ignore:
Timestamp:
Feb 5, 2012 10:40:01 AM (6 years ago)
Author:
rado
Comment:

migrate wiki.mutt.org

Legend:

Unmodified
Added
Removed
Modified
  • VarNames/RoadMap

    v1 v1  
     1[[PageOutline]]
     2== Done, doing ==
     3
     4 * The VarNames/List of var-names itself.
     5  * keep up to date with newest releases.
     6
     7 * VarNames/Script to '''automatically''' translate the varnames in config files. '''Done'''!
     8  * It's safe for configs of regular use for almost all users. Rare special cases with mutt-config generator scripts '''may''' fail,
     9   * but those users are typically capable to fix exceptions quickly, which are few anyway (no production config failure reported yet).
     10  * Try VarNames/Script + VarNames/Test, report failures to be fixed.
     11
     12 * Timetable for Transition where '''both''' variants will be valid. Idea: by 2.0 new names should be '''established well enough''' to drop old pre 1.6 names safely.
     13  * 1.6 will still have old ones only,
     14  * 1.7 - 1.999 will have both.
     15  * 2.0 will have only new ones. If it comes too early, extend to 2.2 or 2.4
     16
     17 * New "muttrc2" to check as config first, so you can keep both config versions around independent of version number for different binaries (pre- + post-change).
     18  * version specific feature exists already: suggest to use generic muttrc for "current/ newest", version specific for old dying versions.
     19  * VarNames/Script easily produces required new version.
     20
     21== To Do ==
     22
     23 * Re-work the manual so what gets committed must be a huge update to make things more consistent in total at once.
     24
     25 * Rewrite the manual (not just re-organize) to reflect groups of "tasks" and such.
     26  * Structure per MuttGuide or UseCases???
     27
     28 * '''BIG''' warning at end of build process to inform sys- and distro- admins, so they can inform and aid their users (see "script" above).
     29  * A "post-install" script can be applied to automatically convert configs when updating,
     30   * basically: `for all in /home/*; do mkdir $all/.mutt2; /Script $all/.mutt $all/mutt2; done`
     31   * Check for whether file or dir: `if [ -e $all/.muttrc ]; then convert .muttrc; fi; if [ -e ~/.mutt/muttrc ]; then convert ~/.mutt; fi`
     32
     33 * contact distro mutt-maintainers to discuss automatic update ideas. Add distros' mutt-contacts for completeness to MuttPeople.
     34
     35 * PR campaign to spread the word,
     36  * i.e. mutt 2.0 could possibly make the media catch up (so that people can read about it in the news, not when updating).
     37  * news sites to contact:
     38   * heise.de, ...
     39
     40== Ideas needed ==
     41
     42 * Documentation of synonyms:
     43  * How to document old + new vars to make manual.txt useful for both while in transition?
     44   * Translation table?
     45   * List both entries in title of desc.?
     46   * ...? (what else)
     47  * Will have to be manually made (except for output of VarNames/Script), no automation, would be just once anyway.