Comments (5)
I find the git flow model useful especially working in larger teams where more contributors have commit privs.
In short it suggests the use of the master branch as production ready with tagged release snapshots.
A develop branch with current development progress which gets merged back into master for release.
Feature branches for more complex feature enhancements which branches from develop and gets rebased on occasion to stay in sync and eliminate conflicts until it is completed and merged back into develop.
As for versioning scheme, I tend to auto-default to, the semantic versioning scheme which needs no introduction and is widely adopted and understood. Does any reservations against its use exist perhaps?
from json-schema-test-suite.
Nope, that's all reasonable sounding to me, it's how I generally do it too :). Sounds good to me.
from json-schema-test-suite.
Think we should tag a release to start?
from json-schema-test-suite.
Did you tag?
Excuse the late reply I somehow thought that I did answer this but it was a looong and winding tale on how I usually only release when ready and then tag when releasing. Anyway you're blessed to have missed it.
=)
from json-schema-test-suite.
Heh :).
Should be tagged, yeah. https://github.com/json-schema/JSON-Schema-Test-Suite/tags
from json-schema-test-suite.
Related Issues (20)
- Tests for bundling HOT 28
- draft2019-09 output-schema.json is wrong HOT 3
- Revamped output testing HOT 8
- test: unevaluatedItems with nested items > with invalid additional item HOT 3
- Incorrect Revert "by default, "format" only annotates, not validates"? HOT 5
- Negative schema tests HOT 4
- File URIs with pointer fragments HOT 6
- New release? HOT 4
- Perhaps add test for `"type": []` HOT 3
- Suite contains invalid, positive tests for idn-hostname HOT 2
- Add tests for single label IDN hostnames
- Missing test for `unevaluatedProperties` and `$dynamicRef` HOT 1
- Add an `id` property to all test cases HOT 4
- Add a `specification` property to test cases + tests HOT 12
- Should identifier declarations be respected in non-schema locations? HOT 29
- Clarify how test runners should handle `format`. HOT 1
- Unknown `format` handling HOT 2
- Test for jumping over a resource HOT 16
- Syntax highlight schemas + instances in the terminal HOT 1
- Description and test case contradiction: `unevaluatedProperties` HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from json-schema-test-suite.