I think it is a good idea to have highlights in the release notes, otherwise we may give the impression that all we do is fix bugs (sometimes). There must be many Sage users who do not bother to upgrade every time, possibly basing that decision on whether anything interestng strikes them in the release notes.
The person with the best overview of what's in a new release is the release manager. He/she already does a lot, but could be the one to ask authors of important tickets to write something at the point of merging them. On 26 May 2017 at 13:21, Jori Mäntysalo <jori.mantys...@uta.fi> wrote: > On Fri, 26 May 2017, Simon King 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. > > > I think that most tickets are not highlights, and those that are, are > usually made of smaller tickets. (As big enhancements are hard to review.) > >> 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. > > > Mostly it should be done on rc-phase. But of course when you see your > ticket closed, you can think if you now have got something ready for > highlights. > > -- > 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.
