Hi, First, sorry for being away since 2 months ;)
I'm happy we talk about this release. I can take a part of the work to release this version. As far as I know, I see from my humble point of view the following bug to close : - bug #10709 : submachine gun missiles fly through a ceiling - bug #10667 : Parachute does not handle correctly left and right arrow keys on remote computer If anyone have another wish ... Now, we can talk about the feature freeze, call for update translation and release. I propose to make a final 0.8 release for end of march. Regards, Yannig Le Thursday 28 February 2008 19:09:14 RCL, vous avez écrit : > Hi! > > Are there any critical show-stopper bugs in the current version? > > One of senior developers should probably take a role of release engineer, > so questions like the above one could be directly addressed to him/her :) > > I personally can build a binary package for FreeBSD (and nudge a > port-maintainer to update port, too). However, I think that Windows version > should be ready as soon as possible, because that's where the largest user > base come from. > > I agree with shortening release cycle, *BUT* some tagging and branching > should be used, so release is never built from "trunk" (code in beta4 is > actually way better tested than some code in the upcoming release and that > causes my concerns). > > Regards, > RCL > > On Thu, Feb 28, 2008 at 12:31 AM, Kurosu <[EMAIL PROTECTED]> wrote: > > Hi, > > > > after a discussion with gentildemon and yekcim (sorry it isn't public, > > but it's hard to note down things when you are face to face during a > > lunch), it seems to us that: > > 1) We should now prepare the final version > > 2) Switch to a less static release cycle, and rather use a 3 months > > schedule without version number (not sure about tagging some versions > > for the official distribution packages) > > > > So far, I think I'm not misrepresenting the opinion of any of the 3 > > aforementioned team members. > > > > Concerning 1), I won't lay out such a neat program as Drayan did, but I > > would like to ask other developers' opinion in order to reach a > > consensus. I don't expect much opposition that a vote would change > > anything in the result. > > > > I'll be personnaly away starting 5th of March, so there won't be win32 > > and probably MacIntel binary package before April. But that shouldn't > > stop the process which I would lay out as this: > > - determine the remaining tasks to finish, and do incorporate them into > > trunk (max one week?) > > - tag this, warn translators and packagers to test the tarball (max 2 > > weeks?) and merge their work > > - incorporate any bugfix found in the meantime (max 1 week) in > > particular from packagers > > - release > > > > This means a release at worst by end of March. > > > > Opinions? > > > > Best regards, > > -- > > Kurosu > > > > _______________________________________________ > > Wormux-dev mailing list > > Wormux-dev@gna.org > > https://mail.gna.org/listinfo/wormux-dev > > _______________________________________________ > Wormux-dev mailing list > Wormux-dev@gna.org > https://mail.gna.org/listinfo/wormux-dev _______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
