I have a big yard, but I don't think it'd be enough to house and feed a pony.

I may have to content myself with a photo. :)

A middle ground that has worked for me is that between my own packages I just use the first digit of the major version. If the bulk of the API is unlikely to break in the 1.x regime, putting a bound of text < 2 would permit large breaking changes to be signaled in the future, while still removing most of the headaches of day to day version bumps forced on you by the pvp.

On Dec 9, 2013, at 3:28 PM, "Bryan O'Sullivan" <bos@serpentine.com> wrote:

On Mon, Dec 9, 2013 at 11:29 AM, Edward A Kmett <ekmett@gmail.com> wrote:

At last check blaze-builder hadn't updated its text dependency though stuff built on top of it has. I opened an issue with the repo about it as this is currently blocking the updated release of trifecta.

There will be a 1.1 release of text in a matter of weeks, which leaves the public API unchanged, but exposes all the hitherto hidden internal modules.

Everyone who removes their upper bounds on the version of text gets a pony. Everyone who widens their upper bounds to allow 1.1 gets a photo of a pony. Everyone who widens, but only to 1.0, gets some postprocessed pony food.