I think, we are flexible. Kind of a guide value is one week. But if you tell us that there are important/useful patches to merge, there's no question about shifting the next release c for some days.
As I can remember, we had branch at wed to thursday. Thus RC2 would be this week we/th. However looking forward to easter (some of us live in christian areas), I'd rather make the branch after easter (monday or +1). This, because I suspect most of us to do not so much during easter.
Filip Navara wrote:
Robert Köpferl wrote:
Hi, I just finished uploading the RC1 to sf.net
The last build worked quite well, but improvements to the branch are welcome. If no major issues occour, we may perhaps advance to Release as next step, already.
I'm against that. I know it's a bit painful to prepare all the packages...but I have quite a few patches to merge from trunk and I would really appreciate having RC2 available for testing purposes. BTW, when is the deadline for patches on the 0.2.6 branch?
Regards, Filip _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev