Hi Jori, On 2017-05-26, Jori =?ISO-8859-1?Q?M=E4ntysalo?= <jori.mantys...@uta.fi> wrote: > This was done in ~10 bigger ticket and another ~10 with small > modifications. As an example see https://trac.sagemath.org/ticket/21861 > > Hence the ticket system would be wrong place for this. For something like > this we should have a wiki page.
How do you come to that conclusion? New features are provided in trac tickets, and thus trac is exactly the right place to highlight what a ticket provides. And how would you keep a wiki in sync with the tickets that are really merged in a release? The ticket author would usually write the highlight when (s)he is done writing the code, but it may be that it is merged only much later. > It should concentrate on user viewpoint: It > may be that a backend function for version 8.1 takes much work and a > interface function for version 8.2 is quite trivial; then the developer > should say nothing in the highlights of 8.1. How should the developer know what version he is supposed to write the highlights for? Best regards, Simon -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
