Re: [perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-03 Thread Bob Rogers
From: Geoffrey Broadwell <[EMAIL PROTECTED]> Date: Tue, 03 Jun 2008 14:21:28 -0700 OK, how about this . . . -'f Perfect. -- Bob

Re: [perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-03 Thread Patrick R. Michaud
On Tue, Jun 03, 2008 at 02:21:28PM -0700, Geoffrey Broadwell wrote: > OK, how about this: > > 1. As with Bob's suggestion, DEVELOPING is reduced to just the > unchanging middle paragraph. It is then merely a flag -- removing that > function as well is better left to another RT. > > 2. The inform

Re: [perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-03 Thread Will Coleda
On Tue, Jun 3, 2008 at 5:21 PM, Geoffrey Broadwell <[EMAIL PROTECTED]> wrote: > On Mon, 2008-06-02 at 20:28 -0700, chromatic via RT wrote: >> On Monday 02 June 2008 20:05:22 Bob Rogers wrote: >> >> > Agreed, but doesn't this info really belong in README? Then DEVELOPING >> > really only needs the

Re: [perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-03 Thread chromatic
On Tuesday 03 June 2008 14:21:28 Geoffrey Broadwell wrote: > OK, how about this: > > 1. As with Bob's suggestion, DEVELOPING is reduced to just the > unchanging middle paragraph. It is then merely a flag -- removing that > function as well is better left to another RT. > > 2. The information abou

Re: [perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-03 Thread Geoffrey Broadwell
On Mon, 2008-06-02 at 20:28 -0700, chromatic via RT wrote: > On Monday 02 June 2008 20:05:22 Bob Rogers wrote: > > > Agreed, but doesn't this info really belong in README? Then DEVELOPING > > really only needs the middle paragraph, which is unchanging, and there > > would be one less file to have

Re: [perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-02 Thread chromatic
On Monday 02 June 2008 20:05:22 Bob Rogers wrote: > Agreed, but doesn't this info really belong in README? Then DEVELOPING > really only needs the middle paragraph, which is unchanging, and there > would be one less file to have to update when cutting a new release. > >Or is there some purpos

[perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-02 Thread Bob Rogers
From: "Will Coleda via RT" <[EMAIL PROTECTED]> Date: Mon, 02 Jun 2008 19:31:15 -0700 On Tue May 20 20:53:06 2008, japhb wrote: > What a developer might want to know is exactly the info described in the > notes at the bottom of the file -- what was the last release, how long > ha

[perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-06-02 Thread Will Coleda via RT
On Tue May 20 20:53:06 2008, japhb wrote: > Here's the current DEVELOPING file: > > > # $Id$ > > THIS RELEASE: Parrot 0.6.2 2008.05.20 > PREVIOUS RELEASE: Parrot 0.6.1 2008.04.15 > > This file should only exist in development distributions. Delete it > (and its entry in

[perl #54562] [TODO] DEVELOPING should stop lagging reality

2008-05-21 Thread via RT
# New Ticket Created by Geoffrey Broadwell # Please include the string: [perl #54562] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=54562 > Here's the current DEVELOPING file: # $Id$ THIS RELEASE: Parrot