Mark de Wever <ko...@xs4all.nl>:
> Choosing between fixing it now and do the final release in a week or fix
> it in 1.6 and trunk and have it a while tested in both I prefer the
> latter. (I see it as picking the lesser evil.)
That's certainly not how we handled potentially destabilizing changes around
the 1.4 release...
> I also think this is a symptom of a bigger problem, the development
> versions are not tested enough, which causes problems to pop up very late
> in the development cycle (same for 1.4).
Agreed.
> So maybe we should look at how
> to give the next development releases a better testing earlier in the
> cycle. Preferably I'd like to see more user testing starting in the
> middle of the cycle so we still have time to do more intrusive changes.
Yes, and while we're at it I'd like a pony.
That is a deliberately sarcastic idiom in English conveying that
wishes don't count for much. I think the only way we're going to get
more user testing is by shipping "stable" releases more often, which
is to say seriously shortening our development cycle.
> So I don't think Wednesday should be a hard
> date if there are good reasons to delay it a few days, however I'd like
> to have the announcement as planned on Sunday.
Seems reasonable. I'd like to hear from fendrin on the state of the
test suite before we make a final decision.
> I only have one bug [1] left which should be fixed before tagging, I
> expect to do that this evening. I've an ugly fix that needs some
> polishing and some more testing, but I'm quite sure I'll be ready this
> evening.
Having fixed theboth recent NR bugs, I have no remauining issues
that need to be pre-1.6
> Would it be an idea to fork 1.6 about a day after tagging so commits
> which are needed in both trunk and 1.6 can be applied to both without
> merging?
If we're going to do that, what would the point be of tagging earlier?
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Wesnoth-dev mailing list
Wesnoth-dev@gna.org
https://mail.gna.org/listinfo/wesnoth-dev
