AGTEK R & D Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== October Suprise ====== 

Earlier track system work for 2014 was completed here:

Most of the track work needed to be integrated into the trunk code line and then deployed. For October/November 2014 an Access Project is as follows:
  * Merge Access Track 1.20 into the trunk.
  * Adjust the application version table to be able to lock out updates (except for AGTEK) add simple descriptive text.
  * Add a report being requested by the AGTEK Business office.
  * Upgrade the server to a medium instance, prep the way for a dual server instance.

====== Story 4 - October Suprise ======

 **Start** 2014-10-13

^ Task Number   ^ Owner    ^ Estimate ^ Actual ^ Status ^ Description   ^ 
| **4.1**       |          |          |       |        | Deploy 1.20 on production server |
| 4.1.1         |  Mike A  |  1       |   0   |  Done  | Merge 1.20 to trunk | 
| 4.1.2         |  Mike A  |  2       |   1   |  Done  | Test against a production MySQL copy to test upgrade state |
| 4.2           |  Mike A  |  1       |       |        | Bring up medium instance on AWS |
| 4.3           |  Mike A  |  1       |       |        | Build utilization report |
| **4.4**       |          |          |       |        | Adjust update table to lock out updates for all but AGTEK |
| 4.4.1         |  Mike A  |  1       |  0.5  |  Done  | Extend table for new attributes, extend update msg in protobuf |
| 4.4.2         |  Mike A  |  1       |  0.5  |  Done  | Adjust logic in server update check to obey "restrict" |
| 4.4.3         |  Mike A  |  1       |       |      | Modify support tool to allow for "restrict" lock on app |
| **Total**     |          |  **8**   |  **X**  |    |    |

Story Velocity == 

Complete
AGTEK R & D Wiki

User Tools

Site Tools

Page Tools
