On Tue, Jan 17, 2017 at 1:48 PM, Thierry
wrote:
> On Tue, Jan 17, 2017 at 12:35:48PM +, Simon King wrote:
>> On 2017-01-16, David Roe wrote:
>> > I don't think anyone's arguing that a changelog is a bad idea. The question
>> > is just whether it's easier to make from fragments in the reposito
On Tue, Jan 17, 2017 at 12:35:48PM +, Simon King wrote:
> On 2017-01-16, David Roe wrote:
> > I don't think anyone's arguing that a changelog is a bad idea. The question
> > is just whether it's easier to make from fragments in the repository or
> > from a new field on trac. Personally I think
On 2017-01-16, David Roe wrote:
> I don't think anyone's arguing that a changelog is a bad idea. The question
> is just whether it's easier to make from fragments in the repository or
> from a new field on trac. Personally I think trac,
+1.
I know that some people believe it is old fashioned, bu
>
>
> The expertise to choose a suitable aggregation rule for the poll results
> is in house
> (literally - my wife does research on this sort of stuff, computational
> social choice :-)).
>
True! But she also knows there ain't no suitable rule for all definitions
of suitable ... luckily it
I don't think anyone's arguing that a changelog is a bad idea. The question
is just whether it's easier to make from fragments in the repository or
from a new field on trac. Personally I think trac, though being able to
edit fragments from previous tickets is appealing. Either way, there should
be
On Fri, Jan 13, 2017 at 4:54 PM, Dima Pasechnik wrote:
>
>
> On Friday, January 13, 2017 at 3:41:23 PM UTC, Erik Bray wrote:
>>
>> On Fri, Jan 13, 2017 at 4:32 PM, Dima Pasechnik wrote:
>> >
>> >
>> > On Friday, January 13, 2017 at 11:15:49 AM UTC, Erik Bray wrote:
>> >>
>> >> On Thu, Jan 12, 201
On Sunday, January 15, 2017 at 6:58:38 PM UTC, William wrote:
>
> On Sun, Jan 15, 2017 at 5:18 AM, Dima Pasechnik > wrote:
> > 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
> >> n
On Sun, Jan 15, 2017 at 5:18 AM, Dima Pasechnik wrote:
> 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 co
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
>
On Friday, January 13, 2017 at 10:05:56 PM UTC, Volker Braun wrote:
>
> On Friday, January 13, 2017 at 8:38:50 PM UTC+1, Jori Mäntysalo wrote:
>>
>> If #1 adds foo() to graphs and #2 adds bar(), then the list should have
>> something like "Graph enchancements: foo() and bar()." Which ticket
>> sh
On Friday, January 13, 2017 at 8:38:50 PM UTC+1, Jori Mäntysalo wrote:
>
> If #1 adds foo() to graphs and #2 adds bar(), then the list should have
> something like "Graph enchancements: foo() and bar()." Which ticket should
> contain that information?
>
Ticket #2 could delete newsfragment/1.fea
On Friday, January 13, 2017 at 11:38:50 AM UTC-8, Jori Mäntysalo wrote:
>
>
> If #1 adds foo() to graphs and #2 adds bar(), then the list should have
> something like "Graph enchancements: foo() and bar()." Which ticket should
> contain that information?
>
>
Meta-ticket #3 "Graph enhancements in
On Fri, 13 Jan 2017, Erik Bray wrote:
Yes, I support this. The idea is to have a high-level view that end
users can digest as to what changed as it impacts them. This
certainly *should* include bug fixes - -
What tickets should not be on the list? I think that most bugs should not
be listed
On Friday, January 13, 2017 at 4:54:57 PM UTC+1, Dima Pasechnik wrote:
>
>
> it's not really documentation, it is more of advertising!
>
> some kind of write-once read-never thing, many people won't be bothered.
>
I also do not read change log for every release, but when my code is
affected by
On Friday, January 13, 2017 at 3:41:23 PM UTC, Erik Bray wrote:
>
> On Fri, Jan 13, 2017 at 4:32 PM, Dima Pasechnik > wrote:
> >
> >
> > On Friday, January 13, 2017 at 11:15:49 AM UTC, Erik Bray wrote:
> >>
> >> On Thu, Jan 12, 2017 at 9:48 PM, Kwankyu Lee
> wrote:
> >> >
> >> >
> >> >
On Fri, Jan 13, 2017 at 4:32 PM, Dima Pasechnik wrote:
>
>
> On Friday, January 13, 2017 at 11:15:49 AM UTC, Erik Bray wrote:
>>
>> On Thu, Jan 12, 2017 at 9:48 PM, Kwankyu Lee wrote:
>> >
>> >
>> > On Thursday, January 12, 2017 at 8:10:54 PM UTC+1, Dima Pasechnik wrote:
>> >>
>> >>
>> >>
>> >> O
On Friday, January 13, 2017 at 11:15:49 AM UTC, Erik Bray wrote:
>
> On Thu, Jan 12, 2017 at 9:48 PM, Kwankyu Lee > wrote:
> >
> >
> > On Thursday, January 12, 2017 at 8:10:54 PM UTC+1, Dima Pasechnik wrote:
> >>
> >>
> >>
> >> On Thursday, January 12, 2017 at 6:01:55 PM UTC, Volker Braun
On Thu, Jan 12, 2017 at 9:48 PM, Kwankyu Lee wrote:
>
>
> On Thursday, January 12, 2017 at 8:10:54 PM UTC+1, Dima Pasechnik wrote:
>>
>>
>>
>> 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
>>> individu
On Thursday, January 12, 2017 at 8:10:54 PM UTC+1, Dima Pasechnik wrote:
>
>
>
> 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
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
> wo
One could perhaps use metatickets on trac for that.
On Thursday, January 12, 2017 at 10:01:55 AM UTC-8, 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 answe
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.
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
On Thursday, January 12, 2017 at 1:48:28 PM UTC+1, Simon King wrote:
>
> On 2017-01-12, Volker Braun > wrote:
> > Yes, to the Sage src tree. That is, we would add a newsfragments
> directory
> > somewhere under $SAGE_ROOT.
>
> Seriously???
>
How else would the ticket authors associate a self-
On 2017-01-12, Volker Braun wrote:
> Yes, to the Sage src tree. That is, we would add a newsfragments directory
> somewhere under $SAGE_ROOT.
Seriously???
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop r
If you want the name "Sage" (vs. "sage") it must be under src/Sage
like in https://trac.sagemath.org/ticket/22176
--
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 s
Yes, to the Sage src tree. That is, we would add a newsfragments directory
somewhere under $SAGE_ROOT.
On Thursday, January 12, 2017 at 8:15:48 AM UTC+1, Simon King wrote:
>
> Hi Volker,
>
> On 2017-01-11, Volker Braun > wrote:
> > There is a somewhat painless approach to generating human-read
Hi Volker,
On 2017-01-11, 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 a
28 matches
Mail list logo
