|
From: Donovan B. <ab...@mi...> - 2006-08-27 11:31:13
|
[adding Cc librsync-devel] Martin Pool wrote: > On 24 Aug 2006, roland <de...@we...> wrote: >> hello librsync authors! >> >> I already tried to contact librsync team some time ago, but maybe this was >> adressed to the wrong people. >> >> the last official librsync release is some time ago: >> >> 0.9.7 [Notes] (2004-10-10 03:20) librsync-0.9.7.tar.gz >> 0.9.6 [Notes] (2003-08-07 07:00) librsync-0.9.6.tar.gz >> 0.9.5 [Notes] (2001-09-13 00:00) librsync-0.9.5.tar.gz >> >> what about releasing a 0.9.8 ? >> >> I think the current cvs contains a very important patch, so that >> librsync/rdiff will work without problems with large files (see below). > > Donovan (abo) was last maintainer for it. If he's not reachable then I > could make a release. I am reachable, just very short of time and hence slow to respond... I still do minor things when prompted like list admin, but I probably don't have time to do a release right now... so if someone else could do it that would be great. Have a look at the end of README.CVS for a rough checklist of things to do for a release. On this particular issue, I've not been keeping up much, but I vaugely recall that there was some ambiguity if the problem was fixed after the patch went in (see bug #1110812). However, the patch #1439412 definitely fixed one problem and is worth a release for. Boy, SF is pretty flakey ATM... it is giving me intermittent 500's. I'll have a bit of a poke around at the source and see if there are any quick things I can do to prepare for a release... -- Donovan Baarda <ab...@mi...> |