On Tue, Oct 14, 2008 at 02:23:48PM +0200, Markus Milleder wrote:
> Adrian Bunk schrieb am 13.10.2008 17:41:15:
>...
> > And upgrading from 2.3.1 to let's say 3.0.0 might be a bad choice if
> > the new version contains regressions.
>
> That's why I said "before branching", this gives a time window to detect
> such regressions. While the cutoff date for moving to a new revision
> of MPFR may be somewhat earlier, my idea was to demand a rather current
> revision.
>
> Changing to 3.0.0 - which implies much larger changes than 2.3.3 - is
> IMHO stage 1 material, maybe stage 2 if the release notes make it
> exceedingly clear that the major version change is only because
> of major new features, with no changes to existing ones.
You seem to wrongly assume gcc was bound to one specific MPFR version?
If you force someone to upgrade from 2.3.1 to >= 2.3.2 he will usually
install the then-latest version, and that might be 3.0.0 .
> Markus Milleder
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
