Policy on spkgs updates
38 views
Skip to first unread message
Paul-Olivier Dehaye
Oct 16, 2012, 2:17:33 AM10/16/12
to sage-...@googlegroups.com
Is it always encouraged to upgrade spkgs to more current stable
upstream version?
Right now scipy is at 0.9, applied with patches to fix a bug that is
now corrected in version 0.11 (normally, I have not tested yet). The
patch does not seem to work under Mac OS X 10.8, so I was wondering if
instead of fixing the patch I should really upgrade the spkg to the
later version for everyone.
Paul
upstream version?
Right now scipy is at 0.9, applied with patches to fix a bug that is
now corrected in version 0.11 (normally, I have not tested yet). The
patch does not seem to work under Mac OS X 10.8, so I was wondering if
instead of fixing the patch I should really upgrade the spkg to the
later version for everyone.
Paul
Michael Welsh
Oct 16, 2012, 2:19:01 AM10/16/12
to sage-...@googlegroups.com
Jeroen Demeyer
Oct 16, 2012, 2:49:48 AM10/16/12
to sage-...@googlegroups.com
On 2012-10-16 08:17, Paul-Olivier Dehaye wrote:
> Is it always encouraged to upgrade spkgs to more current stable
> upstream version?
No. I'd say it's neither encouraged nor discouraged.
> Is it always encouraged to upgrade spkgs to more current stable
> upstream version?
Usually patching a package is easier than updating to the latest
upstream version. Sometimes upstream upgrades break stuff. But if it's
easy to upgrade, then sure, why not do it?
Paul-Olivier Dehaye
Oct 16, 2012, 5:58:50 AM10/16/12
to sage-...@googlegroups.com
Yes, like #13541
Volker Braun
Oct 16, 2012, 6:43:36 AM10/16/12
to sage-...@googlegroups.com, paul-oliv...@math.uzh.ch
Given the choice between update (drop a patch that is fixed upstream) and fork (maintain a separate patch), I think we should always opt for the former. Otherwise we'll just get bogged down in an ever-increasing maintenance headache. Don't reinvent the wheel.
So I'd say we should always upgrade to new upstream stable releases. Sometimes that uncovers bugs, which we then can report upstream.
Julien Puydt
Oct 16, 2012, 7:22:34 AM10/16/12
to sage-...@googlegroups.com
Le 16/10/2012 12:43, Volker Braun a �crit :
For example, in "debian stable", the adjective refers to the fact that
the bugs are stable, precisely because things aren't updated to latest
upstreams. The downside is that it is always using several years old
software, even when it gets out! And that makes sense...
On the other end, when you're looking for say an elliptic curve
algorithm or trying to make some things explicit in some very
specialized domain, then you are generally interested in the latest and
greatest.
Isn't sage geared toward research-level mathematics anymore?
Snark on #sagemath
> Given the choice between update (drop a patch that is fixed upstream)
> and fork (maintain a separate patch), I think we should always opt for
> the former. Otherwise we'll just get bogged down in an ever-increasing
> maintenance headache. Don't reinvent the wheel.
>
> So I'd say we should always upgrade to new upstream stable releases.
> Sometimes that uncovers bugs, which we then can report upstream.
It depends.
> and fork (maintain a separate patch), I think we should always opt for
> the former. Otherwise we'll just get bogged down in an ever-increasing
> maintenance headache. Don't reinvent the wheel.
>
> So I'd say we should always upgrade to new upstream stable releases.
> Sometimes that uncovers bugs, which we then can report upstream.
For example, in "debian stable", the adjective refers to the fact that
the bugs are stable, precisely because things aren't updated to latest
upstreams. The downside is that it is always using several years old
software, even when it gets out! And that makes sense...
On the other end, when you're looking for say an elliptic curve
algorithm or trying to make some things explicit in some very
specialized domain, then you are generally interested in the latest and
greatest.
Isn't sage geared toward research-level mathematics anymore?
Snark on #sagemath
Reply all
Reply to author
Forward
0 new messages