On Tue, Dec 07, 2010 at 01:04:39PM +0100, Nils Kneuper wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi everybody! > This mail is about to short term and longer term plans. Lets start with short > term stuff: > > What do you think of releasing 1.9.3 tomorrow? Is the game currently in a > "stable enough" state or do you have any changes lying around that you > need/want > to incorporate? Please ping me if you have anything that should stop me from > releasing tomorrow.
I have nothing pending, not sure how stable it is at the moment. But nothing against 1.9.3. > Now the longer term plans: > > Beside this there is still the new lobby which is still not really 100% > usable. The fixes for this issue need some larger GUI2 changes, some already in a local branch, but still not entirely happy with that code, so might want to rewrite some parts. > In general I have the impression that we are not really ready to go into any > kind of feature freeze "soonish" enough to release in the timeframe of > February > to April (don't forget that eg translation teams need some significant string > freeze, I'd say that some 6 to 8 weeks would make sense as minimum!). I haven't had much time lately, but there are still some pending issues with GUI2 which I prefer to see fixed in the next stable. (I still hope to find more time for Wesnoth in the near future, but RL has been quite busy the last year.) > - - GUI2 is still in a "needs work and is just partly done" state. maybe when > allowing "large term changes" we have it finished in the next stable series? That most certainly not, I haven't started on the main UI yet and I don't expect to get to that any time soon, I have other GUI2 areas I like to finish first. > - - alink started to work on an OpenGL port of Wesnoth. Starting rather hacky > just > trying to 1:1 replace sdl functionality with OpenGL functionality where > required/useful. This work currently resides in an extra branch and is far > from > finished/polished. Maybe with a move cycle this work can be completed and > tested. That would be nice to get in the next stable. > What do you think regarding changing the release cycle to not release in the > timeframe Febuary-April 2011? Yes, personally I love the system "release > early, > release often". But getting out a new stable series does always require some > additional efforts that I currently think would be better spent in getting the > existing features into a state where we can say "done!". I'd love to hear from > you regarding the release plans. Personally I rather release when we're ready to release instead of at some fixed timeframe. Also the bugcounter seems to go up, so personally I like to get that one lower before the next release. > As you saw mentioned above GSoC is also somehow relevant to the release plans. > If we participate we need to allow students to commit stuff somehow. Since > those > are usually not tasks like "polish ABC" but more like "create some new > feature" > or "reimplement ABC in a sane way" they can basically not happen in mainline > during a feature freeze. And in case that the students vanish shortly after > GSoC > I would not like to have the work (that we could later on use) happen in an > extra branch that would be hell to merge back. The general question that came > to > my mind is: > > "Should we (try to) participate in GSoC 2011?" Not sure yet, but I think we should if we do it, we should try to find smaller tasks. I think we're a tend to overestimate what a student can do during GSoC. -- Regards, Mark de Wever aka Mordante/SkeletonCrew _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
