Forgive me for asking a question whose answer is presumably obvious to
the regulars, but as an outsider I am left wondering if something went
"wrong" in the SCM process to cause such difficulty in reconstructing a
previous (albeit older) release?
Are the dependencies not fully documented? Has the build environment
changed? Or is this simply a matter of resource availability for
testing?
Just curious ...
Thanks,
Mark
On Wed, 2007-04-04 at 23:33 -0700, Justin Erenkrantz wrote:
> On 4/4/07, Erik Huelsmann <ehuels@gmail.com> wrote:
> > Ok, so I've done all the backporting for 1.0 .. 1.3 for the issue 2751
> > fix (rare FS corruption) because there are even occasional reports on
> > users@ which relate to 1.0. I want all distros to be able to do a new
> > release if and when they still do maintenance for anything which
> > includes a post 1.0 release of Subversion.
>
> I think us doing releases for each one of those series is massive
> overkill. We can post a patch for each series and if a distributor is
> still using them, then can repackage accordingly - but expecting us to
> go through, re-create each release environment, and vote and test on
> each release is, IMHO, insane. I think the only one we really need to
> cut a release for is the current version (i.e. 1.4.x) and let
> downstream repackagers figure out if they want to cut their own
> release from older stuff. -- justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
--
----------------------
Mark S. Reibert, Ph.D.
svn@reibert.com
----------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 5 09:20:07 2007