#18113: Warning for unstable/experimental code
---------------------------+---------------------------------
   Reporter:  dkrenn       |            Owner:
       Type:  enhancement  |           Status:  new
   Priority:  major        |        Milestone:  sage-6.6
  Component:  misc         |         Keywords:  sd66, warning
  Merged in:               |          Authors:
  Reviewers:               |  Report Upstream:  N/A
Work issues:               |           Branch:
     Commit:               |     Dependencies:
   Stopgaps:               |
---------------------------+---------------------------------
 During SageDays66 and on [[https://groups.google.com/forum/#!topic/sage-
 devel/LXWs6KOw0Lk]] there were discussions about the possibility to add
 code to Sage which is marked as "experimental". For this code no
 deprecation would be needed (for some time, e.g. a year or when the
 developers decide) in case of changes in the code.

 One motivation for this is, that many modules are developed not in Sage
 but outside (but with the goal of implementing it in to Sage when ready).
 This is done later, when it is clear, that the designs have turned out to
 be a good choice (and maybe changed a couple of times). Having it included
 in Sage from the beginning would have lead to several deprecations in many
 cases, which are a lot of effort and therefore a barrier in the
 development process.

--
Ticket URL: <http://trac.sagemath.org/ticket/18113>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to