Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • document eclipse FTL configuration for hot FTL pages
  • Proposal - One timeboxed story on FTL spike - MIFOS-4409      4409       
  • Measure speed of migration of another area of Mifos. Compare established baseline (12 or so data points of historical LOC counts from git) with these new measurements.

...

  • technical improvements
    • enable instant reloading of Freemarker templates
      • (Stanley was saying he was able to hook it up to WTP and hot
        deployments?)
      • Michael Vorburger is also working on dev setup improvements, which
        includes the promise of instant FTL reloads
      • have early UI walkthrough on dev box with PM and QA
    • use JRebel
    • spend time summarizing and adding transparency to off-list work by
      Stanley Kwok & Michael Vorburger
    • could we use Spring Roo on top of Services/ServiceFacades?
    • better templates
      • reusable css pieces (use Compass?)
      • reusable ftl widgets
    • do pagination on client side with jQuery plugins such as http://www.datatables.net. Right now pagination is handled by TableTag class.
    • standardize the location of web resources (css, js ...)
    • construct breadcrumb automatically? some ideas:
  • measuring/managing the effort
    • as a control to measure against: estimate of how fast it's been going
      in the past e.g. Product Mix page took x days and had 23 bugs logged on
      new implementation
    • measures: what is the time required to build new FTL; how many bugs
      found by QA during manual testing; number of automated tests and time
      to write new automated tests
    • may need to measure twice - once on first try where we have trial
      and error, then second time with better defined
    • show how are new ideas are speeding up the process
  • team for sprint
    • multiple devs
    • fast feedback: tight integration w/testers
      • some testing happening every day
  • QA effort includes
    • new acceptance test for page (or fix/improve old test)
    • manual test pass to see if any bugs can be found in new FTL
    • seperate but associated spike on building API test for create Savings
      account
  • logistical/infrastructure improvements
    • make sure all devs have fast hardware / fast internet

...