rsync release planning

jw schultz jw at
Wed Jul 9 09:06:39 EST 2003

On Tue, Jul 08, 2003 at 09:51:16AM -0700, Wayne Davison wrote:
> On Sat, Jul 05, 2003 at 10:30:13PM -0700, jw schultz wrote:
> > I'll tell you what i'm thinking road map wise and you can
> > agree or disagree, and tell me i'm crazy.
> > 
> > I'd like 2.5.7 fairly soon containing:
> > 
> > 	cygwinhang patch -- if testing shows it to be safe
> > 		and effective.
> I assume you mean adding this patch to what's currently in CVS?  Or do
> you mean you'd like to create a branch of 2.5.6 with just this fix?  I'm
> assuming you mean the former.

Yes, the former.  There are a lot of bug fixes and
improvements that have been in for a while.

> > Then i'm inclined to a 2.6.0 with these things that change
> > the user interface:
> > 
> > 	my keyword based report (verbosity) option.
> > 		This doesn't break anything and i have no
> > 		qualms with it going into 2.5.8
> > 
> > 	ssh as default -rsh transport.
> > 		This would affect users expecting rsh or remsh
> > 
> > This new pattern matching would fall into the changed UI
> > that might merit a minor version number increment.
> Since there are existing exclude changes that have a user-visible effect
> already in CVS, I'd like to make sure that these changes get grouped
> together with the "**" vs "*" change that the wildmatch code implements.
> That could mean either undoing some user-visible changes in CVS (see
> below) or going ahead and adding the wildmatch stuff to what's there.

When i spoke of changed UI i meant changes that would
require current users to adapt to get the same behaviour.  I
exclude changes that bring behaviour in-line with
documentation; If you depend on a bug you had better keep an
eye on NEWS.  That is why i don't list the keyword based
report in that category.  I don't recall of any UI changes
in CVS that break anything existing.  If there are someone
hasn't been keeping NEWS up-to-date.

> Here are the current user-visible changes to the exclude code:
>   - **/foo now matches /foo.
>   - A non-anchored wildcard name with an interior slash properly floats
>     at the end of the path.  I.e. CVS/R* matches the R* files in all CVS
>     dirs, whereas it used to be treated as /CVS/R*.
>   - foo**bar is now matched against the whole path, not just the
>     filename.
> The remaining change:
>   - a "**" in the string no longer makes "*" match a slash.
> > I'm also wondering about the craigb-perf patch.  Anyone know
> > how widely it has been tested?
> I've been wondering about it as well.  I've looked over the whole patch
> and the comments and it certainly looks reasonable, but I am slightly
> concerned about potential deadlock issues, though.  I haven't tested it
> yet, nor have I tried to think through the I/O issues in depth yet.  The

My grasp of what is going on in the client-server I/O just
isn't firm enough in the light of apparent deadlocks in
history for me to be comfortable with any change this
central but otherwise it does indeed look a reasonable and
good idea.  That is why i ask about testing.  My inclination
is to commit it early in a release cycle with a back-out
patch held ready.

> change to reduce the calls to gettimeofday() looks easy to add, though,
> and should really be separated out of the patch.  I've just checked in
> some changes to tweak this.

	J.W. Schultz            Pegasystems Technologies
	email address:		jw at

		Remember Cernan and Schmitt

More information about the rsync mailing list