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

[Vadim Zeitlin]

On Sun, 06 Aug 2006 13:04:16 +0100 Alex Bligh <alex at alex.org.uk> wrote:

AB> >  I wouldn't put this. It's clear that some (long) time will pass before
AB> > 2.8 is available and I'm sure people will want and need use things like
AB> > wxAUI and wxRichTextCtrl before then. I think it's quite possible to use
AB> > 2.7 in production, you just need to freeze the version you use
...
AB> I think we should seriously discourage people from doing this.
...
AB> Note it is quite possible (indeed even relatively easy) to use all
AB> this new fun stuff with 2.6.

 So what's the difference? The new stuff can (and, I agree, will) change
in 2.7 so people using it either with 2,7 or 2.6 may/will have to update
their code. I don't understand how backporting it to 2.6 (and using the
version which likely didn't receive any testing at all) is better than
using a frozen snapshot of 2.7? Let me also say that from support point of
view I strongly prefer answering questions about bugs/problems in 2.7
rather than in some custom Frankenstein version made of bits and pieces of
different releases.

AB> I agree there is no point crying wolf and saying "this is likely
AB> to make your CPU catch fire and erase all your data",

 The experience shows that this is, without doubt, how people understood
the warnings about release being unstable in the past. This is why I want
to avoid using the words "unstable" and "testing" at all and prefer using
"development" release.

AB> but that said, we should be quite, about what will happen w.r.t. ABI
AB> support, and err on the side of caution.

 Again, please feel free to modify docs/publicity/announce.txt to be more
explicit about it but personally I think that current wording
("compatibility is not assured among between different 2.7 series
versions") is clear enough, isn't it?

 Regards,
VZ