Roadmap for OperaGame 2.0
Posted: Sat 29 Aug 2009, 03:41:21
Hi,
I thought about something some days ago... There is no real guidelines for the development of OperaGame. So I've searched how to do that, and thereby, I've made a roadmap for OperaGame 2.0. So let me explain it.
Firstly, it should be 3 releases before the final version of OperaGame 2.0 :
In fact, the first beta will be a version with the new OperaGame's structure but without new features. The second will correct bugs and regressions found in the previous beta plus new features which take advantage of the new structure. Then the release candidate will be logically a debugged v2.0b2 which will be renamed as v2.0 later if no major bug was found.
You couldn't take part of the first beta's development as each feature is already established in the latest v1.9. However, you can already make feature requests for the second beta, and you could report any bugs found for each future release, in the OperaGame's bugtracker. Feel free to suggest anything, besides no account is needed to make a new task! So it's very easy to do. After that, I'll approve it if it's realizable and it doesn't break the rules.
Also, you can follow the development in real time in the bugtracker as I update it as soon as possible. Note that I haven't yet filled it totally.
Finally, I don't know when the first beta will be release, probably not this week-end, but I hope that I'll be able to do it before mid-Septembre.
Anyway, more informations later. That's all, for the moment.
Updated on 2009-09-12 at 23:51:06.
Hi,
Some news since the previous message. It's nearly mid-september and I regret to inform you that it wouldn't be possible to release v2.0b1 this week.
OperaGame's core is practically finished as you can see it on the tasklist in the bugtracker. But it should take more time than expected to rewrite old OperaGame's features. There is more functions than I thought.
I hope that I'll be able to finish the core tonight...
Wait & see.
That's all, for the moment.
I thought about something some days ago... There is no real guidelines for the development of OperaGame. So I've searched how to do that, and thereby, I've made a roadmap for OperaGame 2.0. So let me explain it.
Firstly, it should be 3 releases before the final version of OperaGame 2.0 :
- The first will be called v2.0b1,
- The second v2.0b2,
- And the third v2.0rc1.
In fact, the first beta will be a version with the new OperaGame's structure but without new features. The second will correct bugs and regressions found in the previous beta plus new features which take advantage of the new structure. Then the release candidate will be logically a debugged v2.0b2 which will be renamed as v2.0 later if no major bug was found.
You couldn't take part of the first beta's development as each feature is already established in the latest v1.9. However, you can already make feature requests for the second beta, and you could report any bugs found for each future release, in the OperaGame's bugtracker. Feel free to suggest anything, besides no account is needed to make a new task! So it's very easy to do. After that, I'll approve it if it's realizable and it doesn't break the rules.
Also, you can follow the development in real time in the bugtracker as I update it as soon as possible. Note that I haven't yet filled it totally.
Finally, I don't know when the first beta will be release, probably not this week-end, but I hope that I'll be able to do it before mid-Septembre.
Anyway, more informations later. That's all, for the moment.
Updated on 2009-09-12 at 23:51:06.
Hi,
Some news since the previous message. It's nearly mid-september and I regret to inform you that it wouldn't be possible to release v2.0b1 this week.
OperaGame's core is practically finished as you can see it on the tasklist in the bugtracker. But it should take more time than expected to rewrite old OperaGame's features. There is more functions than I thought.
I hope that I'll be able to finish the core tonight...
Wait & see.
That's all, for the moment.