Alex committed the NDK today, so I went ahead and branched 0.3.0 at the previous revision. Aleskey and I decided that the NDK and CC patches can go in trunk whenever they are ready, for inclusion into 0.3.1. 0.3.0 is still in need of bugfixing and regression testing.
Therefore, we are going to leave the 0.3.0 branch open to development for a bit before we release RC1. Please discuss any large changes on the list before commiting to the branch. I don't care of the branch stays open for a month, as long as it's a good release in the end.
Thanks for all your hard work, WD -- ReactOS is a hub, follow the spokes and you'll immediately find absolutely everything you need to know about Windows. ReactOS is not just software, it's people. kjk_hyperion
What do you want to commit until feature freeze, people ?
Maarten Bosma
WaxDragon schrieb:
Alex committed the NDK today, so I went ahead and branched 0.3.0 at the previous revision. Aleskey and I decided that the NDK and CC patches can go in trunk whenever they are ready, for inclusion into 0.3.1. 0.3.0 is still in need of bugfixing and regression testing.
Therefore, we are going to leave the 0.3.0 branch open to development for a bit before we release RC1. Please discuss any large changes on the list before commiting to the branch. I don't care of the branch stays open for a month, as long as it's a good release in the end.
We need to sync with wine-0.9.12! Most of wine-shared components are still at 0.9.5 or even older.
Maarten Bosma wrote:
What do you want to commit until feature freeze, people ?
Maarten Bosma
WaxDragon schrieb:
Alex committed the NDK today, so I went ahead and branched 0.3.0 at the previous revision. Aleskey and I decided that the NDK and CC patches can go in trunk whenever they are ready, for inclusion into 0.3.1. 0.3.0 is still in need of bugfixing and regression testing.
Therefore, we are going to leave the 0.3.0 branch open to development for a bit before we release RC1. Please discuss any large changes on the list before commiting to the branch. I don't care of the branch stays open for a month, as long as it's a good release in the end.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Not really, I left shell32, some ole*, and something else in 0.9.5 state for a number of reasons, first of them being our IDL/WIDL/MIDL issue, when I can not sync .idl with Wine but have to actually compile their idl and insert .c/.h files to our tree - I don't have much experience to do that (maybe Saveliy or Eric or Ge help here if they have time).
As for shell32, 0.9.5->0.9.12 introduces some wine-specific changes which I again don't know how to deal with, and I didn't want to bug Thomas back that time.
If some of you wants to merge components which are left - please go ahead. Wine vendor import was done (some 10, some 12), so it's just the merge which is left. And main problem is merging 0.9.5->0.9.10, while 0.9.10-0.9.12 is quite easy due to not so big amount of changes.
WBR, Aleksey Bragin.
On May 11, 2006, at 12:21 AM, Maarten Bosma wrote:
Only those which have not been updated in later versions.
Saveliy Tretiakov wrote:
We need to sync with wine-0.9.12! Most of wine-shared components are still at 0.9.5 or even older.
Aleksey Bragin wrote:
Not really, I left shell32, some ole*, and something else in 0.9.5 state for a number of reasons, first of them being our IDL/WIDL/MIDL issue, when I can not sync .idl with Wine but have to actually compile their idl and insert .c/.h files to our tree - I don't have much experience to do that (maybe Saveliy or Eric or Ge help here if they have time).
I don't have time now because things in university become hard. I'll get back to work after exams will end. Eric told me some weeks ago that he almost finished widl sync and he is going to verify that ReactOS can be built successfully using wine-widl.