W3C home > Mailing lists > Public > www-lib@w3.org > April to June 2000

Re: AMAYA branch of libwww sources in CVS

From: <jose@w3.org>
Date: Thu, 18 May 2000 05:02:05 -0400 (EDT)
To: Andy Levine <andyl@epicrealm.com>
Cc: www-lib@w3.org
Message-ID: <20000518110140.D1272@kiribati.inrialpes.fr>
Helly Andy,

On Wed, May 17, 2000 at 10:16:46AM -0500, Andy Levine wrote:
> I noticed that some source files in the CVS tree of libwww have been
> branched under the label "AMAYA" within the last couple of months. The
> changes to these files seem significant, yet they have NOT been rolled back
> into the main trunk of sources. For example, there are changes to the file
> HTTP.c that fix a few crashes we have been having that appear in revision
> that don't roll in to the main line of development at all.

I'm respmsible for that branch. Usually, I try to rollback my changes as
soon as possible to the main tree. I have been quite busy with Amaya and
haven't been able to do so lately. 

Sometimes, the changes helps fixes a particular problem with Amaya. Sometimes
this is done under the pressure of an inminent release. Before rolling out
the changes, I have to review it again to see if it's general enough or if I
can improve it.

> A few questions:
> 1) What is the best way to proceed with these files ? Get the ENTIRE AMAYA
> version ? Just download individual files ?

Just download the individual files. Don't take the HTZip.c and HTTrace ones,
as they solve compilation problems under the Amaya environment. 

> 2) Are these changes going to EVER be rolled back into the main branch ? If
> so, when,

I'm preparing a new tar file release of libwww, so they'll get out in around
three weeks.

> 3) Is there ANY ongoing support anymore of libwww ? Hasn't been a release in
> QUITE a while and things have been REAL quiet.

It's a question of manpower :) We need more volunteers to help us. 

I'm a libwww user as any other one. My only special privileges are that I'm
on W3C staff, so I can modify the HTML pages, publish things on our web site,
and open write access to our CVS server. I also contribute my own patches.
Unfortunately, I can't have a more active presence because I have other 
priorities. We don't have anyone else to do it, though.

libwww should be maintained by its user group. It's alive in the sense that
folks continue contributing patches and the CVS version evolves. I'd be happy
to have other people help improve the integration of patches, so that I'm
not a bottleneck.

Sorry for the inconveniences.

Received on Thursday, 18 May 2000 05:15:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:52 UTC