On Tue, Jun 24, 2008 at 10:27:07PM -0700, Junio C Hamano wrote:
> Ok, let's map this out seriously.
>
> * 1.6.0 will install the server-side programs in $(bindir) so that
> people coming over ssh will find them on the $PATH
>
> * In 1.6.0 (and 1.5.6.1), we will change "git daemon" to accept both
> "git-program" and "git program" forms. When the spaced form is used, it
> will behave as if the dashed form is requested. This is a prerequisite
> for client side change to start asking for "git program".
>
> * In the near future, there will no client-side change. "git-program"
> will be asked for.
>
> * 6 months after 1.6.0 ships, hopefully all the deployed server side will
> be running that version or newer. Client side will start asking for
> "git program" by default, but we can still override with --upload-pack
> and friends.
>
> * 12 months after client side changes, everybody will be running that
> version or newer. We stop installing the server side programs in
> $(bindir) but people coming over ssh will be asking for "git program"
> and "git" will be on the $PATH so there is no issue.
>
> The above 6 and 12 are yanked out of thin air and I am of course open to
> tweaking them, but I think the above order of events would be workable.
Is that really 6 and 12 months, or "6/12 months or at the next major
release boundary, whichever is later". i.e., would make some of these
changes as part of a minor dot release, such as having the client side
change what it starts asking for in 1.6.3 or some such? Presumably
the earliest that change would happen is 1.7, and the earliest to make
the server side installation changes is 1.8, right? Or did you really
mean a hard 6/12 months, regardless of release cycle issues?
- Ted
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
