Release Trains

[gr2m]

• [x] setup unified release workflows for all Hoodie modules
  • [ ] [deferred https://github.com/hoodiehq/hoodie.js/issues/337] hoodie.js
  • [x] hoodie-cli
  • [ ] [deferred] https://github.com/hoodiehq/hoodie-cli/issues/121 my-first-hoodie
  • [x] hoodie-plugin-appconfig
  • [x] hoodie-plugin-email
  • [x] hoodie-plugin-users
  • [x] hoodie-plugins-manager
  • [x] hoodie-plugins-api
  • [x] hoodie-server
  • [x] hoodie-pocket-UIKit
  • [x] node-multicouch
  • [x] couchdb-db-notify
  • [x] pocket
  • [ ] [deferred https://github.com/hoodiehq/hoodie.admin.js/issues/4] hoodie-admin.js
  • [x] local-tld-lib
  • [x] node-ports
• [x] for any Hoodie Module release, update my-first-hoodie dependencies

[gr2m]

see also discussion at https://github.com/hoodiehq/discussion/issues/46

[boennemann]

for any Hoodie Module release, update my-first-hoodie dependencies

not necessary, because semver

[boennemann]

This is done as per https://github.com/hoodiehq/discussion/issues/46#issuecomment-49161956 The setup is well documented, so once the blocking issues are solved this can come back on the agenda without blocking things on the roadmap.

[gr2m]

@boennemann Maybe I misunderstand something, but I think that is not true.

Use case:

1. I update hoodie.js from 0.9.7 to 0.9.8
2. I run hoodie new mynewapp
3. Result: I still get 0.9.7

The same is true for

• hoodie-admin-dashboard
• hoodie-admin-dashboard-uikit
• hoodie-plugins-manager
• hoodie-plugins-manager
• hoodie-plugins-api

The problem is that hoodie new myappname only requires the latest hoodie-server, while the ones listed below are dependencies of hoodie-server (hoodie-plugins-api is a dependency of hoodie-plugins-manager).

I'm not sure if sub-dependencies are covered by semver as well, just want to make sure.

Besides that, what is the workflow if I don't publish a patch version, but a minor / major update?

[boennemann]

If you update hoodie.js from 0.9.7 to 0.9.8 you will get 0.9.8 the next time you run hoodie new (at least with a clean cache, but that's not even needed with https://github.com/hoodiehq/hoodie-cli/issues/121 anymore. Integration tests always run with empty cache).

All my-first-hoodie dependencies are >1.0 so all non breaking changes will be delivered to new apps immediately (which is kind of what we want).

The only "problem" then would be hoodie-server dependencies <1.0 (hoodie.js, hoodie-plugins-manager), so here you need to update manually for new feature releases.

[gr2m]

Okay, so everytime I publish a new hoodie.js version, I need to manually update hoodie-server and publish it as well, right? Just want to make sure I understand that correctly, thanks!