It sounds to me like a good idea. We could build a list of those tickets right before a public release and publish it somehow, with links toward the tickets.
It would mean trying our best to make the tickets title/description a bit more "user-friendly" than usual, and it might comfort those of us who are always worried about our users being taken aback by the new changes introduced by an update. Of course that's only useful if we all agree on something like that and try to enforce it all together. Nathann On 9 February 2016 at 20:53, Jori Mäntysalo <jori.mantys...@uta.fi> wrote: > Slightly related to #20026, i.e. changing default colors for a small part of > Sage: > > Could we have a specific trac keyword for user-visible changes? Then we > could make a semi-automatic "What's new in version X" better. Anything that > deprecates something should always have that keyword set. But not only them, > also those tickets that change some default value. > > As an example, some versions ago .plot() for poset gave the picture > upside-down with dot2tex installed. Ticket correcting that would have the > keyword set. > > (Warning: Got the idea 15 minutes ago. Can be a very bad idea.) > > -- > Jori Mäntysalo -- 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.
