Am 2015-05-04 um 12:46 schrieb Volker Braun:
> It didn't work, there is no deprecation period for removing bugs.

I see. Sorry, that was not clear to me, neither here nor on the ticket.

Regards, CH


> 
> 
> On Monday, May 4, 2015 at 11:14:43 AM UTC+2, Clemens Heuberger wrote:
> 
>     On 2015-05-04 10:55, Volker Braun wrote:
>     > We intentionally deleted the pyopenssl spkg. If it can be found on a
>     mirror then
>     > that is only because it hasn't been updated.
>     >
>     > This is http://trac.sagemath.org/ticket/18261
>     <http://trac.sagemath.org/ticket/18261>
> 
>     I am not too happy that the instructions in the documentation of the 
> _current_
>     _stable_ release lead to a link to a no longer existing file.
> 
>     Shouldn't there be some analogy to our deprecation policy? Or, 
> alternatively, a
>     new stable release fixing the documentation issue?
> 
>     What is the policy for removing spkgs, also in relation to 
> reproduceability of
>     old research? I can probably compile old sage versions if needed for some 
> old
>     non-polished code, but if the corresponding parts of 
> sage-as-a-distribution are
>     no longer available? (Granted, pyopenssl is probably not about research, 
> just
>     about infrastructure).e
> 
>     Regards, CH
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to