Each project does schedules and planning differently - in the macosx-port right now, we have a lot of code that needs to move rapidly (without destabilizing the build) so we are carving off chunks and migrating them piece by piece. I don't really have any schedule guidance beyond "it's going to be busy this month" as we try to clear out everything in the "Partially done - on private branch" section of <http://wikis.sun.com/display/OpenJDK/Mac+OS+X+Port+Project+Status>. We are close to landing the Aqua Look and Feel, so look for that in the next day or two - but it will be broken in several key areas like Screen Menu Bar, or rendering system art, as we need to re-plumb the relationships between the Cocoa AWT and Aqua.
Regards, Mike Swingler Java Engineering Apple Inc. On Apr 5, 2011, at 3:29 AM, Henri Gomez wrote: > Thanks to you Mike also for your reply. > > The hard side for a non core developer or individual like me is to find infos > about roadmap or planning, for example to know when a given feature will be > implemented or backported from trunk to bsd-port, from bsd-port to mac-port. > > And also the large portions of code injected in HG in a single shot. > > > > Le 4 avr. 2011 à 21:30, Mike Swingler <swing...@apple.com> a écrit : > >> On Apr 4, 2011, at 11:39 AM, John Rose wrote: >> >>> P.S. I am intentionally not commenting, because I don't know the details, >>> of how Apple and Oracle and the community are dividing the work on bsd and >>> macos. All I know is that intelligent people are working on keeping it >>> sane and making it better. >> >> For right now, the macosx-port is generally merging upstream changes from >> the BSD port, since they are doing a great job of providing a stable branch >> off of the trunk. They fix up little issues that affect BSD and Darwin at >> the HotSpot and core-lib level that are different from Linux and Solaris - >> this allows us to focus on our hot mess of Objective-C code in the JDK. >> >> This means that the stock macosx-port is not going to be bleeding-edge for >> HotSpot or JDK features, but it's a stable base for us to port over the >> proprietary Apple Java SE 6 onto. >> >> Just an FYI as well, for the next month we probably won't ask for public >> code reviews of our changes, since we are largely porting chunks of our Java >> SE 6 implementation and we are trying to keep the process stream-lined. Once >> this initial bring-up period is over, we will switch over to a more >> traditional bug/review model of development, since most of the code from >> that point on will be new original content. >> >> Though, if you see any bugs that we need to be made aware of, please file >> them at: <http://java.net/jira/browse/MACOSX_PORT>! >> >> Thanks, >> Mike Swingler >> Java Engineering >> Apple Inc. >>
