On Feb 10, 2008, at 1:42 PM, Johannes Schindelin wrote:
On Sun, 10 Feb 2008, Steffen Prohaska wrote:
Should we follow Junio's maint branch and release maintenance
versions
of msysgit?
One way would be to have "maint" branches in mingw and 4msysgit. You
would merge Junio's maint to your maint branch, which I would then
merge
to 4msysgit's maint. Afterwards I'd build and release the installer.
I am the other Johannes, but I have some thoughts on this, too ;-)
IMHO it is better to follow "master" for now, since there are quite
a few
features coming along that we _need_.
Thats true, but maybe we should just wait ...
For example, your crlf stuff, and the solution for the "git gc" in big
repositories, as well as the patch to support case-insensitive
filesystems
better (hopefully soon!).
These will not be in "maint" for a long time.
... Junio mentioned a few times on the git list that he plans to
have a short 1.5.5 cycle. So hopefully a "long time" will not be
that long.
The question for me is if we want to improve 1.5.4 in the same
very controlled way that official git is improved. Certainly we
won't have the new features; but we would also avoid having
uncontrolled regressions. This is how maintenance releases
work, no?
We do not advertise msysgit for production, but I know that
people are already using git for getting real work done on
Windows. So maybe we should make the bug fixes from Junio's
maint available to them.
Steffen
