libsoup branched for 2.28

2009-11-21 Thread Dan Winship
I branched libsoup for 2.28. Also, I support the recommendation to stop
requiring branch announcements.

-- Dan

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: libsoup branched for 2.26

2009-04-15 Thread Emilio Pozuelo Monfort
Hi Dan,

Dan Winship wrote:
 Plans for 2.28 are not nailed down, but are mostly being driven by
 WebKit at this point (with bug reports, feature requests, and patches
 coming from both the Epiphany and Midori developers). Features currently
 in progress include better Content-Type sniffing (kov), caching (xan),
 and Content-Encoding (ie, gzip) support (Company).

Are there any plans for IDN support for this cycle (bug #548287)?

Cheers,
Emilio



signature.asc
Description: OpenPGP digital signature
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: libsoup branched for 2.26

2009-04-15 Thread Dan Winship
Emilio Pozuelo Monfort wrote:
 Hi Dan,
 
 Dan Winship wrote:
 Plans for 2.28 are not nailed down, but are mostly being driven by
 WebKit at this point (with bug reports, feature requests, and patches
 coming from both the Epiphany and Midori developers). Features currently
 in progress include better Content-Type sniffing (kov), caching (xan),
 and Content-Encoding (ie, gzip) support (Company).
 
 Are there any plans for IDN support for this cycle (bug #548287)?

Yes, hopefully all the GResolver stuff (IDN, better IPv6 support, using
libsoup without gthread) should get merged in. (I don't remember if the
next glib release is due before 2.28 or not, but if it's not, we can
still use a local copy of GResolver, libegg-style, for 2.28.)

-- Dan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


libsoup branched for 2.26

2009-04-14 Thread Dan Winship
I branched libsoup for 2.26 and updated jhbuild.

Plans for 2.28 are not nailed down, but are mostly being driven by
WebKit at this point (with bug reports, feature requests, and patches
coming from both the Epiphany and Midori developers). Features currently
in progress include better Content-Type sniffing (kov), caching (xan),
and Content-Encoding (ie, gzip) support (Company).

If you read this far, and you are not subscribed to libsoup-list, then
maybe you should be? http://mail.gnome.org/mailman/listinfo/libsoup-list

-- Dan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


libsoup branched for 2.24

2008-09-29 Thread Dan Winship
I branched libsoup for 2.24. (Actually, I did this last week and just
never sent mail.) Someone already updated jhbuild. Not cc'ing docs and
i18n since libsoup has neither.

Plans for 2.26: unclear. The burst of activity around
libsoup+webkit+epiphany last spring that then quickly died out seems to
have possibly suddenly picked up again, so maybe more of that will end
up happening this time.

-- Dan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


libsoup branched for 2.20

2007-09-14 Thread Dan Winship
I branched libsoup for 2.20 and updated jhbuild.

Note that there has not been a libsoup release since 2.18 went out, due 
to a blocker in HEAD, and so the 2.20 branch is branched from the same 
point as the 2.18 branch, even though there are additional fixes in HEAD 
(which will eventually see the light of day in GNOME 2.20.1).

-- Dan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


libsoup branched for 2.18

2007-03-12 Thread Dan Winship
I've branched libsoup for gnome-2-18. You know the drill. (Not cc:ing
docs or i18n lists because libsoup has neither.)

Plans for 2.20? Well, maybe I'll finally do the long-awaited ABI break I
originally claimed I was going to do for 2.14.[1] Or maybe not.

People who are using libsoup (or who *want* to be using libsoup but are
somehow thwarted) who have ideas for what things should be fixed should
file bugs or send mail to [EMAIL PROTECTED]

-- Dan

[1]
http://mail.gnome.org/archives/release-team/2005-November/msg00047.html


___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


libsoup branched

2005-11-10 Thread Dan Winship
I branched libsoup for gnome-2-12 and updated jhbuild. (libsoup has 
neither translatable strings nor user documentation, so I'm not cc:ing 
those lists.)


Plans for 2.14 include:
* Finally using the GNOME proxy settings from gconf (including
  ignore_hosts) by default (*)

* A patch from the OpenSync hackers to allow a SoupSession or
  SoupServer to use a non-default GMainContext (allowing
  multithreaded async use). This is used by their SyncML server
  backend.

* Support for HTTP Content-Encoding (eg, gzip)

* Fixes to SoupUri to better support complex URIs (eg, http URIs
  with other http URIs encoded as query parameters) (*)

* Miscellaneous other improvements (*) and possibly other new useful
  APIs

The plan is to do all of the API-breaking changes (the *ed things) on 
libsoup-pre214-branch and then land them all on HEAD simultaneously to 
minimize headaches. (And then hopefully to not ever break API again in 
the future, at least for the client-side API.)


-- Dan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list