On 2009/3/17, Nils Kneuper wrote: > I just wanted to inform you about the deadline for commits that are meant to > go > into 1.6. That is everything in until tomorrow in the afternoon in Europe will > be in, everything later will not. The firm "pencils down date" is as follows: > > March 18th, 5PM GMT+1 > (as in "five in the afternoon in Europe (Paris/Berlin/...)") > > Currently I even think about placing an "svn lock" at this time to make sure > that it is done for the moment. The lock will be released with a) tagging 1.6 > and b) branching trunk over to branches/1.6. If you have *anything* else that > I > have to wait for, ping me early in IRC, so that I can consider pausing for > your > change/fix. If I get nothing, I will "just" get it done...
I just ran a diffstat and this is what I obtain: - for WML (data/): 86 files changed, 542 insertions(+), 566 deletions(-) - for C++ (src/): 23 files changed, 171 insertions(+), 140 deletions(-) In other words, the 1.6 release will have hardly been tested by rc3. So I would like to suggest yet another release candidate, so that the 1.6 release actually gets some testing done. Ideally (and this also happens to be true in most projects), the release should be identical to the last release candidate, except for the version number. I know such a delay would be annoying (at least it annoys me, especially due to the 300KB patches lying on my harddrive waiting for the branch). But having to release a 1.6.1 fix right after 1.6 was released would feel pretty bad. Please consider it. Best regards, Guillaume _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
