#11321: Make lcalc compatible with the new PARI
--------------------------------------------+-------------------------------
   Reporter:  jdemeyer                      |          Owner:  tbd              
                             
       Type:  defect                        |         Status:  needs_review     
                             
   Priority:  major                         |      Milestone:  sage-4.7.1       
                             
  Component:  packages                      |       Keywords:  lcalc spkg       
                             
Work_issues:                                |       Upstream:  Reported 
upstream. Developers acknowledge bug.
   Reviewer:  Volker Braun, Leif Leonhardy  |         Author:  Jeroen Demeyer   
                             
     Merged:                                |   Dependencies:  #11130           
                             
--------------------------------------------+-------------------------------

Comment(by leif):

 Replying to [comment:14 jdemeyer]:
 > About committing the changes: I find it very annoying to have to commit
 the changes everytime I make a change.

 You don't have to, unless you publish them. ;-)

 And you can always keep an uncommitted copy. I don't think it's much work
 to commit the changes if you have to create (perhaps upload) and announce
 a new spkg anyway.

 > If you are happy with the spkg except for the committing of the changes,
 I can still commit the changes at that point.

 Well, not committing the changes means ''I'' have to commit your changes
 ''in your name'' (with some random commit message) and repackage the spkg
  * in order to really test all changes (as files get deleted upon commit),
  * if I want to make some reviewer patch or a (follow-up) spkg based on
 yours.

 The first point is of course more crucial, since not only lazy people
 might just install and test the spkg as is, such that potential errors
 will only show up much later. So not committing the changes is IMHO simply
 bad practice unless the spkg is really and explicitly said to be in some
 alpha state, most probably not ready and not intended to get merged as is
 (despite needing review / testing by others), which might be ok in rare
 cases.

 There's a reason the term ''commit'' is used rather than just e.g. ''save
 changes'', the former implying some confidence or conviction by the author
 (or committer).

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11321#comment:15>
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