[ros-kernel] 0.2.2 RC2
Royce Mitchell III
royce3 at ev1.net
Sun Apr 25 20:13:04 CEST 2004
I agree, this sounds like too big a change since we're in code freeze
already. Even if we merged stuff that's directly copied from wine, they
may change some functionality we might currently be relying on. While
that scenario would be a change for the better, it's not something we
want to end up in the middle of while trying to get the release out.
Even though it sounds like an innocuous change, it could cause problems
( especially since we wouldn't be merging all the changes ).
These merges should be in HEAD and appear in 0.2.3, methinks.
Andrew Greenwood wrote:
> I think we should keep things as they are already and only merge
> changes after the release.
>
> We're about half a month overdue anyway...
>
>
> ----- Original Message -----
> *From:* Stephen Hodges <mailto:theteofscuba at hotmail.com>
> *To:* ReactOS Kernel List <mailto:ros-kernel at reactos.com>
> *Sent:* Sunday, April 25, 2004 11:35 PM
> *Subject:* [ros-kernel] 0.2.2 RC2
>
> Since a release is pending soon, and WINE has since made a new
> release on Apr 8, I'd like to synchronize any components that do
> not require heavy modification for testing. Does anybody have a
> list of which parts of ROS are directly copied from the wine
> source -without- modifications?
>
> ------------------------------------------------------------------------
> _______________________________________________
> Ros-kernel mailing list
> Ros-kernel at reactos.com
> http://reactos.com/mailman/listinfo/ros-kernel
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Ros-kernel mailing list
>Ros-kernel at reactos.com
>http://reactos.com/mailman/listinfo/ros-kernel
>
--
-------------------------
http://wecanstopspam.org/
More information about the Ros-kernel
mailing list