5 - MediaWiki 1.9.3 and 1.6.7
7 - If no newlines at all, DON'T CARE (don't rewrite the file again!)
9 - Check for improper use of os.exists() when os.lexists() was meant
11 - Add support for mypristine workflow
12 - Wordpress needs to get rid of the siteurl hack, so that it actually
13 has a fully-qualified URL http://foo.scripts.mit.edu/blah. This will
14 also fix Wordpress's cron functionality. We should be careful not
15 to write over users who are on vhosts. We should figure out who is
16 still on twiddle paths. We should make sure the redirect is handled
19 - Remerges aren't reflected in the parent files, so `git diff` output is
20 spurious. Not sure how to fix this w/o tree hackery.
21 - Sometimes users remove files. Well, if those files change, they automatically
22 get marked as conflicted. Maybe we should say for certain files "if they're
23 gone, they're gone forever"? What is the proper resolution?
25 - Parse output HTML for class="error" and give those errors back to the user (done),
26 then boot them back into configure so they can enter in something different
28 - If you try to do an install on scripts w/o sql, it will sign you up but fail to write
29 the sql.cnf file. This sucks.
31 - Web application for installing autoinstalls has a hard problem
32 with credentials (as well as installations that are not conducted
33 on an Athena machine.) We have some crazy ideas involving a signed
34 Java applet that uses jsch to SSH into athena.dialup and perform
38 - Tidy up common code in callAsUser and drop_priviledges in shell;
39 namely cooking up the sudo and environment variable lines
40 - Summary script should be more machine friendly, and should not
41 output summary charts when I increase specificity
44 - Figure out why Sphinx sometimes fails to crossref :func: but wil
45 crossref :meth:, even though the dest is very clearly a function.
46 Example: :func:`wizard.app.php.re_var`
47 - The TODO extension for Sphinx doesn't properly force a full-rebuild
48 - Make single user mass-migrate work when not logged in as root. The
49 primary difficulty is making the parallel-find information easily
50 accessible to individual users: perhaps we can do a single-user
51 parallel-find on the fly.
52 - Don't use the scripts heuristics unless we're on scripts with the
53 AFS patch. Check with `fs sysname`
54 - Make 'wizard summary' generate nice pretty graphs of installs by date
55 (more histograms, will need to check actual .scripts-version files.)
56 - It should be able to handle installs like Django where there's a component
57 that gets installed in web_scripts and another directory that gets installed
60 - ACLs is a starting point for sending mail to users, but it has
61 several failure modes:
62 - Old maintainers who don't care who are still on the ACL
63 - Private AFS groups that aren't mailing lists and that we
65 A question is whether or not sending mail actually helps us:
66 many users will probably have to come back to us for help; many
67 other users won't care.
71 COMMIT MESSAGE FIELDS:
73 Installed-by: username@hostname
74 Pre-commit-by: Real Name <username@mit.edu>
75 Upgraded-by: Real Name <username@mit.edu>
76 Migrated-by: Real Name <username@mit.edu>
77 Wizard-revision: abcdef1234567890
78 Wizard-args: /wizard/bin/wizard foo bar baz
82 Committer: Real Name <username@mit.edu>
83 Author: lockername locker <lockername@scripts.mit.edu>
88 * Some parts of the infrastructure will not be touched, although I plan
89 on documenting them. Specifically, we will be keeping:
91 - get-homedirs.sh. which needs to be run as root on scripts. Store
92 in /mit/scripts/sec-tools/store/scriptslist
94 - parallel-find.pl, and the resulting
95 /mit/scripts/sec-tools/store/versions
97 [ XXX: doc/deploy.rst ]
98 GET APPROVAL BEFORE PROCEEDING ANY FURTHER;
99 THIS IS PUSHING THE CHANGES TO THE PUBLIC
101 NOTE: The following commands are to be run on not-backward.mit.edu.
102 You'll need to add daemon.scripts-security-upd to
103 scripts-security-upd to get bits to do this. Make sure you remove
104 these bits when you're done.
106 10. Run `wizard research appname`
107 which uses Git commands to check how many
108 working copies apply the change cleanly, and writes out a logfile
109 with the working copies that don't apply cleanly. It also tells
110 us about "corrupt" working copies, i.e. working copies that
111 have over a certain threshold of changes.
113 11. Run `wizard mass-upgrade appname`, which applies the update to all working
116 12. Run parallel-find.pl to update our inventory
118 [ XXX: doc/metadata.rst ]
119 * The repository for a given application will contain the following files:
121 - The actual application's files, as from the official tarball
123 - A .scripts directory, with the intent of holding Scripts specific files
124 if they become necessary.
126 - .scripts/dsn, overriding database source name