backports: Make it clear that it will only be extracted to a separate gem if theres enough interest

This commit is contained in:
Fabio Rehm 2014-03-12 20:26:28 -03:00
parent bb8514b518
commit 320a698f49

View file

@ -4,7 +4,9 @@
[![Build Status](https://travis-ci.org/fgrehm/vagrant-backports.png?branch=master)](https://travis-ci.org/fgrehm/vagrant-backports) [![Gem Version](https://badge.fury.io/rb/vagrant-backports.png)](http://badge.fury.io/rb/vagrant-backports) [![Code Climate](https://codeclimate.com/github/fgrehm/vagrant-backports.png)](https://codeclimate.com/github/fgrehm/vagrant-backports) [![Coverage Status](https://coveralls.io/repos/fgrehm/vagrant-backports/badge.png?branch=master)](https://coveralls.io/r/fgrehm/vagrant-backports) [![Gittip](http://img.shields.io/gittip/fgrehm.svg)](https://www.gittip.com/fgrehm/)
-->
A "soon to be extracted" gem that helps Vagrant plugin developers to stay sane
when keeping up with Vagrant improvements and backwards incompatible changes.
A _"hypothetical"_ gem that helps Vagrant plugin developers to stay sane when
keeping up with Vagrant improvements by backporting parts of its recent versions
functionality.
More information coming out soon...
More information will be provided if there is enough interest on having this
extracted as a separate gem.