On 31.07.2012 17:52, pulkomandy wrote:
The purpose of alphas is getting new code some exposure and gathering user reports about it, so actually it couldbe a good idea to merge x86_64 in before the release.
Depends on when. There is no point in an alpha release of untested code. If you want to delay the release a few more months, then sure, that's a good idea.
However, it's been a year since the last release, and people want some more stable release to work on. Maybe we should make a DR (developer release) with stable things, and make another alpha with all the new changes merged in ?
We didn't manage to release an alpha in quite some time, and you want to add just another release to the mix?
I think as long as we try to make *alpha* releases stable, we will have trouble releasing anything. If we want to make stable releases, then call them DR or something similar that better represents what they actually are, and put everyone in the mindset for it.
I think you have a strange understanding of a release :-)There is no point in doing releases when what you release is untested crap. Doing releases is hard work, and we actually intended to learn from the alpha release process for the real thing.
If you want unstable, please just use the nightly images instead. Bye, Axel.