浏览代码

Some work on changelog already

Kevin van Zonneveld 9 年之前
父节点
当前提交
b8b563af1f
共有 1 个文件被更改,包括 27 次插入11 次删除
  1. 27 11
      CHANGELOG.md

+ 27 - 11
CHANGELOG.md

@@ -1,29 +1,45 @@
-Our combined changelog and todo. Items can be tagged by owner and optionally, if discussion
-happened / is needed, a GitHub issue.
+Our combined changelog and todo. 
 
-Please add your entries in the form of:
+Items can be optionally be tagged tagged by GitHub owner issue if discussion
+happened / is needed.
 
- - `- [ ] (<plugin name>|website|core|meta): <Present tense verb> <subject> \(<list of associated owners/gh-issues>\)`.
+Please add your entries in this format:
+
+ - `- [ ] (<plugin name>|website|core|meta|test): <Present tense verb> <subject> \(<list of associated owners/gh-issues>\)`.
+
+Following [SemVer item 4](http://semver.org/#spec-item-4), we're `<1.0.0` and allowing ourselves to make breaking changes in minor patch levels.
+
+In the current stage we aim to release a new version on the first Tuesday of every new month.
 
 ## TODO
 
-Work not started yet
+Ideas that will be planned into a release at one point
 
-- [ ] modal: Add basic Modal plugin that can be used as a target
-- [ ] google: Add basic Google Drive plugin example
 - [ ] instagram: Add basic Instagram plugin example (#21)
 - [ ] presets: Add basic preset that mimics Transloadit's jQuery plugin (#28)
 - [ ] tus: Add support tus 1.0 uploading capabilities (#3)
 - [ ] core: Apply plugins when DOM elements aren't static (#25)
-- [ ] core: Create a progressbar/spinner/etc plugin (#18)
-- [ ] multipart: Write an acceptance test for the Multipart example via Saucelabs (#2, #23, @hedgerh)
+- [ ] test: Write an acceptance test for the Multipart example via Saucelabs (#2, #23, @hedgerh)
 - [ ] test: setup an HTML page with all sorts of crazy styles, resets & bootstrap to see what brakes Uppy
 
-## 0.0.2 (Unreleased, work in progress)
+## 0.0.4 (April 05, 2016)
+
 
+## 0.0.3 (March 01, 2016)
+
+- [ ] test: Fix and enable phantom acceptance test. Write one actual test. Enable it in `npm run test` so it's ran on Travis automatically (@hedgerh)
+- [ ] test: Fix and enable commented out `run one plugin success` unit test  (@arturi)
+- [ ] core: Decide on single-noun terminology (npm, umd, dist, package, cdn, module, bundle), and call it that through-out.
+- [ ] modal: Add basic Modal plugin that can be used as a target (#53, #50)
+- [ ] google: Add basic Google Drive plugin example
+- [ ] core: clean up package.json. We've accumulated duplication and weirdness by hacking just for our current problem without keeping a wider view of what was already there 
+- [ ] core: Create a progressbar/spinner/etc plugin (#18)
+- [ ] meta: Decide on tagline(s)
 - [ ] meta: Create an Uppy logo (@vvolfy)
-- [ ] core: Decide on good names for `cdn` vs `npm` builds and rename all-the-things
 - [ ] server: Add a deploy target for uppy-server so we can use it in demos (#39, @kvz)
+
+## 0.0.2 (February 11, 2016)
+
 - [x] server: Create a (barely) working uppy-server (#39, @hedgerh)
 - [x] core: implement a non-blocking `install` method (for Progressbar, for example)  (@arturi, @kvz)
 - [x] dragdrop: Use templates, autoProceed setting, show progress (#50, #18, @arturi)