versioning in vendor distributions
TK Soh
teekaysoh at gmail.com
Wed Apr 2 16:07:37 CDT 2008
On Wed, Apr 2, 2008 at 9:04 PM, Matt Mackall <mpm at selenic.com> wrote:
>
> On Wed, 2008-04-02 at 13:39 -0700, Danek Duvall wrote:
> > Matt,
> >
> > I'm about to integrate 1.0 into Solaris, but Rich tells me that we need
> > issue 1052 solved. That's fine, but I didn't like his change to
> > __version__.py, which turned "1.0" into "1.0-osol1".
> >
> > Another idea would be to do to mercurial as we do to perl: split out a list
> > of locally applied patches when calling "perl -V". I just wanted to make
> > sure that modifying mercurial in this way (changing the output of "hg
> > version" to have a list of patches applied, below the copyright statement)
> > is something you'd be okay with.
>
> Seems ok. We'll probably ship a 1.0.1 pretty soon.
How soon?
Just wondering if we should wait before releasing TortoiseHg 0.4.
More information about the Mercurial
mailing list