Renegade
03.10.2010, 04:17:05
With only 9 "serious" issues left on 0.2's roadmap, we are slowly crawling towards 0.2's release, and therefore, inevitably, towards 0.3's development.
As mentioned multiple times before, 0.3 will start a new, accelerated development pace, in which we focus only on a handful of issues per version, in order to release each particular version as quickly as possible.
However, this poses a particular problem: All previous scheduling is void.
Everything currently on the roadmap after 0.2 is irrelevant. Scheduling starts over.
Undoubtedly, you are noticing a slight clash at this point: If all scheduling after 0.2 is void, and we're slowly crawling toward's 0.2's release...what the hell are we gonna do after that?
That is the question I would like to settle in this thread.
In the future, we'll likely have this kind of discussion on the tracker, largely based on ICS ratings and comments, however, since this is the first time, and the tracker is still arranged for the previous release model, that kind of wouldn't work out.
Parameters
Let's start with the basic framework: What do we have, and what are we looking for?
We currently have three "full time" developers (D, Alex and me), plus Marsh focused on #340. Since #340 is targeted for 1.0, and even if it weren't, it'd likely need an additional round of bugfixing after it was publicly released (it's quite complex), I'm assuming Marsh would be busy either way, even if he were, on principle, interested in tackling more issues. Thus, we'll be loading work on 3 developers only.
Now, what will we load onto these developers? 1 small feature and 1 big feature each, or, alternatively, 1 system - where "system" would be a conglomerate of multiple issues on the same topic. EMP would be such an example, or a collection of RMG improvements, things like that.
While selecting issues, always remember that those few feature requests are not the only things we'll work on. There are hundreds of bugs already in the system, and a public release of 0.2 will lead to a spike in new reports. These six issues will not be the only issues we work on - it will just be the only features.
So when you pick what you'd like, don't assume "oh well, if he's only gonna do one system anyway, I guess it doesn't matter if it's 6 issues big".
Unwritten features don't cause harm.
Bugs do.
Your selections will compete for attention and development time with necessary changes that we cannot ignore. Remember that when proposing your selections.
With that being said, you're pretty much free to choose from any unresolved issue on the tracker, including bugs, if you wish so.
That explicitly and emphatically includes all issues currently targeted for 0.3 and upwards.
Their targeting is void. The fact that they are currently still systematically targeted is irrelevant and has no meaning. The fact that an issue is currently targeted does not mean we plan on putting it in a future version.
I will purge these listings as soon as possible, but currently, that would lead to chaos on the tracker.
It would likely be wisest to start from the top of the Issue Community Support ranking, but you don't have to.
As usual, feel free to support your pick with arguments for or against yours or other issues.
Also keep in mind that certain issues have been postponed for a reason - while we will focus on what the community wants, shouting for fixed savegames in 0.3 is a futile exercise. It's just not gonna happen.
Proposing
Proposing a feature set is simple: Just do it. Pick up to six issues you'd like to see tackled in 0.3, and support them with arguments if you want to. Make sure to include the issue numbers, and make them bold, so we can easily find the features you want, and adhere to the parameters given above in terms of pairing.
If you underestimate the work a feature will require, we'll tell you quickly enough.
As said: On principle, you're free to choose from everything. We'll check where the community leans to, and we'll try our best to pick a feature set that will make as many of you as possible happy.
As usual, however, it's always possible that a feature simply doesn't find a developer, or that it's too complicated to implement at the moment. The mere fact that an issue has broad support will not guarantee its implementation.
With that all being said...go ahead and talk! What do you want to see targeted for Ares 0.3?
As mentioned multiple times before, 0.3 will start a new, accelerated development pace, in which we focus only on a handful of issues per version, in order to release each particular version as quickly as possible.
However, this poses a particular problem: All previous scheduling is void.
Everything currently on the roadmap after 0.2 is irrelevant. Scheduling starts over.
Undoubtedly, you are noticing a slight clash at this point: If all scheduling after 0.2 is void, and we're slowly crawling toward's 0.2's release...what the hell are we gonna do after that?
That is the question I would like to settle in this thread.
In the future, we'll likely have this kind of discussion on the tracker, largely based on ICS ratings and comments, however, since this is the first time, and the tracker is still arranged for the previous release model, that kind of wouldn't work out.
Parameters
Let's start with the basic framework: What do we have, and what are we looking for?
We currently have three "full time" developers (D, Alex and me), plus Marsh focused on #340. Since #340 is targeted for 1.0, and even if it weren't, it'd likely need an additional round of bugfixing after it was publicly released (it's quite complex), I'm assuming Marsh would be busy either way, even if he were, on principle, interested in tackling more issues. Thus, we'll be loading work on 3 developers only.
Now, what will we load onto these developers? 1 small feature and 1 big feature each, or, alternatively, 1 system - where "system" would be a conglomerate of multiple issues on the same topic. EMP would be such an example, or a collection of RMG improvements, things like that.
While selecting issues, always remember that those few feature requests are not the only things we'll work on. There are hundreds of bugs already in the system, and a public release of 0.2 will lead to a spike in new reports. These six issues will not be the only issues we work on - it will just be the only features.
So when you pick what you'd like, don't assume "oh well, if he's only gonna do one system anyway, I guess it doesn't matter if it's 6 issues big".
Unwritten features don't cause harm.
Bugs do.
Your selections will compete for attention and development time with necessary changes that we cannot ignore. Remember that when proposing your selections.
With that being said, you're pretty much free to choose from any unresolved issue on the tracker, including bugs, if you wish so.
That explicitly and emphatically includes all issues currently targeted for 0.3 and upwards.
Their targeting is void. The fact that they are currently still systematically targeted is irrelevant and has no meaning. The fact that an issue is currently targeted does not mean we plan on putting it in a future version.
I will purge these listings as soon as possible, but currently, that would lead to chaos on the tracker.
It would likely be wisest to start from the top of the Issue Community Support ranking, but you don't have to.
As usual, feel free to support your pick with arguments for or against yours or other issues.
Also keep in mind that certain issues have been postponed for a reason - while we will focus on what the community wants, shouting for fixed savegames in 0.3 is a futile exercise. It's just not gonna happen.
Proposing
Proposing a feature set is simple: Just do it. Pick up to six issues you'd like to see tackled in 0.3, and support them with arguments if you want to. Make sure to include the issue numbers, and make them bold, so we can easily find the features you want, and adhere to the parameters given above in terms of pairing.
If you underestimate the work a feature will require, we'll tell you quickly enough.
As said: On principle, you're free to choose from everything. We'll check where the community leans to, and we'll try our best to pick a feature set that will make as many of you as possible happy.
As usual, however, it's always possible that a feature simply doesn't find a developer, or that it's too complicated to implement at the moment. The mere fact that an issue has broad support will not guarantee its implementation.
With that all being said...go ahead and talk! What do you want to see targeted for Ares 0.3?
Forum Rules
(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!
(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.