Emulator

Have you looked at the wiki?
http://code.google.com/p/dolphin-emu/wiki/TodoBeforeNextRelease

Yeah, I saw that after I registered the issue, but I still think of it as a little
vague. It's more of a To-do list, rather than a release plan.

speaking for myself, there are no milestones, due dates to fix certain bugs, or
anything like that. I go on emutime, which is like contractor time, but more
indefinite.
why is a release plan needed? It's not in my opinion.

at the moment release will just slow down development.
Release is good when you want islands of stability in development.
We are not in that stage yet...
what do you need releases for anyhow? Missing official binaries?

As a user, it would be nice to know when to expect some stability. That being said,
I'm not asking for a release in the immediate future.

It would simply be nice to see a list of the ongoing tasks, in organized in a
slightly better format. The Issue list has a feature which allows features to be
tied to milestones/releases. This would give users a good idea about progress, and
good information as to whether or not the current code base will build/run/function
well at the current moment. It's helpful to your users, and keeping people up to
date on the state of the project.

Currently, the only real way to do this is to check the code out and build it. I
don't know why current errors are there (is there a refactor happening, is the code
broken, is it an in-progress new feature?) since I don't know what might be happening
from a project standpoint.

Open-source projects are good practice grounds for all parts of project development,
not just writing code.

Open source projects are also a way to do things differently from what you do at your
day job as a pro dev :)

That said, we're thinking about going into feature freeze and pushing a release out.
We're probably not gonna devote much energy to setting up milestones and such, given
how hard it is to define meaningful ones in an emulator, other than specific features.

I think it would be a good Idea to push towards release when Wii support is a little
better. Aim towards the end of the year is my vote. If I get a vote that is :P

I also think end of this year sounds reasonable,
I think a month of feature freeze will be enough.

Let me see... It's possible to define milestones but they are pretty much useless
(i.e. Complete JIT emulation, complete Wiimote emulation, non-AX sound emulation,
perfect graphics emulation). As you can see, these are simply specific features which
may or may not be of priority.

ok so what's the status on this one?
should we just closed it?

Seems like you folks aren't interested, so feel free to close it. I was just hoping
for some better visibility into progress - neither the svn messages nor the wiki
entry tell me enough about where a feature is in terms of doneness.

You are right, but at this point everyone are just working on whatever they find
interesting at the moment. (makes sense when most of us are working to make their
favorite game work;). So there isn't much planing being done. We can define
milestones it's very unlikely someone will go by them :P
If you look at other projects such as xorg or even the linux kernel you'll see it's
very common. Most of them define milestones by what the developers are planing to
make until next release.
What we should do I think is to have official builds every week or two, with a short
change log. There are people willing to maintain it, but we are waiting for hrydgard
to decide when the time is right;)

The weekly builds sounds like a really good idea. Being unstable would be expected
and acceptable, but it would be nice to see that the project is still verifiable
buildable.

The TodoBeforeNextRelease seems to do the trick.

I vote for closing this.

What trick? people just randomly add things to there.
It became this bug annoys me list.
I doubt there will be any milestone or release anytime soon.