Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
The main documentation is here: http://www.wesnoth.org/wiki/WesnothFormulaAIBranch It's admittedly rather poor though. You are welcome to tell me some things your AI aims to allow one to do, and I'll let you know if the formula AI can do that (or aims to be able to do that). On Tue, 2008-03-04 at 13:01 -0500, John McNabb wrote: > Is there a link to documentation on the new formala AI WML definition? > I am interested in seeing how much overlaps with my own side project > on developing an AI and whether it completely minimizes the need for > it. If my AI still has features that the formula AI doesn't, if there > are pieces that I can steal to make sure that the syntax for the two > different AIs is not too different when doing the same thing... > > Thanks, > Darth Fool > > On Mon, Mar 3, 2008 at 11:36 AM, David White <[EMAIL PROTECTED]> wrote: > > I have finished the merge; people can check in to 1.4. > > > > (Except I think I broke trunk until we work out how to link in > > boost-regex properly, which is now an added dependency) > > > > > > > > On Fri, 2008-02-29 at 22:53 -0800, David White wrote: > > > After 1.4 has been branched off, I would appreciate it if we could stop > > > all check-ins to the trunk for several hours, to give me a chance to > > > merge in the formula AI branch. > > > > > > David > > > > > > On Fri, 2008-02-29 at 12:30 +0100, Nils Kneuper wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > > > Hash: SHA1 > > > > > > > > Hi everybody! > > > > Currently it looks like trunk is about as stable as it can get. There > > is some > > > > more time left, basically for translators and artists to complete some > > stuff. I > > > > want to announce that I want to see svn froozen for the time that I do > > work on > > > > creating the package and testing it. So that there is only exactly one > > extra > > > > revision needed to fix any bugs that occur in my testing. My current > > plans are > > > > (and I am sure to be able to follow these): > > > > > > > > * Start packaging and testing on Sunday, 2nd March at 2pm (gmt+1) > > > > > > > > So the deadline for commits is ~1pm at that day. The freeze will > > probably last > > > > till about 8pm (gmt+1). In this timeframe there should be *no* > > commits, they > > > > will not go into the tarball anyway and might just create problems if > > smaller > > > > stuff occurs. The freeze will basically last until I declare 1.4 > > tagged (that is > > > > until you see the commit message for tags/1.4. As requested by esr I > > will then > > > > leave 1.4 still as trunk for some more hours (maybe three or four > > hours) for > > > > fixes that are small and have to get into both (stringfixes, tiny > > bugs, whatever). > > > > > > > > So to sum things up in short: > > > > > > > > * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) > > > > * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) > > > > * trunk free for 1.4+1.5 commits (not branched off yet): Sunday, 2nd > > March, 8pm > > > > (gmt+1) > > > > * branching off 1.4 to branches/1.4, trunk free for 1.5.0-svn commits: > > Sunday, > > > > 2nd March, 11pm > > > > > > > > > > > > Regarding what should be commited to 1.4 after 1.4 is tagged: > > > > Please do not commit any new feature stuff in there. 1.4 is meant to > > be bugfix > > > > and translation updates only. Yes, some new graphics are fine, but > > rewrites of > > > > scenarios, adding features, changing maps, adding music and such > > should *not* > > > > happen. The reason for this is that when eg adding one new piece of > > music in the > > > > music playlist all the games on the mp server will show as "remote > > scenarios" > > > > (can currently be observed with 1.3.19+svn on the official server). In > > general I > > > > would like to see the size of the package not change too much, that is > > it will > > > > increase due to translation updates, but that will basically be it. > > > > I think such a policy is rather sensible and a good compromise. > > > > > > > > Regarding the first post 1.4 dev release: > > > > > > > > I plan to at least wait 6 weeks with this. That is to give you some > > time to add > > > > all your new and shining features in there, which are likely to break > > things. I > > > > know that 1.5.0 will probably be rather broken due to the new stuff... > > > > > > > > Cheers, > > > > Nils Kneuper aka Ivanovic > > > > > > > > > > > > PS: If you need any changes to these plans, if there are none, I will > > procede > > > > with those plans. I will give status updates on IRC for the 1.4 > > release steps. > > > > -BEGIN PGP SIGNATURE- > > > > Version: GnuPG v2.0.7 (GNU/Linux) > > > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > > > > > iD8DBQFHx+zvfFda9thizwURAo+hAJ9jxyH9YgSWmd4uAV1jc2PIjQWvQACgiCWe > > > > BGdwcvYFMtsnaDuNcB4C3WU= > > > > =6cBT > > > > -END
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
On Sat, Mar 01, 2008 at 08:25:56AM +0100, Mark de Wever wrote: > On Fri, Feb 29, 2008 at 10:53:19PM -0800, David White wrote: > > After 1.4 has been branched off, I would appreciate it if we could stop > > all check-ins to the trunk for several hours, to give me a chance to > > merge in the formula AI branch. > > > > I agree that this would be a good idea. I also agree with Ivanovic's > proposal. I think 1.4 will be a really nice release :-) > > After the trunk is open I want to replace our SDL_ttf files with a depency > to the real library. It seems our fix has been first in 2.0.8 so I want to > keep that as minimum version. > > If nobody objects I'll look at this after Dave has reopend trunk. The change has been made, only the autotools build system has been updated. Regards, Mark de Wever aka Mordante/SkeletonCrew ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
Is there a link to documentation on the new formala AI WML definition? I am interested in seeing how much overlaps with my own side project on developing an AI and whether it completely minimizes the need for it. If my AI still has features that the formula AI doesn't, if there are pieces that I can steal to make sure that the syntax for the two different AIs is not too different when doing the same thing... Thanks, Darth Fool On Mon, Mar 3, 2008 at 11:36 AM, David White <[EMAIL PROTECTED]> wrote: > I have finished the merge; people can check in to 1.4. > > (Except I think I broke trunk until we work out how to link in > boost-regex properly, which is now an added dependency) > > > > On Fri, 2008-02-29 at 22:53 -0800, David White wrote: > > After 1.4 has been branched off, I would appreciate it if we could stop > > all check-ins to the trunk for several hours, to give me a chance to > > merge in the formula AI branch. > > > > David > > > > On Fri, 2008-02-29 at 12:30 +0100, Nils Kneuper wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > Hi everybody! > > > Currently it looks like trunk is about as stable as it can get. There is > some > > > more time left, basically for translators and artists to complete some > stuff. I > > > want to announce that I want to see svn froozen for the time that I do > work on > > > creating the package and testing it. So that there is only exactly one > extra > > > revision needed to fix any bugs that occur in my testing. My current > plans are > > > (and I am sure to be able to follow these): > > > > > > * Start packaging and testing on Sunday, 2nd March at 2pm (gmt+1) > > > > > > So the deadline for commits is ~1pm at that day. The freeze will > probably last > > > till about 8pm (gmt+1). In this timeframe there should be *no* commits, > they > > > will not go into the tarball anyway and might just create problems if > smaller > > > stuff occurs. The freeze will basically last until I declare 1.4 tagged > (that is > > > until you see the commit message for tags/1.4. As requested by esr I > will then > > > leave 1.4 still as trunk for some more hours (maybe three or four hours) > for > > > fixes that are small and have to get into both (stringfixes, tiny bugs, > whatever). > > > > > > So to sum things up in short: > > > > > > * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) > > > * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) > > > * trunk free for 1.4+1.5 commits (not branched off yet): Sunday, 2nd > March, 8pm > > > (gmt+1) > > > * branching off 1.4 to branches/1.4, trunk free for 1.5.0-svn commits: > Sunday, > > > 2nd March, 11pm > > > > > > > > > Regarding what should be commited to 1.4 after 1.4 is tagged: > > > Please do not commit any new feature stuff in there. 1.4 is meant to be > bugfix > > > and translation updates only. Yes, some new graphics are fine, but > rewrites of > > > scenarios, adding features, changing maps, adding music and such should > *not* > > > happen. The reason for this is that when eg adding one new piece of > music in the > > > music playlist all the games on the mp server will show as "remote > scenarios" > > > (can currently be observed with 1.3.19+svn on the official server). In > general I > > > would like to see the size of the package not change too much, that is > it will > > > increase due to translation updates, but that will basically be it. > > > I think such a policy is rather sensible and a good compromise. > > > > > > Regarding the first post 1.4 dev release: > > > > > > I plan to at least wait 6 weeks with this. That is to give you some time > to add > > > all your new and shining features in there, which are likely to break > things. I > > > know that 1.5.0 will probably be rather broken due to the new stuff... > > > > > > Cheers, > > > Nils Kneuper aka Ivanovic > > > > > > > > > PS: If you need any changes to these plans, if there are none, I will > procede > > > with those plans. I will give status updates on IRC for the 1.4 release > steps. > > > -BEGIN PGP SIGNATURE- > > > Version: GnuPG v2.0.7 (GNU/Linux) > > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > > > iD8DBQFHx+zvfFda9thizwURAo+hAJ9jxyH9YgSWmd4uAV1jc2PIjQWvQACgiCWe > > > BGdwcvYFMtsnaDuNcB4C3WU= > > > =6cBT > > > -END PGP SIGNATURE- > > > > > > ___ > > > Wesnoth-dev mailing list > > > Wesnoth-dev@gna.org > > > https://mail.gna.org/listinfo/wesnoth-dev > > > > > > ___ > > Wesnoth-dev mailing list > > Wesnoth-dev@gna.org > > https://mail.gna.org/listinfo/wesnoth-dev > > > ___ > Wesnoth-dev mailing list > Wesnoth-dev@gna.org > https://mail.gna.org/listinfo/wesnoth-dev > -- -
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
On Mon, Mar 03, 2008 at 08:36:15AM -0800, David White wrote: > I have finished the merge; people can check in to 1.4. > > (Except I think I broke trunk until we work out how to link in > boost-regex properly, which is now an added dependency) I fixed that for autotools. Regards, Mark de Wever aka Mordante/SkeletonCrew ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
I have finished the merge; people can check in to 1.4. (Except I think I broke trunk until we work out how to link in boost-regex properly, which is now an added dependency) On Fri, 2008-02-29 at 22:53 -0800, David White wrote: > After 1.4 has been branched off, I would appreciate it if we could stop > all check-ins to the trunk for several hours, to give me a chance to > merge in the formula AI branch. > > David > > On Fri, 2008-02-29 at 12:30 +0100, Nils Kneuper wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hi everybody! > > Currently it looks like trunk is about as stable as it can get. There is > > some > > more time left, basically for translators and artists to complete some > > stuff. I > > want to announce that I want to see svn froozen for the time that I do work > > on > > creating the package and testing it. So that there is only exactly one extra > > revision needed to fix any bugs that occur in my testing. My current plans > > are > > (and I am sure to be able to follow these): > > > > * Start packaging and testing on Sunday, 2nd March at 2pm (gmt+1) > > > > So the deadline for commits is ~1pm at that day. The freeze will probably > > last > > till about 8pm (gmt+1). In this timeframe there should be *no* commits, they > > will not go into the tarball anyway and might just create problems if > > smaller > > stuff occurs. The freeze will basically last until I declare 1.4 tagged > > (that is > > until you see the commit message for tags/1.4. As requested by esr I will > > then > > leave 1.4 still as trunk for some more hours (maybe three or four hours) for > > fixes that are small and have to get into both (stringfixes, tiny bugs, > > whatever). > > > > So to sum things up in short: > > > > * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) > > * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) > > * trunk free for 1.4+1.5 commits (not branched off yet): Sunday, 2nd March, > > 8pm > > (gmt+1) > > * branching off 1.4 to branches/1.4, trunk free for 1.5.0-svn commits: > > Sunday, > > 2nd March, 11pm > > > > > > Regarding what should be commited to 1.4 after 1.4 is tagged: > > Please do not commit any new feature stuff in there. 1.4 is meant to be > > bugfix > > and translation updates only. Yes, some new graphics are fine, but rewrites > > of > > scenarios, adding features, changing maps, adding music and such should > > *not* > > happen. The reason for this is that when eg adding one new piece of music > > in the > > music playlist all the games on the mp server will show as "remote > > scenarios" > > (can currently be observed with 1.3.19+svn on the official server). In > > general I > > would like to see the size of the package not change too much, that is it > > will > > increase due to translation updates, but that will basically be it. > > I think such a policy is rather sensible and a good compromise. > > > > Regarding the first post 1.4 dev release: > > > > I plan to at least wait 6 weeks with this. That is to give you some time to > > add > > all your new and shining features in there, which are likely to break > > things. I > > know that 1.5.0 will probably be rather broken due to the new stuff... > > > > Cheers, > > Nils Kneuper aka Ivanovic > > > > > > PS: If you need any changes to these plans, if there are none, I will > > procede > > with those plans. I will give status updates on IRC for the 1.4 release > > steps. > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v2.0.7 (GNU/Linux) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > iD8DBQFHx+zvfFda9thizwURAo+hAJ9jxyH9YgSWmd4uAV1jc2PIjQWvQACgiCWe > > BGdwcvYFMtsnaDuNcB4C3WU= > > =6cBT > > -END PGP SIGNATURE- > > > > ___ > > Wesnoth-dev mailing list > > Wesnoth-dev@gna.org > > https://mail.gna.org/listinfo/wesnoth-dev > > > ___ > Wesnoth-dev mailing list > Wesnoth-dev@gna.org > https://mail.gna.org/listinfo/wesnoth-dev ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nils Kneuper schrieb: | Nils Kneuper schrieb: | | * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) | | Turns run out! | | | * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) | | Turns run out! | | | * trunk free for 1.4+1.5 commits (not branched off yet): Sunday, 2nd March, 8pm | | (gmt+1) | | Currently active. For the next 4 to 6 hours you are free to commit stuff that is | meant to end in both, 1.4.x and in trunk. Do not commit any trunk-only stuff. | That has to wait 6 more hours until 1.4 is in its own branch. Turns run out! | | * branching off 1.4 to branches/1.4, trunk free for 1.5.0-svn commits: Sunday, | | 2nd March, 11pm | | In about 6h 1.4 will be branched off to branches/1.4. Then trunk/ is free for | new stuff. Though it would be good if you coordinated with Dave, so that he can | first merge his formula ai changes into trunk/src. Done. Now there is branches/1.4 for all the 1.4 stuff and trunk for all the things adding features and stuff. For the moment Dave asked to not commit stuff to trunk/src until he has a chance to merge in formula ai. Beside this you can start the "real work" on trunk again. It will be at least 6 weeks until the next dev release named 1.5.0. Regarding stuff that should go to branches/1.4: * translation updates * non-intrusive bugfixes * graphics update (if wanted/needed) That's basically everything. All the real polishing like "let's rewrite scenario XYZ" and "man, this feature would be great" should go to trunk instead. When we need a new stable release, there has to be at least one week of stringfreeze before this. Just as a warning for everybody of you. I don't think there will be something like 1.4.1 withhin the next three weeks, but just to make sure... Cheers, Nils Kneuper aka Ivanovic -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyzCLfFda9thizwURAmBoAJ9z0+DRTaebiRowxMKDyBhjalvE1QCcDCAn 5rPB39W7cKoGrjuDQ6Gf1/A= =M7gI -END PGP SIGNATURE- ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nils Kneuper schrieb: | * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) Turns run out! | * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) Turns run out! | * trunk free for 1.4+1.5 commits (not branched off yet): Sunday, 2nd March, 8pm | (gmt+1) Currently active. For the next 4 to 6 hours you are free to commit stuff that is meant to end in both, 1.4.x and in trunk. Do not commit any trunk-only stuff. That has to wait 6 more hours until 1.4 is in its own branch. | * branching off 1.4 to branches/1.4, trunk free for 1.5.0-svn commits: Sunday, | 2nd March, 11pm In about 6h 1.4 will be branched off to branches/1.4. Then trunk/ is free for new stuff. Though it would be good if you coordinated with Dave, so that he can first merge his formula ai changes into trunk/src. So now it's time to start the 1.4 celebrations. Cheers, Nils Kneuper aka Ivanovic -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyuCwfFda9thizwURAl1jAJ9YuW0SSd3aYMRlKVKOo8bmhRd1yQCeLJtx paCbx/6pSjeUbqyQgyCCFIA= =6o5d -END PGP SIGNATURE- ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
Mark de Wever <[EMAIL PROTECTED]>: > I do get the impression the rate of reported bugs is increasing > and I expect quite some bugs to be discovered in 1.4. > That being said; I do like to get and keep the bug count low but I think > it will be hard. I'm a little more optimistic, which is significant because I'm a fairly close second after Mordante in count of fixes. Yes, we've had a rash of new bugs lately, but I've noticed that the frequency of such reports is in general very noisy and bursty. I don't see any reason to fear this is a long-term trend. Also, there has been a trend over the last couple of months for the new bugs to be less about serious gameplay issues and more about polish and details. While the bug count has not decreased to the less than 30 that Mordante and I were shooting for, we have been trading deep bugs for shallow ones. We presently have zero bugs in the classes Blocker or Important, and following the recent demise of #4410 there are no longer any bugs that I see as indicators of serious archicture problems. This is encouraging. > The last weeks we ran into quite some 1.4-unfixable bugs, which > increased the bug count again. I think it would be nice to have a bug > stomping phase halfway towards 1.6 as well. That way we can still try to > solve the harder to fix bugs and try to make 1.6 even better as 1.4. In > this period we have a soft feature freeze, only features which do fix > bugs are allowed. I'm in favor of having a scheduled bug-stomping phase halfway before 1.6. But I have a more radical proposal. I think our stable release interval is too long. I think we need to shorten it to six months. Argument for this will follow in a separate post, so please respond to that. -- http://www.catb.org/~esr/";>Eric S. Raymond ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nils Kneuper schrieb: | Looks like my other mail was lost, so here again the remainder about the deadline: | | | * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) | | That is ~11h from now. Commit your stuff that is meant to get into 1.4.0! Deadline is over, everything seems to be fine. | | * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) Trunk is now *frozen*. There are *no* commits allowed in the next hours (that is until I say that trunk is free for 1.4+trunk commits (stuff that is meant for both). The only exception for commits is when I explicitly ask for stuff to be commited though I don't expect this to happen. Cheers, Nils Kneuper aka Ivanovic -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyqiffFda9thizwURAmGrAJ9SdtBhKle8U5YskdOPNA2JtjMajACfVOLi NYzOBtq2Nn0xLDeMIXa7uI0= =f+CP -END PGP SIGNATURE- ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
On Sat, Mar 01, 2008 at 07:05:07PM -0500, Eric S. Raymond wrote: > David White <[EMAIL PROTECTED]>: > > We should continue this. The team has done a tremendous job of making > > 1.4 as stable as possible. We should try to stay as close as possible to > > this ideal, attacking bugs aggressively and trying to keep our bug count > > as low as possible. We should not adapt an attitude of "oh well lets > > slam in lots of features and not worry about the bugs until later". The problem I see is that the last months we've been tackling bugs quite aggressively. Personally I spend most of my Wesnoth time on bug fixing. But we get quite a flood of new bugs and bug fixing seems a full time job. Post rc2 we have resolved 19 bugs, which is quite nice for about one week. I do get the impression the rate of reported bugs is increasing and I expect quite some bugs to be discovered in 1.4. That being said; I do like to get and keep the bug count low but I think it will be hard. I also think new features should be polished and fully implemented before the developer starts to work on a new project instead of committing half finished features and work on something else. That doesn't mean I'm against getting things in fast and clean up and polish in trunk! > Agreed. In fact, in spite of the fact that I've got a couple of > serious feature plans myself, I'd be quite happy if we stayed in > bug-stomping mode for a week or two after 1.4 release and only then > forked 1.5. I still want to do some bug fixing, but also start to work on the projects I assigned to myself, which means I'll have less time for bug stomping. (Some of those features are prerequisite to fix some other bugs.) The last weeks we ran into quite some 1.4-unfixable bugs, which increased the bug count again. I think it would be nice to have a bug stomping phase halfway towards 1.6 as well. That way we can still try to solve the harder to fix bugs and try to make 1.6 even better as 1.4. In this period we have a soft feature freeze, only features which do fix bugs are allowed. Regards, Mark de Wever aka Mordante/SkeletonCrew ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Looks like my other mail was lost, so here again the remainder about the deadline: | * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) That is ~11h from now. Commit your stuff that is meant to get into 1.4.0! | * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) Yes, it looks very much like I will be able to follow these plans. If you have any blockers, *NOW* is the time to state so. I will be available in #wesnoth-dev while doing all the tests regarding "does this stuff really work". So if anything really problematic comes up, please do ping me *immediately*. Cheers, Nils Kneuper aka Ivanovic -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHygbefFda9thizwURArq0AJ429+4y61TCtxVrgYHr/xWOKtvy3ACfSB8T Pc1FLCAmLacoTsn8GXqEmps= =ebaG -END PGP SIGNATURE- ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
Nils Kneuper <[EMAIL PROTECTED]>: > At the moment it looks like we are perfectly fine for 1.4... I have one issue left. Mordante rports that the file filtering in campaigns_clent.py doesn't work. I'll try to get that fixed before deadline. -- http://www.catb.org/~esr/";>Eric S. Raymond ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just as a reminder: Less than 11h are left until the deadline for commits meant to go into 1.4.0 is reached. Get your stuff commited, look out for serious breakage and be sure to write a mail or stay in #wesnoth-dev and ping me if you find any real problems. At the moment it looks like we are perfectly fine for 1.4... Cheers, Nils Kneuper aka Ivanovic -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHygKWfFda9thizwURAhhHAJ4gHYdSsD/ZkWVyx1gTVVbSbIjwHgCgmpwk ao3VS9WQzxAeLLKAbV3lB9k= =JZEy -END PGP SIGNATURE- ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric S. Raymond schrieb: | Agreed. In fact, in spite of the fact that I've got a couple of | serious feature plans myself, I'd be quite happy if we stayed in | bug-stomping mode for a week or two after 1.4 release and only then | forked 1.5. Personally I do think this does not make too much sense. We are already at a really good state. For those who are able to remember the 1.0.x and the 1.2.x times: there we have forked off the branch *before* the stable release, several month before in the case of 1.2. In general I think there will not be much benefit in waiting more than some hours for spelling-/grammarfixes that apply directly to both branches. Most bugfixes that are left will need bigger changes which should probably not happen in 1.4.x at all unless it is something really critical. The smaller stuff can be backported easy enough. Cheers, Nils Kneuper aka Ivanovic -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHygNSfFda9thizwURAqtaAJ0ZGxwad/6hqO11Dw6XiO8jeI0rvgCfTFzF Sv+gzuDZTQP/dMe/CFFFp+k= =NaxX -END PGP SIGNATURE- ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
David White <[EMAIL PROTECTED]>: > We should continue this. The team has done a tremendous job of making > 1.4 as stable as possible. We should try to stay as close as possible to > this ideal, attacking bugs aggressively and trying to keep our bug count > as low as possible. We should not adapt an attitude of "oh well lets > slam in lots of features and not worry about the bugs until later". Agreed. In fact, in spite of the fact that I've got a couple of serious feature plans myself, I'd be quite happy if we stayed in bug-stomping mode for a week or two after 1.4 release and only then forked 1.5. -- http://www.catb.org/~esr/";>Eric S. Raymond ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
On Fri, 2008-02-29 at 12:30 +0100, Nils Kneuper wrote: > Regarding the first post 1.4 dev release: > > I plan to at least wait 6 weeks with this. That is to give you some time to > add > all your new and shining features in there, which are likely to break things. > I > know that 1.5.0 will probably be rather broken due to the new stuff... I would like to add a clarifying point to this: while we know that adding features is much more likely to introduce bugs than not adding features, during Wesnoth's development we have always tried our best to make *every* release as stable as possible. This approach has worked well, often leading to development releases being more stable than 'stable' releases. We should continue this. The team has done a tremendous job of making 1.4 as stable as possible. We should try to stay as close as possible to this ideal, attacking bugs aggressively and trying to keep our bug count as low as possible. We should not adapt an attitude of "oh well lets slam in lots of features and not worry about the bugs until later". David ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
On Fri, Feb 29, 2008 at 10:53:19PM -0800, David White wrote: > After 1.4 has been branched off, I would appreciate it if we could stop > all check-ins to the trunk for several hours, to give me a chance to > merge in the formula AI branch. > I agree that this would be a good idea. I also agree with Ivanovic's proposal. I think 1.4 will be a really nice release :-) After the trunk is open I want to replace our SDL_ttf files with a depency to the real library. It seems our fix has been first in 2.0.8 so I want to keep that as minimum version. If nobody objects I'll look at this after Dave has reopend trunk. Regards, Mark de Wever aka Mordante/SkeletonCrew ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
Re: [Wesnoth-dev] Release of 1.4 and freezing svn for some hours and 1.4 policy
After 1.4 has been branched off, I would appreciate it if we could stop all check-ins to the trunk for several hours, to give me a chance to merge in the formula AI branch. David On Fri, 2008-02-29 at 12:30 +0100, Nils Kneuper wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi everybody! > Currently it looks like trunk is about as stable as it can get. There is some > more time left, basically for translators and artists to complete some stuff. > I > want to announce that I want to see svn froozen for the time that I do work on > creating the package and testing it. So that there is only exactly one extra > revision needed to fix any bugs that occur in my testing. My current plans are > (and I am sure to be able to follow these): > > * Start packaging and testing on Sunday, 2nd March at 2pm (gmt+1) > > So the deadline for commits is ~1pm at that day. The freeze will probably last > till about 8pm (gmt+1). In this timeframe there should be *no* commits, they > will not go into the tarball anyway and might just create problems if smaller > stuff occurs. The freeze will basically last until I declare 1.4 tagged (that > is > until you see the commit message for tags/1.4. As requested by esr I will then > leave 1.4 still as trunk for some more hours (maybe three or four hours) for > fixes that are small and have to get into both (stringfixes, tiny bugs, > whatever). > > So to sum things up in short: > > * deadline for 1.4.0 commits: Sunday, 2nd March, 1pm (gmt+1) > * trunk frozen + start of release stuff: Sunday, 2nd March, 2pm (gmt+1) > * trunk free for 1.4+1.5 commits (not branched off yet): Sunday, 2nd March, > 8pm > (gmt+1) > * branching off 1.4 to branches/1.4, trunk free for 1.5.0-svn commits: Sunday, > 2nd March, 11pm > > > Regarding what should be commited to 1.4 after 1.4 is tagged: > Please do not commit any new feature stuff in there. 1.4 is meant to be bugfix > and translation updates only. Yes, some new graphics are fine, but rewrites of > scenarios, adding features, changing maps, adding music and such should *not* > happen. The reason for this is that when eg adding one new piece of music in > the > music playlist all the games on the mp server will show as "remote scenarios" > (can currently be observed with 1.3.19+svn on the official server). In > general I > would like to see the size of the package not change too much, that is it will > increase due to translation updates, but that will basically be it. > I think such a policy is rather sensible and a good compromise. > > Regarding the first post 1.4 dev release: > > I plan to at least wait 6 weeks with this. That is to give you some time to > add > all your new and shining features in there, which are likely to break things. > I > know that 1.5.0 will probably be rather broken due to the new stuff... > > Cheers, > Nils Kneuper aka Ivanovic > > > PS: If you need any changes to these plans, if there are none, I will procede > with those plans. I will give status updates on IRC for the 1.4 release steps. > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHx+zvfFda9thizwURAo+hAJ9jxyH9YgSWmd4uAV1jc2PIjQWvQACgiCWe > BGdwcvYFMtsnaDuNcB4C3WU= > =6cBT > -END PGP SIGNATURE- > > ___ > Wesnoth-dev mailing list > Wesnoth-dev@gna.org > https://mail.gna.org/listinfo/wesnoth-dev ___ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
