[wx-dev] [all] 2.7.0 and releases organization in general

Vadim Zeitlin vadim at wxwindows.org
Sun Aug 6 11:09:40 PDT 2006


On Sun, 06 Aug 2006 18:59:28 +0100 Alex Bligh <alex at alex.org.uk> wrote:

AB> What I proposed was adding a reference to announce.txt, then
AB> inserting the following material on the web site [1]:
AB> 
AB> [start]
AB> No guarantee of ABI or API compatibility is given between 2.7 and 2.6, or
AB> between different releases of the 2.7 series. You should thus expect that
AB> if your program compiles under one version of wx 2.7, it may well not
AB> compile under a subsequent version of 2.7. If you want to guarantee your
AB> program will always compile and run, then you may either need to ship it
AB> with a particular snapshot of 2.7, OR perhaps 2.7 is not for you, and you
AB> should use 2.6 instead. 2.7 has also received less testing than 2.6, and
AB> many of its features are newer; if this worries you, then consider using
AB> 2.6 instead. We do not encourage 2.7 to be put into distributions. This is
AB> because it is still under active development, and the API between versions
AB> may change. On the other hand, 2.7 contains many features and indeed
AB> bug-fixes that are not present in 2.6.
AB> [end]
AB> 
AB> [1] = I am now wondering whether it would be better in docs/readme.txt,
AB> or perhaps both.

 I think it should be in both. The text does frighten me quite a bit though
as it gives the impression that you have no chance to recompile your
program with the next 2.7 version when usually the changes are not that
brutal, even in development releases. I'd propose a much more gentle
warning but I don't know if it's worth doing it as the majority here seems
to think that it's not enough. IMHO it's a mistake as it risks frightening
people away from 2.7.

 Regards,
VZ





More information about the wx-dev mailing list