On Thursday, January 12, 2017 at 6:01:55 PM UTC, Volker Braun wrote: > > The whole point of NEWS would be to have coarser granularity than > individual tickets. E.g. 7.4 -> 7.5 is over 300 tickets, and a 300-item > list is never a good answer to the question "whats new in this release". I > would envision a list of, say, 10-20 highlights to have associated news > fragments. >
yes, right, so you'd tag these "interesting for NEWS" tickets on trac, using some kind of trac plugin. > > > > > On Thursday, January 12, 2017 at 5:14:23 PM UTC+1, Dima Pasechnik wrote: >> >> Wouldn't it be better to relate news to closed/merged trac tickets? >> This might need an extra trac feature allowing for tagging tickets for >> priority in the sense >> of how much value a ticket adds. >> (critical/blocker/major hierarchy is something different) >> >> Then NEWS would come from harvesting ticket's summaries and arranging >> them >> w.r.t. the value-adding priority. >> This would be indeed almost painless, as opposed to extra files somewhere >> etc etc. >> (This might even fit within some of ODK deliverables :-)) >> >> Dima >> >> >> >> On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote: >>> >>> There is a somewhat painless approach to generating human-readable >>> release notes using https://github.com/hawkowl/towncrier. As far as the >>> ticket author is concerned, if you think that your ticket #12435 is of >>> wider interest and should be announced then all you'd have to do is add a >>> file >>> >>> echo "Added the last twin prime" > newsfragments/12435.feature >>> >>> Note that the fragment filename starts with the ticket number, so it >>> won't conflict with other news fragments. Then, when making a new release, >>> I concatenate the fragments into NEWS.rst as, for example, in >>> https://github.com/hawkowl/towncrier/blob/master/NEWS.rst >>> >> -- 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.
