plib-devel

[Plib-devel] Are we ready for 1.2.0?

[Steve B. <sjb...@ai...>]

Well, 1.1.12 has been out for a few days now - and apart from a few
build issues on the more oddball platforms, I've not had any complaints.

Are we ready to call this 1.2.0 with all the attendant implications
of stability and feature-freeze that goes along with that?

If so, I'll make a release of it and we'll start two parallel
threads:

  1.2.xx  -- Bug fixes to 1.2.0 only.

  1.3.xx  -- New features.

Please vote:

   A)  OK  release 1.2.0 immediately.

   B)  NO  I need new features in 1.1.xx before we go to 1.2.0

   C)  NO  I need more time for testing (or there are too many bugs)
           so please wait for a while longer (or make a 1.1.13 first).

If there is a majority for (A) within (say) 48 hours, I'll make 1.2.0,
if not I'll wait.

New features due immenently (but not yet ready for 1.2.0) include:

* New loaders/writers,
* The FGFS Line-of-Sight code
* Curt's new Sky model.

We'd have to delay at least a month to get those into 1.2.0  IMHO.

My vote is (A) because I'd like TuxKart to be released with 1.2.0
and I want to do that within the next couple of weeks.

-- 
Steve Baker   HomeEmail: <sjb...@ai...>
              WorkEmail: <sj...@li...>
              HomePage : http://web2.airmail.net/sjbaker1
              Projects : http://plib.sourceforge.net
                         http://tuxaqfh.sourceforge.net
                         http://tuxkart.sourceforge.net
                         http://prettypoly.sourceforge.net

RE: [Plib-devel] Are we ready for 1.2.0?

[Norman V. <nh...@ca...>]

Steve Baker writes:
>
>Well, 1.1.12 has been out for a few days now - and apart from a few
>build issues on the more oddball platforms, I've not had any 
>complaints.
>
>Are we ready to call this 1.2.0 with all the attendant implications
>of stability and feature-freeze that goes along with that?

The only thing I can think of is that the configure.in
script could use some cleaning up but it seems to have been
working as is so this shouldn't be a reason to hold up a release.

Therefore barring any reports of show stoppers

I vote for

>   A)  OK  release 1.2.0 immediately.

Many thanks again to all those who have contributed :-)

Norman