Kurosu a écrit : > Hi, > > RCL a écrit : > >> Whose decision is needed to release 0.8 and move on to the next version? :) >> > > So far, consensus has been the way in the past. So far, nobody expressed > any opinion, so I'd like more opinions. >
Well, usually, release are published when someone exporess the idea of publishing a release :) Kurosu is probably right, we are publishing beta from a too long time, but that was so difficult to stabilize the network code... So, I agree to publish 0.8 by the end of the month or middle of march. Just to remember, here are the steps we have followed in the past to release 0.8beta2: 1) create a branch 0.8beta2 2) ensure "make dist-bzip2" creates a valid archive (no missing .h files) 3) upload a pre-release archive for - the packager to test if everything is good - the translators 4) when nearly all translations are ok (some translators can be on hollydays or not interested in updating anymore the translation), create a release archive (Waiting between 2 weeks) 5) inform all packagers than we are ready to release 6) collect packages 7) update the website and release 0.8beta2 :) A step is missing between 4 and 5 : tag the branch. Before step 4, we must update and tests the index server. It's probably a good idea too, to ensure that "How to play" manual (in .pdf, generated with tools/help2pdf/ are included in the package). It is better of course if this documentation was previously updated to explain how to play a network game (how to host a game (forwarding port 3826), how to connect, ...) Regards, Matt (gentildemon) > However, most developpers will tell you it's fine to commit. So if you > have some stalled work, go ahead. I think you'd only need some asking if > you are modifying a core system (network, action handler, ...). And > that's not a rule but just common sense. :) > > Best regards, > _______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
