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 to update when cutting a new release.
> >
> >    Or is there some purpose in keeping this information out of the hands
> > of mere tarball-downloaders?
> 
> DEVELOPING mostly exists so that people who check out interim releases run 
> extra tests by default and people who download only official releases don't.
> 
> There may be a better way to accomplish this.

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 about the next release moves to NEWS, where I think
it belongs.  As soon as a release is cut and functionality starts to be
committed, we should start updating NEWS.  A simple change to the format
of the header line makes it serve the duty previously done by the first
paragraph in DEVELOPING.

See the attached patch.


-'f

diff --git a/DEVELOPING b/DEVELOPING
index 66d50d4..b1d5aee 100644
--- a/DEVELOPING
+++ b/DEVELOPING
@@ -1,11 +1,5 @@
 # $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
+This file should only exist in development distributions.  Delete it
 (and its entry in the MANIFEST) before packaging Parrot up for a CPAN
 or other release distribution.
-
-'THIS RELEASE' is the goal of the current development.
-'PREVIOUS RELEASE' is the release that has been last let out into the wild.
diff --git a/NEWS b/NEWS
index d740ad8..bb6ba56 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,12 @@
 # $Id$
 
+New for next release (2008-06-17, version undecided)
+- Configuration
+  + expanded step gen::opengl
+- Miscellaneous
+  + ported OpenGL/GLU/GLUT bindings to Win32 and more Mac OS X variants
+  + generate OpenGL/GLU/GLUT bindings by parsing system headers
+
 New in 0.6.2
 - Specification
   + updated and launched pdd28_strings.pod

Reply via email to