#8059: update Singular SPKG to newest upstream release
----------------------------------------------------------------------+-----
   Reporter:  malb                                                    |       
Owner:                                           
       Type:  enhancement                                             |      
Status:  positive_review                          
   Priority:  major                                                   |   
Milestone:  sage-4.5.2                               
  Component:  packages                                                |    
Keywords:                                           
     Author:  Martin Albrecht                                         |    
Upstream:  Reported upstream. Little or no feedback.
   Reviewer:  David Kirkby, Simon King, William Stein, John Palmieri  |      
Merged:                                           
Work_issues:                                                          |  
----------------------------------------------------------------------+-----

Comment(by drkirkby):

 Replying to [comment:106 mpatel]:
 > I'm working on 4.5.3.alpha0, which will contain a mix of spkg updates
 and repository patches from report {32}.  Should I attempt to merge this
 ticket into 4.5.3 or wait for a dedicated Sage release?  Also, can someone
 indicate exactly which spkg and patch to apply?  Thanks!

 Does this have to be called 4.5.3? I'd feel a lot happier calling it 4.6.0
 if there's a major upgrade like Singular. But I think you should try to
 upgrade Singular.

 I don't see the need of a dedicated release - there are lots of updates
 that have almost no chance of conflicting with this.

 I guess I'm one of the people that believes increments in the last digit
 are just minor changes (bug fixes) and not major new components. It's just
 the release number I don't like - I think its right to merge this, and
 some .spkg updates. Pari seems to have stalled again, so I'd go for
 Singular.

 That said, I seem to be in a minority who feel version numbers should
 reflect the sort of updates that take place. Almost everyone seems happy
 with random numbers!

 Dave

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8059#comment:108>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to