1. Get a good understanding of what features are left before we are feature complete on the OpenMW side.
2. Do a news post write-up on these features, and announce that once they are finished, we can enter a Beta phase. More on that below.
3. Share this news post around to try to rally development for the last handful of features we need.
In response to Zini:
Bug fixes are obviously needed before 1.0, but my view (which may be incorrect, please correct me if I am wrong) is that we only have a handful of features left to implement, and if we can clean those up, we can announce we are in Beta, and focus only on bug fixes and optimizations.Zini wrote:Low activity: We actually have quite a lot going on on the OpenCS side of things and we are still getting plenty of bug fixes. it is to be expected that things are slowing down on the OpenMW side of features. But of course the fact that scrawl is currently busy with other stuff contributes to this perception. I think he mentioned that he would be able to go full speed again at the beginning of December. I don't think we have a problem here that makes immediate action necessary.
I definitely understand this is a broad issue. But can we add it as a task on the tracker to be closed once these other issues are handled? We are all aware that it needs to be done, but it'd be nice to see it on the to-do list, and even nicer to be able to close it once we hit a certain threshold.Zini wrote:FPS optimisation: Too broad for an issue. The batching task will improve performance (though probably not much for vanilla Morrowind content) and then there is OGRE 2.0.
Which of these http://bugs.openmw.org/projects/openmw/ ... &group_by= are non-Morrowind features? That link filters only 0.34 and 1.0 version-tagged issues, so it should not include anything extra?Zini wrote:Non-Morrowind features: Not in favour of that. For most of these we would need a fully functional OpenCS first anyway.
The point of a Beta is this: it lets people know that we are feature complete, and it's a point where we formally call for testing. We've already been doing that, but a lot of people walk away when they see that this or that feature is not implemented. We're basically feature complete at this point, but if we can formally announce that we are feature complete, people will be more inclined to test. It also sets a milestone goal for us for getting everything implemented. It's like the "1.0" of development, after which only bug fixes and optimization happen. I think it'd be a good goal for the project, and gives us good direction as we try to slog through the last bit of work to get things done.
I think this is a really good idea, and I'm strongly advocating it! I can definitely carry the banner for this effort, but Zini I need your blessing. I don't want to be trying to run off and do something with development planning that you're not on board with. Basically right now I am just asking permission to organize development this way, and to be able to write up a post to that effect, and to post it. And if I do a write-up on the remaining features, I want to make sure I've got a definitive list...