Gearing up (again) for the next release: 2014.2.0.0
Herbert Valerio Riedel
hvr at gnu.org
Wed Apr 9 18:00:40 UTC 2014
On 2014-04-09 at 19:02:56 +0200, Michael Snoyman wrote:
> On Wed, Apr 9, 2014 at 7:55 PM, Herbert Valerio Riedel <hvr at gnu.org> wrote:
>> On 2014-04-09 at 17:51:11 +0200, Greg Weber wrote:
>>> I don't think we are going to include a package in the platform that
>>> was just changed today to work on Windows. Have you looked at
>>> building http-streams on top of http-client as pipes-http has done?
>>> That seems like the ideal solution if it is possible: then we can
>>> just include http-client in the platform.
>> Is the http-client API really mature enough (for being included in the
>> HP) after having gone through 3 major version bumps in its rather short
>> lifespan? I wouldn't be surprised if the http-client API required yet
>> another major version bump in order to accomodate http-client.
> Do you mean to accommodate http-streams?
yes
> If so, I doubt it: the streaming aspects of the library have been
> completely unchanged. For the record, the changes in the API were:
>
> 0.3: transition from failure to exceptions package
> 0.2: replace the original, placeholder API with the intended end-user API
> 0.1: initial pre-release
>
> So it's not 3 major version bumps, it's two major version bumps, one of
> which being the first "real" release and the second being due to
> consolidated upstream packages. So the API isn't as unstable as it
> seems.
Sorry, my mistake, I was counting "major versions" but then actually
went on and wrote "version bumps"
> That said, I'm not actually advocating for including http-client in
> this revision: I think it's pretty late in the game for a new package
> in the platform, and I *do* think a few more months of testing to see
> if everyone's happy with the API makes a lot of sense.
More information about the Libraries
mailing list