Custom Query (1173 matches)
Results (7 - 9 of 1173)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#146 | fixed | Make messaging system testable | ||
Description |
We should make it possible to test the messaging system. If you look at mediagoblin/utils.py you can see what happens when we \_activate\_testing() for some other things... ie, we insert template context info like so: :: if TESTS_ENABLED: TEMPLATE_TEST_CONTEXT[template_path] = context Maybe we should do something similar with messaging? Either we should store in a dictionary like TEMPLATE\_TEST\_CONTEXT, maybe TEST\_MESSAGES (which gets wiped by clear\_test\_buckets()) or we should store in the session like request.session['test\_messages'] (should also get wiped by clear\_test\_buckets()) I'm assigning this to Caleb Davis who I think is a good fit for it. |
|||
#178 | fixed | Have a Users page that lists all the users on a given install | ||
Description |
Right now, I have no way of telling how many users are on the site or any way of seeing their profiles (other than clicking on another user's photo and clicking their name on the photo page). If we're going to have user profiles, let's have a way of finding other users! |
|||
#187 | no-action | add gnu ftp system to release process | ||
Description |
This covers some research and also some tweaks to our process. GNU requires that we push tarballs to their ftp server. `http://www.gnu.org/prep/maintain/html\_node/Automated-FTP-Uploads.html <http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html>`_ So we need to figure out the following: 1. how do we get set up with that? 2. how do we add it to our release process? Grabbing this one and putting it in the 0.0.5 target. |
Note:
See TracQuery
for help on using queries.