-
How about adding versioning of the blocks? Could be complicated with many_many and nested blocks though.
-
Reports need to support different versions i.e. updating a report should not just overwrite data.
kynan updated
10 years ago
-
improve controllers so we can have better API management (i.e. versioning). For example, have "/v1/" in the path so we can have multiple concurrent versions.
Also, try to improve APIs (format, syntax…
-
Is there any chance of adding versioning to Torch anytime soon?
e.g. [linux](https://github.com/torvalds/linux/releases), [rails](https://github.com/rails/rails/releases), [docker](https://github.co…
-
Could you please tag a release?
-
Well, I see two versioning options:
- Copy files into an "archive" folder instead of deleting them forever.
- Disassemble files into blocks, and then store disassembled version in system_path along wi…
-
At v 1.0.0 of the this server (from npm) the schema version offered in the endpoint list at `http://.../signalk/` is 1.0.0 but the version property returned in the full message from `http://.../signal…
-
Hey Chris - Just an FYI that the latest tableau-react package doesnt work. I fixed this with the following command: npm install --save react@15.4.2 react-dom@15.4.2
-
The way we version needs better documented, but roughly it is:
- Major: triggered only my massive breaking change, like jump from c++98 -> c++11 or major rewrite in public API (styling or core interfa…
-
Just a few comments on semantic versioning:
v1.3.0 switched its dependencies to the ASP.NET Core non-LTS channel. This is a major change, which I think should have been versioned as v2.0.0.
Let …