Meta: maintenance tasks for next release

[usmonster]

Some stuff to do for v1.2.0:

• Reevaluate this list! Move some tasks to other tickets/releases, possibly use "Projects"?
• merge develop branch into master
• delete develop branch
• merge master branch into gh-pages
• Update README:
  • Update the list of features to be more comprehensive
  • Maybe add comparison to other Gantt implementations out there?
  • Merge in updated CONTRIBUTORS file content into its own section (can add back CONTRIBUTING file with details later only if needed)
  • Remove CONTRIBUTORS file
• Some more CSS cleanup:
  • replace images with data URIs in CSS (then remove img directory)
  • remove references to gantt & gantt2 classes (update demo accordingly)
  • switch to border-box box model (Box-sizing might affect Gantt appearance #102)
• replace jquery.cookie support with JS Cookie support
• adopt AMD or ESM pattern
• minify js (note in README that pull requests should not contain changes to minified file(s))
• Add appropriate dotfiles:
  • add .eslintrc file
  • add .editorconfig file
  • add .gitattributes file
• Add package.json for npm (remember to add jquery-plugin and ecosystem:jquery keywords - ref)
• add tag & release notes (Create a new release/tag #161)
• Register on npm registry
• Update reference on cdnjs ([Request] Add jQuery.Gantt cdnjs/cdnjs#6099, [New] Manually add jQuery.Gantt@1.1.0 w/ git auto-update cdnjs/cdnjs#7005)

[taitems]

How do you feel about using using a specific CI tool, or alternatively github actions to achieve some of these tasks?

At ACG we're using buildkite for CI/CD, lerna to publish packages etc. I'm very green on github actions.

[usmonster]

I think most of the tasks in this particular issue are one-offs that can only (or make more sense to) be done manually, but I'd definitely be up to use GitHub Actions to tag & publish new versions going forward!