-
-
Packages will use [Semantic Versioning](https://semver.org/)
i.e :
MAJOR.MINOR.PATCH (-Prerelease-Label).
With Binary compatibility being a major issue wth delphi dcu's, this will be very muc…
-
I see that this repository now uses versioning/tags. I think that it would be appropriate to use [Semantic Versioning](https://semver.org/).
As far as I know this is quite a standard for bigger proj…
bzgec updated
2 years ago
-
Currently we're just tracking the OpenEXR major/minor version and assuming we'll bump patch as necessary. This is going to be pretty terrible because it means we can't iterate on the safe API - we'd h…
-
In requiremnet.txt can you mention which version should be used for each dependency. I am facing issues in producing the output from this repo.
Thanks
-
This one is more of a brainstorm. Here's the problem:
## The Problem
1. A user has my flashcard app (for example) installed on an iPad and iPhone.
2. I release an update, allowing users to add …
-
Hi all,
Are there any plans for built-in API-versioning? I've been looking at https://github.com/dingo/api, and it looks great, though a little overkill for what I need. One thing it does have it sma…
snipe updated
8 years ago
-
Yo, so you should put some proper semantic version numbers on this thing so that people can keep their bindings up to date.
-
It's time to start thinking about real [semantic versioning](http://semver.org) and real release cycles.
I still want to release frequently to fix occassional bugs - right now it's all uncontrolled t…
-
See https://github.com/theodi/shared/issues/484