Re: CS, CEL etc. 2.2 then 3.0
Matthieu Kraus <[email protected]> Wed, 23 Apr 2014 17:47:22 +0200
| Newsgroups | gmane.comp.graphics.crystalspace.devel |
|---|---|
| Message-ID | <[email protected]> |
-----Original Message----- From: Phil Wyett [mailto:[email protected]] Sent: Wednesday, April 23, 2014 10:59 To: [email protected] Subject: Re: [Crystal-develop] CS, CEL etc. 2.2 then 3.0 On Wed, 2014-04-23 at 09:44 +0100, Phil Wyett wrote: > Hi all, > > Below are some core proposals to discuss/argue about then vote on. > > === CS, CEL etc. 2.2 release === > > - Update bullet plugin(s) to be able to use 2.81. > - Continue support of Cg in 2.x series. > - Stabilise code base. > - Move bug tracking back to SF. We need to have solid tracking and > even give anonymous people ability to file them. Unless it is reported > we do not know. If we do not know we cannot fix. A bit of possible > spam we should be able to live with. > - Bring CSEditing into release cycle. > - Drop old move recorder. All fine by me, however I wouldn't exactly call it "support" for Cg - deprecate it already in 2.2 and make the support legacy only. There's no need to write Cg fallbacks given we want to drop it, anyway, and focus should be on porting the missing shader(snippet)s that are still Cg-only (clipping is most important, I think for fur and such there's also some missing). > > After branch for 2.2 is done... > > === CS, CEL etc. 3.0 release development. === > > - Drop Cg. Totally for it. > - Drop OSS audio. As pointed out we're using OpenAL, so use whatever OpenAL has available as backend - accordingly I'm not sure what you want to drop there tbh. If needed I can test it on BSD - I have a server running FreeBSD (running on an ARMv5 and a custom trunk, though) and can set up a VM if necessary. > - Re-enable Java. Not exactly sure that's a good idea tbh. Bindings easily get outdated and are rarely tested (at least judging from the issues people had with the python bindings in the past) which I doubt gets better with more to maintain. > - Drop old/unused platforms. Fine by me (although I'm not sure what exactly you have in mind there). > - Add Android support. That seems a bit too much for 3.0 imo, not sure what others think. > - Licenses audit. > - Audit, document, maintain as tier 1, 2 etc. elements of projects. > Improve tracking of project code, state, dependencies etc. > - Audit levels and data resources for licenses and usefulness. > - Review tutorials/test apps and change or add where appropriate. > - Remove unused older/bullet plugin. > - Drop ODE support. All fine by me. Kind regards, RlyDontKnow ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform