Replies

True. But they had a complete halt, year before last, when MS complained that they were using MS code. So they had to audit every line, and do a major rewrite. They’re back on track now, just slow going.

They desperately need money and/or more programmers.

I'm glad you brought that up, it caused me to go back and re-read something I had only glanced over previously...

THIS Post:

Starting from version 0.3.3 we have aimed to move our release cycle to a 2 month period. There are various reasons for this, but the two which are key to this decision is a desire to keep the main development tree in a stable condition, and an effort to keep up the interests of the people who follow the project, by providing regular release builds to play with.

To explain the first one in a little more detail; one of the problems we were experiencing as a project was huge system regressions at release time. Our release cycle used to be around the 6 month mark and we were finding that after 6 months of heavy development, we would branch and start to test only to find regressions had appeared all over the operating system. A list of blockers was then generated and this could take a huge amount of time to clear, at which point developers were concentrating on trying to fix regressions and development came to a halt.

We stumbled across this post from Linus Torvalds which showed the linux kernel was experiencing the same problems we were having, and discusses the changes which worked for Linux.

We opted for a similar approach of shortening the release cycle, which is keeping our main trunk much more stable and means we can virtually release trunk ‘as is’ without the need for lengthy branch periods. It also means more releases from the project, which is hoped will raise awareness and interest in ReactOS.

So that should help to explain some things, also.