Re: LYNX-DEV 2.7 release.

[Al Gilman]

  From: address@hidden (Scott McGee (Personal))

  My thoughts concerning a 2.7 release. 
  
  3. I was under the impression that we needed a beta period to shake out any
  little bugs, but was waiting for a "no new features" peroid to be declared
  like last time.
  
I see benefits to recognizing three separate steps or phases in processing
a release:

        I. Last Call:
        This is where we decide the requirements for the version to 
        be released.  Andrew mentioned this being used in IETF.
        In my snail's eye view, this takes about a week to get all
        the issues on the table and about another week to finish
        arguing about them.  For this phase, we would benefit from
        the services of a scorekeeper:  someone who will keep a publicly 
        accessible [bookmark] page with a list of issues and what
        the scorekeeper thinks is the rough consensus on each issue.
        [Values of status per issue could be: (raised, rejected,
        accepted, deadlock)]  Is there someone other than me who
        would be willing to try to keep this list?

        II. Productizing:
        In this phase the mods for the requirements accepted in the
        first phase are implemented and integrated.  It is also the
        time for library and documentation cleanup, such as what
        Henry suggested.

        The basic exit requirement for this phase is that there is
        a draft release package meeting all the requirements set in
        the Last Call phase which compiles and appears to work on
        one system.

        III. Beta testing:
        In this phase the portability of the product is verified and
        it gets exposed to real users.
        Here a list we can benefit from is the list of systems for which we
        have people building the system.  I will pull together an index 
        of those that responded to my earlier post.

I don't know if it is too much to ask that there be a
publicly-accessible installation of Fote's code during the Last
Call phase.  It would help the compilation-challenged among us
relate to the discussion.

--
Al Gilman

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;