bringing releases up to date about gulp-twig

@olets I prefer semver too. Sadly twigjs doesn't follow semver and releases had often breaking changes in the past. However, small backwards compatible tweaks, cleanups like the one I've mention above can always be applied. I don't think it's against semver.

[olets]

@Dotmagic makes sense. Hoping to get Twig.js on a more semver release schedule, we'll see how that goes

[bezoerb]

@olets thanks for bringing that up again ;)
Why shouldn't we just release the v1.0.0 now?

[bezoerb]

Released. Just need you to merge #43

I would like to see updated twigjs, v1.10.5 was already released when we upgrade to v1.10.4. And readme.md cleanup (remove atpl reference) before we're going to bump the version again.

[bezoerb]

v1.10.5 is already catched by "^1.10.4"

[bezoerb]

I've changed it anyway

[olets]

Fyi best to tag the upstream repo only after merge - 0575656 has been the default npm install gulp-twig point since the tag was added.

Yep no reason to bump the Twig.js dependency until it hits v2. Just introduces noise

@bezoerb Ha you are quick! Leaving some feedback in the PR

@Dotmagic what versioning scheme do you picture for this project? I'd like to use semver: breakingchanges.newfeatures.fixes. That will lead to more frequent releases, but that's good: updates will ship to npm much more quickly. No matter what, it could be good to formalize