On Sun, May 26, 2013 at 9:41 AM, Brett Cannon wrote:
>> The NEWS update script could even use the revision history to decide
>> which order to add entries to the bulleted list.
>
> I think the annoyance with this approach is you will have to remember
> to add a file every time you do anything wort
On Sat, May 25, 2013 at 12:05 PM, Nick Coghlan wrote:
> On Sun, May 26, 2013 at 1:29 AM, Gregory P. Smith wrote:
>> I like where you're heading with this but it still leaves merges during
>> Spruits and when a few people are working at once by putting stuff in a
>> single file.
I don't know if s
On Sun, May 26, 2013 at 1:29 AM, Gregory P. Smith wrote:
> I like where you're heading with this but it still leaves merges during
> Spruits and when a few people are working at once by putting stuff in a
> single file.
>
> Per news item / per issue files for each release that are riled up into th
On May 25, 2013 8:29 AM, "Gregory P. Smith" wrote:
>
>
> On May 25, 2013 1:40 AM, "Nick Coghlan" wrote:
> >
> > On Sat, May 25, 2013 at 2:01 PM, Eric Snow
wrote:
> > > On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
> > > wrote:
> > >> and it recognizes that users don't really need to look a
On May 25, 2013 1:40 AM, "Nick Coghlan" wrote:
>
> On Sat, May 25, 2013 at 2:01 PM, Eric Snow
wrote:
> > On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
> > wrote:
> >> and it recognizes that users don't really need to look across merge
> >> boundaries.
> >
> > This is tricky though for any p
On Sun, May 26, 2013 at 1:10 AM, Brett Cannon wrote:
> On Sat, May 25, 2013 at 4:40 AM, Nick Coghlan wrote:
>> The 3.3 branch layout would look like this:
>>
>> NEWS.next/
>> 3.3.txt # Categorised changes
>
> Categorized how? E.g. Core,Lib,Docs, etc.? Or "3.3 only", "3.3 and 3.4"?
J
On Sat, May 25, 2013 at 4:40 AM, Nick Coghlan wrote:
> On Sat, May 25, 2013 at 2:01 PM, Eric Snow
> wrote:
>> On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
>> wrote:
>>> and it recognizes that users don't really need to look across merge
>>> boundaries.
>>
>> This is tricky though for any
On Sat, May 25, 2013 at 2:01 PM, Eric Snow wrote:
> On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
> wrote:
>> and it recognizes that users don't really need to look across merge
>> boundaries.
>
> This is tricky though for any patch that is forward-ported to a
> release branch (a la 3.2->3.3
