refs #56 - Add versioning

[ogarbe]

To be able to use Incubator in a production environment with composer auto-update without fearing something breaks.

[ogarbe]

Thanks @sjinks ! We need one last thing, it's to create the tag 'v1.2.4' for this version.

[ghost]

@phalcon or @niden could you please do that?

[ogarbe]

it's here : https://github.com/phalcon/incubator/releases and create new release v1.2.4

[niden]

Done

The contents of this message may contain confidential or privileged
information and is intended solely for the recipient(s). Use or
distribution to and by any other party is not authorized. If you are not
the intended recipient, copying, distribution or use of the contents of
this information is prohibited.

On Wed, Nov 27, 2013 at 4:41 PM, Olivier Garbé notifications@github.comwrote:

it's here : https://github.com/phalcon/incubator/releases and create new
release v1.2.4

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/64#issuecomment-29422517
.

[ogarbe]

Thank you !

Concerning this package, i recommend you to follow Packagist recommandation concerning update schedule, so that the package https://packagist.org/packages/phalcon/incubator will be updated automatically.

Regards

Olivier

https://packagist.org/about

New packages will be crawled immediately after submission if you have JS enabled.

Existing packages without auto-updating (GitHub hook) will be crawled once a day for updates. When the GitHub hook is enabled packages are crawled whenever you push, or at least once a week in case the crawl failed. You can also trigger a manual update on your package page if you are logged-in as a maintainer.

It is highly recommended to set up the GitHub service hook for all your packages. This reduces the load on our side, and ensures your package is updated almost instantly. To do so you can go to your GitHub repository, click the "Admin" button, then "Service Hooks". Pick "Packagist" in the list, and add the API key you will find on your profile, plus your Packagist username if it is not the same as on GitHub. Check the "Active" box and submit the form.

[ogarbe]

Sorry again, after most reading, it seems puting the version in the composer.json is a bad idea...

[ogarbe]

#66 to change this.

Sorry for inconvenience...