RE: [Bodington-developers] creationmenu.html problem

[Peter C. <Pet...@me...>]

> From: [...] Sean Mehan
> Why can't we work until Wed. On wed we chop off new stuff. This is =20
> the plan as it presently stands.
>=20
> Then we can take a day or three to finish some quick testing.
>=20
> Then we can finalize this and have 2.6 out a week or so after we =20
> said, which is pretty good.

OK.  So this would be going straight for 2.6.0 with *no* 2.5.* testing
or candidate releases before it - seems a bit odd to have been at the
meeting in February where the new odd/even numbering scheme was
described, but hey.

I'm with Colin - releasing a half-baked build as 'production quality',
burning CDs of it etc. isn't going to endear us to any prospects, nor is
it going to help sell any next-generation system such as Tetra.

> We have already promised to deploy the 2.6 here at UHI mid=20
> August. We =20
> must adhere to this as people need access to the new tool set=20
> at that =20
> time. They have already planned on it (e.g. Bookmarks).

"The 2.6" or "the new version at that time"?

If UHI has time constraints that mean it has to take an interim build in
mid-August, then that is UHI's internal decision.  However, one
organisation's internal decision should not affect the declaration of a
production quality release from a cross-institution development team
such as the one for Bodington.  If, as a result of their internal
constraints, UHI wish to put in a lot of testing effort in order to
validate their decision and meet their timescales... that's UHI's
decision.  UHI is not Bodington or bodington.org - at least, not unless
the academic politics are *very* different from the public face - and
the two organisations' objectives may legitimately differ.

		- Peter

"The bitterness of poor quality remains long after the sweetness of
meeting the deadline has gone." - somebody or other.