Difference between revisions of "User:Ryan52/todo"
Jump to navigation
Jump to search
(→queue + 3: another cashier code enhancement) |
(more rearranging) |
||
| Line 61: | Line 61: | ||
** [[FGRT: 16673 | #16673]] eleminate cashier_created_by? | ** [[FGRT: 16673 | #16673]] eleminate cashier_created_by? | ||
** [[FGRT: 15498 | #15498]] should not recheck the same cashier code | ** [[FGRT: 15498 | #15498]] should not recheck the same cashier code | ||
| + | * get fgdb.rb able to be set up by new freegeeks and new coders | ||
| + | ** [[FGRT: 15738 | #15738]] mutate the returns too in data-mutate | ||
| + | ** [[FGRT: 15523 | #15523]] fgdb can't be set up from scratch atm (broken devel data) | ||
| + | ** [[FGRT: 14227 | #14227]] Fix docs on how to install FGdb | ||
== queue + 4 == | == queue + 4 == | ||
| Line 68: | Line 72: | ||
* [[FGRT: 17031 | #17031]] integrate meeting-minder functionality into skedjulnator | * [[FGRT: 17031 | #17031]] integrate meeting-minder functionality into skedjulnator | ||
| − | == | + | == queue + 5 == |
| − | + | what's left release | |
| − | + | ||
* changes to the contact widget | * changes to the contact widget | ||
** need to think this through. | ** need to think this through. | ||
| Line 79: | Line 83: | ||
*** [[FGRT: 14828 | #14828]] FGDB feature request #2 | *** [[FGRT: 14828 | #14828]] FGDB feature request #2 | ||
*** [[FGRT: 15034 | #15034]] add show more button on contact search | *** [[FGRT: 15034 | #15034]] add show more button on contact search | ||
| − | |||
| − | |||
| − | |||
| − | |||
* fix up form_has_not_been_edited | * fix up form_has_not_been_edited | ||
** [[FGRT: 15921 | #15921]] form_has_not_been_edited isn't called on edit links, I think | ** [[FGRT: 15921 | #15921]] form_has_not_been_edited isn't called on edit links, I think | ||
** [[FGRT: 15922 | #15922]] form_has_not_been_edited shouldn't be called on destroy | ** [[FGRT: 15922 | #15922]] form_has_not_been_edited shouldn't be called on destroy | ||
| − | |||
* [[ FGRT: 16108 | #16108]] gizmo_types with same name and different effective date ranges should act sanely in reports | * [[ FGRT: 16108 | #16108]] gizmo_types with same name and different effective date ranges should act sanely in reports | ||
| + | |||
| + | == junk == | ||
* go through remaining trac tickets: | * go through remaining trac tickets: | ||
** [http://dev.freegeek.org/projects/fgdb.rb/report/1 fgdb.rb tickets] | ** [http://dev.freegeek.org/projects/fgdb.rb/report/1 fgdb.rb tickets] | ||
| Line 97: | Line 98: | ||
*** looks like it's already in rails itself... :autosave | *** looks like it's already in rails itself... :autosave | ||
**** need to test though. and why did none of the sites that I found in the process of figuring this out show it? | **** need to test though. and why did none of the sites that I found in the process of figuring this out show it? | ||
| − | |||
| − | |||
| − | |||
* release utilities | * release utilities | ||
** test if the auto-update script works | ** test if the auto-update script works | ||
Revision as of 00:48, 27 March 2010
not fgdb
- User:Ryan52/maintenance
- ASS
- hard drive tester
- keyboard tester
- #15784 Newfangled keyboard tester addition request/issues
- #16161 additional function keys (F13 - F16) as well as the volume/eject keys to (volume up/down/mute keys)
- #16162 Macs: the equal (=) sign on the number pad never shows up as working
- #16163 larger title for the keyboard type
- #16164 screenshots of each layout and the settings screen
queue
the next release
- remove "def parent" from volunteer_task_types at next release (1.0.49). it is currently needed in the migration, but otherwise unused.
- foreign key overhaul
- #16932 Adjustments in gizmo counts
- #17660 fix up the points trading interface
- #16835 make an interface for editing a worker's worker_type
queue + 1
the old shit release
queue + 2
the library release
queue + 3
the unimportantish release
- #14985 privilege to role mapping for database users
- User:Ryan52/roles
- ack "(requires_(role|staff)|is_staff|has_role)" app/
- #16933 privileges for tech support role
- #15050 people with TECH_SUPPORT role should imply the CONTACT_MANAGER
- #17210 store or at least store admin should imply contact manager
- should happen after library branch for sidebar stuff
- link to old system IDs on the systems page as well
- #17231 "current" system ids
- cashier code enhancements
- get fgdb.rb able to be set up by new freegeeks and new coders
queue + 4
the cool toy release
queue + 5
what's left release
- changes to the contact widget
- fix up form_has_not_been_edited
- #16108 gizmo_types with same name and different effective date ranges should act sanely in reports
junk
- go through remaining trac tickets:
- old TODO list
- my crazy ideas that will just make fgdb.rb that much more awesome
- #16514 create a plugin that will improve partial updates (by freezing attributes)
- #16513 create a plugin which will make records associated by has_many (optionally?) saved when the parent record is saved
- looks like it's already in rails itself... :autosave
- need to test though. and why did none of the sites that I found in the process of figuring this out show it?
- looks like it's already in rails itself... :autosave
- release utilities
- test if the auto-update script works
- test if test-migrate will work with other branches
- the auto-update script is connected to my home dir (because of the devel checkout), but it shouldn't be.
- use multiple working copies from the production checkout: http://kerneltrap.org/mailarchive/git/2007/10/11/335637
- or just create a dbadmin user on arik
- benefit of possibility of having a key connected to devo.
- update Committing to FGdb after that.
- I want all changes on a release_X.X.X branch (after the initial branch) to get their own tag. this would involve running ./script/mini-release (new script?) when making a direct change, and this would affect the output of ./script/version. mini-release would also close the ticket(s) (by pushing the tag, I guess). also, this would mean that pushes on release_X.X.X branches wouldn't close the tickets. this would also affect the changelog workflow probably.
- I wonder, could we have root mail go to an RT queue.