1 - Make scripts_plugin email heuristic less stupid, or maybe
4 - Test head doesn't do quite the right thing with version numbers
5 (shouldn't git describe, instead should give a version infinitely
7 - Strategy introspection and disabling.
8 - prepare-config (and others) create .wizard dir even
9 when not strictly necessary
10 - Bug out immediately if tags are not present in the master tip
12 - pending doesn't seem to get written out properly sometimes (or
13 it's being deleted); this makes it hard to --continue on the
14 event of an upgrade failure. Also, we seem to bounce back to
15 the production copy to check pending even when we run --continue
17 - Newline checks are /really really/ expensive on AFS; see if
18 we can minimize them or something. Right now, we're testing
19 a fix where we don't clone with --shared.
20 - Replace .split("\n") with .splitlines()
22 - Need to fix existing repo history? (not adding extra commits;
23 that'll be more difficult)
25 git rebase -i -p --root --onto COMMITID
27 This won't work if you need to change the very root of the
28 repository. You'll probably end up with conflicts and have
29 to manually resolve everything afterwards.
31 But usually you won't need --root --onto unless you really
32 fucked up the pristine branch. If you just need to change
35 git rebase -i -p COMMITID
39 - [SCRIPTS] MediaWiki 1.6.7, 1.9.3 and 1.10.0
42 "Connection to scripts.mit.edu closed" is confusing
43 the URL should be easier to copy and paste, which means we should
45 We should ... upgrade our autoinstaller
46 Apparently installing WordPress updates or themes never indicates
47 completion, and just says "Downloading..", and you have to guess
51 - phpBB or phpbb? (right now it's the former)
52 - need an upgrade story; srv needs more versions
53 - need a story about install/ contrib/
55 - Give users a "certificate" of their merge, which they can
56 use to reuse that merge commit if something unrelated fails.
58 - Human readable quota output
59 - Nice error message on --continue if you forgot to git add your
60 resolved file (look for conflict markers)
61 - The merge interface is a kind of major UI disaster; you won't
62 be able to use it unless you know how Git works. Also, the
63 merges can be quite difficult to resolve if upstream has made
64 large formatting changes like reindenting. We may also consider
65 providing a --rebase option, which seems to do better when
66 big problems like this show up.
68 - Better mass-* support for just one user (this includes letting
69 a user mass upgrade just his own autoinstalls)
71 - Show progress or something when upgrading
72 - Allow 'sticky notes' for future upgraders to notice
73 - .wizard/url semantics are subtly wrong: in particular, if we
74 explicitly configure a URL at install, we should be able to
75 detect this URL as baked in from the configuration
77 - Rerere support doesn't actually work
78 - "Version 3.0.0 doesn't exist; did you mean 3.0?"
79 - Be a little more intelligent when perform web checks; for example,
80 if we get a forbidden message, that probably means we go the right
81 address but it's blocked off; if we get a 404 message, that probably
82 means wrong address. Account Unknown is something particularly good
84 - Wordpress module can do something intelligent if we get redirected
85 to the installation page.
86 - wizardResolve* files seem to get left in tmp en-mass, and we don't
89 - [SCRIPTS] Wordpress needs to get rid of the siteurl hack, so that it
90 actually has a fully-qualified URL http://foo.scripts.mit.edu/blah.
91 This will also fix Wordpress's cron functionality. We should be
92 careful not to write over users who are on vhosts. We should figure
93 out who is still on twiddle paths. We should make sure the redirect
96 - Remerges aren't reflected in the parent files, so `git diff` output is
97 spurious. Not sure how to fix this w/o tree hackery.
98 - Sometimes users remove files. Well, if those files change, they automatically
99 get marked as conflicted. Maybe we should say for certain files "if they're
100 gone, they're gone forever"? What is the proper resolution?
102 - Parse output HTML for class="error" and give those errors back to the user (done),
103 then boot them back into configure so they can enter in something different
105 - [SCRIPTS] If you try to do an install on scripts w/o sql, it will sign
106 you up but fail to write the sql.cnf file. This sucks.
108 - [SCRIPTS] Web application for installing autoinstalls has a hard
109 problem with credentials (as well as installations that are not
110 conducted on an Athena machine.) We have some crazy ideas involving a
111 signed Java applet that uses jsch to SSH into athena.dialup and
115 - Tidy up common code in callAsUser and drop_priviledges in shell;
116 namely cooking up the sudo and environment variable lines
117 - Summary script should be more machine friendly, and should not
118 output summary charts when I increase specificity
119 - util.fetch() should use urllib under the hood, not httplib. Code
120 has to be changed. We should log if we get redirected.
123 - Add support for mypristine workflow
124 - Figure out why Sphinx sometimes fails to crossref :func: but wil
125 crossref :meth:, even though the dest is very clearly a function.
126 Example: :func:`wizard.app.php.re_var`
127 - The TODO extension for Sphinx doesn't properly force a full-rebuild
128 - Make single user mass-migrate work when not logged in as root. The
129 primary difficulty is making the parallel-find information easily
130 accessible to individual users: perhaps we can do a single-user
131 parallel-find on the fly.
132 - Don't use the scripts heuristics unless we're on scripts with the
133 AFS patch. Check with `fs sysname`
134 - Make 'wizard summary' generate nice pretty graphs of installs by date
135 (more histograms, will need to check actual .scripts-version files.)
136 - It should be able to handle installs like Django where there's a component
137 that gets installed in web_scripts and another directory that gets installed
140 - [SCRIPTS] ACLs is a starting point for sending mail to users, but it
141 has several failure modes:
142 - Old maintainers who don't care who are still on the ACL
143 - Private AFS groups that aren't mailing lists and that we can't get
144 to A question is whether or not sending mail actually helps us:
145 many users will probably have to come back to us for help; many
146 other users won't care.
147 - Whatever happens here should be used to improve user.email()
149 [ XXX: metadata.rst ]
151 COMMIT MESSAGE FIELDS:
153 Installed-by: username@hostname
154 Pre-commit-by: Real Name <username@mit.edu>
155 Upgraded-by: Real Name <username@mit.edu>
156 Migrated-by: Real Name <username@mit.edu>
157 Wizard-revision: abcdef1234567890
158 Wizard-args: /wizard/bin/wizard foo bar baz
162 Committer: Real Name <username@mit.edu>
163 Author: lockername locker <lockername@scripts.mit.edu>
167 [ XXX: doc/deps.rst ]
168 * Some parts of the infrastructure will not be touched, although I plan
169 on documenting them. Specifically, we will be keeping:
171 - get-homedirs.sh. which needs to be run as root on scripts. Store
172 in /mit/scripts/sec-tools/store/scriptslist
174 - parallel-find.pl, and the resulting
175 /mit/scripts/sec-tools/store/versions
177 [ XXX: doc/deploy.rst ]
178 GET APPROVAL BEFORE PROCEEDING ANY FURTHER;
179 THIS IS PUSHING THE CHANGES TO THE PUBLIC
181 NOTE: The following commands are to be run on not-backward.mit.edu.
182 You'll need to add daemon.scripts-security-upd to
183 scripts-security-upd to get bits to do this. Make sure you remove
184 these bits when you're done.
186 10. Run `wizard research appname`
187 which uses Git commands to check how many
188 working copies apply the change cleanly, and writes out a logfile
189 with the working copies that don't apply cleanly. It also tells
190 us about "corrupt" working copies, i.e. working copies that
191 have over a certain threshold of changes.
193 11. Run `wizard mass-upgrade appname`, which applies the update to all working
196 12. Run parallel-find.pl to update our inventory
198 [ XXX: doc/metadata.rst ]
199 * The repository for a given application will contain the following files:
201 - The actual application's files, as from the official tarball
203 - A .scripts directory, with the intent of holding Scripts specific files
204 if they become necessary.
206 - .scripts/dsn, overriding database source name