Juest | how much of 2.99.x has been backported to releases? | 00:39 |
---|---|---|
blast007 | I don't know if we backported any stuff after 2.4.0 | 00:41 |
Zehra | 2.4.x. was mostly a backport of a lot of 2.99x stuff which could work/run without issue. | 00:41 |
Zehra | I think most of it was documented in the differences in 2.x and 2.4.x | 00:42 |
blast007 | there were a lot of map features in 2.99 that we didn't backport | 00:43 |
Juest | they were not feasible? | 00:43 |
blast007 | it was more about being risky | 00:43 |
Juest | hurting the brand? | 00:44 |
blast007 | no | 00:44 |
Juest | well, performance or features, user acceptance? | 00:44 |
blast007 | we needed to get a new major release out, so we picked features we could backport that we knew we could get working | 00:44 |
Juest | ah i see | 00:44 |
blast007 | and we set more of a hard deadline, and if we didn't have something working by that point (or it wasn't at least close to working), we pulled it | 00:45 |
Juest | well, now with that out of the way perhaps we could focus on some of the other things that didnt make it? | 00:45 |
Juest | after completing current "pending" release | 00:45 |
blast007 | we need to do the same sort of thing with 2.5 - look at what's in there and decide if it's working, or can be made to work easily enough, and if not, maybe just pull the feature/change back out | 00:46 |
*** SpringTank is now away: No clients connected to this core right now. | 00:47 | |
Zehra | This is just me throwing around an idea... I know it is going to be a lot of planning to make it possible/viable... | 00:50 |
Zehra | But after the next major release... have builds available for "feature" testing and it just be a continually "unstable" version... if testing shows it to be good... implement it in a new "major" release. | 00:51 |
Zehra | Features get added in little by little, but the next major release should be stable regardless of when it's "released". | 00:52 |
Zehra | 6 months of "stability" testing per feature should be enough. 2 features per year and we run 5 years, we get around 10 ground breaking features per major release. | 00:53 |
*** SpringTank is back | 00:54 | |
*** SpringTank is now away: No clients connected to this core right now. | 01:13 | |
*** SpringTank is back | 01:14 | |
*** SpringTank is now away: No clients connected to this core right now. | 01:22 | |
*** SpringTank is back | 01:48 | |
*** spldart <spldart!~spldart@2601:2c7:4100:2cb0:3210:b3ff:fef0:93af> has quit IRC (Ping timeout: 268 seconds) | 01:49 | |
Juest | or maybe just have a "experiments" section built into DEVEL builds only | 02:13 |
Juest | a menu where you can toggle features that are work in progress | 02:13 |
*** SpringTank is now away: No clients connected to this core right now. | 02:14 | |
Zehra | Partly I am interested in what is BZFlag to be envisioned in the long run. | 02:24 |
*** SpringTank is back | 02:29 | |
*** Zehra <Zehra!~Yukari@user/yukari> has quit IRC (Quit: Leaving) | 03:16 | |
*** Agatha_ is now known as Agatha | 04:08 | |
*** SpringTank is now away: No clients connected to this core right now. | 05:27 | |
*** SpringTank is back | 05:44 | |
*** Flash_ <Flash_!~Flash@user/flash> has joined #bzflag | 06:38 | |
*** I_Died_Once <I_Died_Once!~I_Died_On@c-73-184-170-223.hsd1.ga.comcast.net> has quit IRC (Ping timeout: 276 seconds) | 06:41 | |
*** Flash <Flash!~Flash@user/flash> has quit IRC (Ping timeout: 268 seconds) | 06:42 | |
*** Sgeo <Sgeo!~Sgeo@user/sgeo> has quit IRC (Read error: Connection reset by peer) | 09:20 | |
*** FastLizard4 is back | 10:35 | |
*** SpringTank is now away: No clients connected to this core right now. | 10:35 | |
*** iamzim <iamzim!~iamzim@user/invaderzim> has joined #bzflag | 11:04 | |
*** spldart <spldart!~spldart@2601:2c7:4100:2cb0:3210:b3ff:fef0:93af> has joined #bzflag | 11:08 | |
*** FastLizard4 is now away: AWAY from keyboard | 11:09 | |
*** iamzim <iamzim!~iamzim@user/invaderzim> has left #bzflag | 11:19 | |
*** FastLizard4 is now away: GONE - Screen Detached and Disconnected from IRC (I'm probably asleep, at work, or doing something in real life) | 11:24 | |
*** SpringTank is back | 11:26 | |
*** I_Died_Once <I_Died_Once!~I_Died_On@c-73-184-170-223.hsd1.ga.comcast.net> has joined #bzflag | 12:42 | |
*** tupone <tupone!~tupone@gentoo/developer/tupone> has quit IRC (Quit: leaving) | 17:30 | |
*** tupone <tupone!~tupone@gentoo/developer/tupone> has joined #bzflag | 17:30 | |
*** SpringTank is now away: No clients connected to this core right now. | 17:39 | |
*** SpringTank is back | 17:39 | |
*** SpringTank is now away: No clients connected to this core right now. | 17:43 | |
*** SpringTank is back | 17:43 | |
*** ahs3- <ahs3-!~ahs3-@user/ahs3-> has quit IRC (Ping timeout: 268 seconds) | 19:04 | |
*** ahs3- <ahs3-!~ahs3-@098-121-003-221.res.spectrum.com> has joined #bzflag | 19:04 | |
*** FastLizard4 is back | 19:04 | |
*** ahs3- <ahs3-!~ahs3-@098-121-003-221.res.spectrum.com> has quit IRC (Ping timeout: 252 seconds) | 19:11 | |
*** ahs3- <ahs3-!~ahs3-@2603-6081-2802-32d4-ea08-636e-c573-194e.res6.spectrum.com> has joined #bzflag | 19:12 | |
*** FastLizard4 is now away: AWAY from keyboard | 19:19 | |
*** ahs3- <ahs3-!~ahs3-@2603-6081-2802-32d4-ea08-636e-c573-194e.res6.spectrum.com> has quit IRC (Ping timeout: 268 seconds) | 19:55 | |
*** ahs3- <ahs3-!~ahs3-@2603-6081-2802-32d4-51eb-827c-7d10-0965.res6.spectrum.com> has joined #bzflag | 19:55 | |
*** ahs3- <ahs3-!~ahs3-@2603-6081-2802-32d4-51eb-827c-7d10-0965.res6.spectrum.com> has quit IRC (Ping timeout: 246 seconds) | 20:15 | |
*** ahs3- <ahs3-!~ahs3-@2603-6081-2802-32d4-4206-302d-d8e5-a7ac.res6.spectrum.com> has joined #bzflag | 20:15 | |
*** Sgeo <Sgeo!~Sgeo@user/sgeo> has joined #bzflag | 21:04 | |
*** Cobra_Fast is now away: offline | 21:17 | |
*** Cobra_Fast is back | 21:17 | |
*** ahs3- <ahs3-!~ahs3-@2603-6081-2802-32d4-4206-302d-d8e5-a7ac.res6.spectrum.com> has quit IRC (Ping timeout: 245 seconds) | 22:31 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!