Closed Bertram25 closed 9 years ago
Once the release news is out, it'll be time to open a new discussion thread on OD forums for 0.6.0 :D It will be two releases done!
Not much to fill out on this one, yet...
Yeah, we'd better discuss this all on the forum to maybe also get feedback from players directly, and determine our roadmap for 0.6.0.
Yeah, we'd better discuss this all on the forum to maybe also get feedback from players directly, and determine our roadmap for 0.6.0.
Yeah, it's time to open a new topic about what we want for 0.6.0. If I could just release the win32 binary with all the deps before next month... XD
when will you open it? i have a few ideas
when will you open it? i have a few ideas
Sure: http://forum.freegamedev.net/viewtopic.php?f=35&t=6299
pinging also @oyvindln @Wout-van-Dongen @hwoarangmy @eugeneloza Hey, I've updated the 0.6.0 issue content to reflect the current effort. :)
This one is big and will be quite a good stuff to release. I'll also add an issue about the fact that the development branch game should now be 0.6.0 as there already are incompatible level changes.
Let's review the progress and iteration drifting in a month. :D
In the meanwhile, if you see anything to change, comment and so on. Feel free to do so. :)
There are more here than what I was expecting ^^ Let's try to do most of it.
Don't worry, we'll likely move the hurting pieces preventing from releasing as we want once we're at mid scope.
@akien-mga @hwoarangmy @Danimal696 Just for the small point of situation. What are your current short-term mid-term plan? Mine is to:
unless last minute change:
My current list:
A quick note: tuxfamily.org does not support CC-BY license (including OGA-BY), only CC-BY-SA. See: http://faq.tuxfamily.org/License/En . They have no statement about CC0, but it seems to be ok for them. It should be checked before moving to this hosting. Or contact them on IRC to re-check if they demand this deliberately or it's just a poorly written document 'cause GNU license guide they referr to supports CC-BY.
A quick note: tuxfamily.org does not support CC-BY license (including OGA-BY), only CC-BY-SA. See: http://faq.tuxfamily.org/License/En .
They say "We do accept other open licenses, feel free to join our irc channel if you have questions about a specific license." I think it's just a badly written document, as I don't see why they would accept GPL and BSD code (i.e. strong copyleft and almost public domain) but not CC-BY for artwork. I'm asking them on IRC to clarify.
Edit: Confirmed on IRC, they accept any CC license as long as it's not NC or ND, which seems pretty classic to me. As I understand it, the licenses that they list are recommendations for projects without license, but not strong enforcements for already licensed projects.
Perfect. Thanks for the heads up. :)
Note that we are already at 4 months from the start of 0.6.0 dev. Should we start moving to next version what won't be done in a near futur ?
@hwoarangmy
Should we start moving to next version what won't be done in a near futur ?
What have you got in mind? Or more precisely what do you think should be moved?
I would also add that we should all have a look at all the issues open and see whether there are points not clear about how to fix the issues. We never know, we may even have forgotten a few ones to close? ;)
What have you got in mind?
ATM, I've released a PR with library logic (obviously what I was on). So I guess we should move all non "critic" stuff to later and focus on what we are currently doing or what we really want for the 0.6.0. For my part, I've nothing to do unless you see something in my PR ^^
on what we are currently doing or what we really want for the 0.6.0.
Good for me. I'm always for smaller and saner scopes. ;) I'd like to see #590 #632 fixed as such details can be removed from the way once and for all, and #722 for usability purpose. (I'm fixing the settings as requested atm.) All the rest can move to 0.7 or 0.6.1 as you like, where I'll personally keep on with the GUI stuff. (bugs, skin + help @akien-mga with user maps support.) Why not focus on equipment for the next release, while @Danimal696 keeps on fixing the tileset?
Ah, while we're speaking of that kind of stuff. There is a bit of vision to discuss: For the next release or the one after that, shall we:
My own preference is the given order. Why? Because we still need a few stuff to complete the gameplay, such as gems, bridges, a room or two and a few more spells, but we are also mostly known to be multiplayer stable and permitting to let people join a masterserver could really help the project to be even better at that, before we move onto a completely different subject (The campaign) WDYT?
IMHO, the most missing right now is game content. ATM, the game is too repetitive. Building a hatchery + dormitory is enough to unlock almost everything. I think we should go for 2-3 specific rooms and a few spells to make the game fun ^^ Concerning points 2 and 3, I would also choose the same order because IMHO, the point of the whole project is to have a multiplayer game (otherwise, playing DK2 would be enough).
We're in line then. :)
@OpenDungeons/developers As we're in what could be called "integration" phase for 0.6.0, I'd propose this:
On the other hand, it would be a cool milestone if we could fix the tileset before that release, and I'd like to keep documentation to fix here, to make it happen before we move onto next topics. EDIT: Ah, And I'll try to make the skill button happen asap while I still have no eta.
WDYT?
First of all, I agree with the general vision outlines above (more game content first, then masterserver, then campaign).
For the 0.6.0 integration phase, I also agree with @Bertram25's points. I'll create issues for the remaining points that I want to fix before the release (create a new map, finish the move to TuxFamily, update the release notes).
As we're still working on core gameplay elements, I guess the level format will continue to evolve, so our next release will probably be a 0.7.0 and not a 0.6.1. If you agree, let's create the 0.7.0 milestone and start moving stuff to it.
As we're still working on core gameplay elements, I guess the level format will continue to evolve, so our next release will probably be a 0.7.0 and not a 0.6.1. If you agree, let's create the 0.7.0 milestone and start moving stuff to it.
Sure, I'll create the milestone now. :) Edit: Done: https://github.com/OpenDungeons/OpenDungeons/milestones/0.7.0
And I'll try to make the skill button happen asap while I still have no eta.
I havent heard about that, what is it about?
That's the button that displays a progressbar for researches
@Danimal696 @hwoarangmy Ok with my move proposal?
yes, go ahead
3 voices. Ok. I apply.
Ok with my move proposal?
It sounded like a summary, I didn't get that you were waiting an approvation ^^ But as I said, I am for finishing what we all are doing and releasing ASAP. IMO, the only "blocking" issue would be the water/lava animation (even if it is a big problem in my mind)
@hwoarangmy Eh eh. Did I sound that much like a dictator? XD There are at least one task left for each of us so hopefully you'll have a bit more time to finish what you will. :)
hwoarangmy i posted the models into the forum in case you didnt see my topic reply
@akien-mga Thanks for the wiki cleanups. We're mostly done on the communication part now. :)
For 7.0 release, please add Masterserver.
For 7.0 release, please add Masterserver.
I'll add it. Let's pray that someone bites it during that release. ;)
For 7.0 release, please add Masterserver.
You don't like our leading 0, do you? :p I think 0.7.0 is important to show that we are well aware that our game is not complete yet :)
We're getting close! :)
great news
I will upload a PR tonight with the last needed fixes. Once it will be reviewed/merged, the RC1 will be on its way ^^
I will upload a PR tonight with the last needed fixes. Once it will be reviewed/merged, the RC1 will be on its way ^^
Nice :) So once this PR is merged, I propose that we create the 0.6 branch from the development one, and use it as a basis for RC1. IMO we don't need to add a git tag for RC1, I think all our testers will use the precompiled binaries, and we don't really need to keep a tagged RC1 for the posterity (I'd even remove the existing 0.4.9-RC1 and 0.5.0-RC1 tags, but that's nit-picking, they don't hurt :p).
Left is adding the announcement and maybe a few balancing tweaks. RC1 is good to go before lans! :D
Sound and balancing tweaks in. Announcement draft done!
Nice! I think it's time to branch development into a new 0.6 branch, and that we create the RC1 binaries for wider testing. I'll do the Linux binaries in the evening or tomorrow.
Nice! I think it's time to branch development into a new 0.6 branch, and that we create the RC1 binaries for wider testing. I'll do the Linux binaries in the evening or tomorrow.
Ok, will do asap. Note that you guys have the access level to do it, in case you're tempted.
@Bertram25 We're going to play test 0.6.0 RC1 with @hwoarangmy tonight, if you're around ;)
FYI, I've pushed the 0.6 branch which is currently in sync with the development one. So we can start merging 0.7 stuff in development if you want ;)
@Bertram25 @akien-mga Could one of you try to launch a game with valgrind to check if we have memory problems ? I don't have a Linux computer to try but I think it would be good. The game will probably be (very) slow but if you could just open a level, let it play for some time and exit to check if everything goes well, it would be nice ^^
Here we go!! :D
General
Gameplay
Levels
Graphics
UI
Sounds
Documentation