Agreed.

On Jan 21, 2007, at 1:23 PM, Hansenet Mail wrote:

I have no objections whatsoever. Thanks for the great work and the lots of
effort you have put into this, Mark :-)

Greetings,

Yogi



-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:wesnoth-dev- [EMAIL PROTECTED] Im
Auftrag von Nils Kneuper
Gesendet: Samstag, 20. Januar 2007 22:32
An: Mark de Wever
Cc: [email protected]
Betreff: Re: [Wesnoth-dev] Terrain branch update + trunk locking + merge
plans

Mark de Wever schrieb:
Hi,

I've converted and tested all campaigns except UtbS and the terrain
branch seems to work correctly (expect for some bugs inherited from
trunk.) UtbS will be converted this week.

Next weekend I'd like to convert all MP stuff and request a lock on
these files. Note the freeze of the Campaigns has been broken more
than once but thusfar it hasn't caused me trouble. Changing a map
after conversion _will_ give trouble so if somebody objects against a
freeze let it know now. If I don't get objections I regards the MP
stuff being frozen starting on the 27th of January (GMT).

Once I've converted all stuff I would like other people to also test
my branch especially the MP part, since I'm not familiar with MP there might be things I miss. Once the conversion is done I'll also post the
test request in the forum.

At the moment I'm targetting for a mergeback on the 10th of February
and I would like to have a short full trunk freeze in order to merge
the stuff back. I'll post more about that when the merge back is
getting closer.


I would really welcome having the merge done right now. This way it is
possible to state "XYZ is broken atm and needs to be converted" and the stuff already converted can be tested in a nice manner. I know that UTBS would not work if this happens but at least the already converted content gets testing. I think atm there are not many users for the terrain branch itself. Here are the benefits I see that stand in favor if a direct merge:
- More people testing the already converted content.
- Easier to stay in sync, as in little changes to campaigns and such are not this likely to cause problems. There would only be a freeze for some days per campaign/folder/whatever be needed. This is easier to enforce than a
freeze for many weeks for almost all of the content.
- It is trunk, we really are expected to break it every now and then...

Problems with a direct merge:
- Some stuff will definatly not work (UTBS). Since that is know a list could be posted with stuff known not to work yet and a request to test the rest
for a moment.
- Due to broken stuff some bug reports might appear though I think most people using trunk are also subscribed to this ml or read the forum so I
don't think this is a real problem. If it is: I am good at closing any
stuff. ;)

Does anyone have other reasons to wait with the merge? Anyone agreeing with me that it should be done now? I would really welcome that merge to happen ASAP so that the engine gets as much testing from anyone as possible. As long as it is in an extra branch I think there are not many people testing
it...
Greets,
Nils Kneuper aka Ivanovic

_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev


_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev



_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev

Reply via email to