Re: [XBoard-devel] new developer release

[Arun Persaud]

Hi

> why do we call the release from master a "developer release"?
> Will we ever do "version releases" from this branch? It is the
> development branch, after all, so any release is bound to be
> a developer release, until we are ready to call it 4.5.0.

well, so the name of developer release sounds appropriate :) I think
everything that isn't stable, e.g. the latest official version should be
called developer release as far as making a final release from master, I
say it depends on how much testers we get for the new features on master
and on how fast we can get the gtk-branch to catch up with master...

> For the v4.4.x branch we clearly make the destinction, so
> a "developer release" will be considered inferior to the release
> of a new version, whch will deter people from using it. E.g.
> it might not go into Debian. It should be more clear to people
> if they can expect the release of a "more final" version from
> master, or if "this is it".

hmm, so how would you call the releases?

> Now I guess that in this particular case what we have in both
> branches actually does fall short of the mark for a "version
> release": The tar ball has parser.c in the winboard directory,
> while the gcc and ms Makefiles do look for it in the XBoard
> directory, so it will not build unless you have flex installed.
> On the other hand, this means the release is probably not
> broken for compiling with the IDE of the Windows compiler.

yes, perhaps we can come up with something better... e.g. make the
makefile test if flex is installed and then either generate it or use a
fallback version? or should we for the windows version just always
include an up to date parser.c with the release?

ARUN