Maintaining Releases

[sebastiaanluca]

Maybe a thought to create fixed releases? Using dev-master in composer.json is highly discouraged, and our project guidelines don't actually allow it :3

[chriscannon]

I also think this is a great idea.

[slampenny]

I..uh..don't actually know how to do that. I'm googling now.

[sebastiaanluca]

@slampenny Look into git flow and Sourcetree if you want to do it right :) Then just create a release and the tag to GitHub. Packagist should take care of it automatically if I remember correctly.

[chriscannon]

git tag v1.0

[slampenny]

I looked at laravel-debugbar... Barry uses different branches for version control, which is what I did here. I'll look at the other suggestions you guys made asap.

[sboo]

The easiest way to do it and for packagist to pick up versions is to tag the commits with the right version, just like @chriscannon suggests. And yes, git flow is the way to go to handle releases.

Check this out for some reading:
http://nvie.com/posts/a-successful-git-branching-model/