jQueryUI DB - Multiple release versions

gistfile1.md

Effort estimation plan (aka guess)

frontend

• show multiple versions; 1h 👍
• handle different components list per different jQueryUI version; 4h 👍

backend:

• grunt prepate: 4h 👍
  • instead of getting user input, read config file and prepare all jQueryUI versions presented there;
  • iterate over all config-jQueryUI-versions on {checkout, install, build, copy};
• grunt build:
  • iterate over all config-jQueryUI-versions; 1h 👍
• release model (lib/release.js): 1h 👍
  • check if all config-jQueryUI-versions have been prepared;
  • other than that: done;
• builder model (lib/builder.js):
  • cache the files of all releases; 4h 👍
  • parameterize #build and #writeTo with 'version'; 2h 👍
  • error handling: catch wrong components; 1h 👍
• DB controller (download.js) 1h 👍
  • pass all config-jQueryUI-versions to renderer;
  • pass new variable 'version' to build;
• unit test
  • iterate over all config-jQueryUI-version; 3h 👍

Issues

backend:

• grunt prepare:
  • figure out how to map: documentation vs. jQueryUI version; 3h 👍

Total

Total effort estimation: 25h (1w in a 5h/d basis)

Premises

• ThemeRoller will show all the components of the latest UI version;
• Although on different versions we may add components, its file structure will remain the same. If we change anything from one place to another or any naming scheme, this might brake builder.