From gbenson at redhat.com Fri Jun 1 07:41:57 2007 From: gbenson at redhat.com (Gary Benson) Date: Fri, 1 Jun 2007 08:41:57 +0100 Subject: making j2se more portable In-Reply-To: <465F0FAE.1020806@sun.com> References: <50be7b020705300934l258f6808te9f14e3576da3802@mail.gmail.com> <20070531073615.GA3856@redhat.com> <465F0FAE.1020806@sun.com> Message-ID: <20070601074157.GB4088@redhat.com> Phil Race wrote: > Gary Benson wrote: > > Pieter Libin wrote: > > > However, I think renaming the solaris directory into unix would > > > make a lot of sense. > > > > "posix" would probably be more correct. > > Not sure about that for a couple of reasons > > * The largest chunk of code in src/solaris is related to UI libs (eg > X11 etc) which is not in the scope of POSIX. I suspect the same goes > for a chunk of the rest. > > * Some versions of Windows are in fact POSIX compliant too Ok, maybe "posix" wouldn't be correct, but a lot of FLOSS projects use the term. I'm guessing it's to avoid trademark issues with the word "unix". Cheers, Gary From Phil.Race at Sun.COM Fri Jun 1 18:27:03 2007 From: Phil.Race at Sun.COM (Phil Race) Date: Fri, 01 Jun 2007 11:27:03 -0700 Subject: making j2se more portable In-Reply-To: <20070601074157.GB4088@redhat.com> References: <50be7b020705300934l258f6808te9f14e3576da3802@mail.gmail.com> <20070531073615.GA3856@redhat.com> <465F0FAE.1020806@sun.com> <20070601074157.GB4088@redhat.com> Message-ID: <466064F7.4020500@sun.com> > I'm guessing it's to avoid trademark issues with the word "unix". You are probably right but Posix is also a trademark. See http://standards.ieee.org/regauth/posix/index.html There's an ? after almost every one of the many uses of posix on that page, which suggests they are keen on reminding people. At least in the case of "solaris" Sun owns the trademark .. and hopefully we aren't likely to complain to ourselves. -phil. Gary Benson wrote: > Phil Race wrote: >> Gary Benson wrote: >>> Pieter Libin wrote: >>>> However, I think renaming the solaris directory into unix would >>>> make a lot of sense. >>> "posix" would probably be more correct. >> Not sure about that for a couple of reasons >> >> * The largest chunk of code in src/solaris is related to UI libs (eg >> X11 etc) which is not in the scope of POSIX. I suspect the same goes >> for a chunk of the rest. >> >> * Some versions of Windows are in fact POSIX compliant too > > Ok, maybe "posix" wouldn't be correct, but a lot of FLOSS projects use > the term. I'm guessing it's to avoid trademark issues with the word > "unix". > > Cheers, > Gary From Ray.Gans at Sun.COM Fri Jun 1 21:52:46 2007 From: Ray.Gans at Sun.COM (Ray Gans) Date: Fri, 01 Jun 2007 14:52:46 -0700 Subject: Project proposals In-Reply-To: <4656A086.2010006@sun.com> References: <20070524190709.D287884E3@eggemoggin.niobe.net> <4656A086.2010006@sun.com> Message-ID: Sorry about the late reply. I think we're in agreement Oleg. Perhaps the word "sponsorship" is the issue. I understand "group sponsorship" to mean that we, as members of Group XXX believe this project has (or could have) value and we expect -some- people who participate in our group's discussions and projects to have interest in this proposed project. Sponsorship does not mean all group participants (or even a significant number of them) will participate in the project. If a non- member wishes to start a project he/she must ask a group member to propose it. In my opinion, that group member needs only think the project is a good idea, but does not have to commit to participate in the project at all (although that would be nice). Certainly those who vote to approve sponsorship would not be expected to join the project. To be clear, code developed under a project will not necessarily get released as part of Sun's or anyone else's binary distributions -- but it will be available to OpenJDK participants. So I still think it should be a fairly low bar to sponsor a project. Group voting is good because it demonstrates some support for the project and will help to screen out projects that belong somewhere else or have little chance of getting any attention (e.g., Proposal: hey, let's start a project to do x-y-z and see if people want to work on it.... but then no one speaks up in pre-sponsorship discussions that shows any willingness to do so). -Ray On May 25, 2007, at 1:38 AM, Oleg Sukhodolsky wrote: > Ray Gans wrote: >> In my opinion, there should generally be a fairly low bar to jump >> over to get a project approved -- it should be relevant to OpenJDK >> of course (i.e., text editors, games, etc. belong somewhere else), >> but research is usually a good thing, even if the direction isn't >> necessarily the focus of the majority. Groups should sponsor >> projects that their memberships want associated with the group -- >> not because they think a project is worthy of being added to the >> main source distribution, but because the project is relevant to >> that group's focus area, or that it someday might be. I would >> expect that discussions about such projects could naturally occur >> on the group mailing lists and be of interest to some of the >> group's participants. > > Well, I agree that it should be easy to get approval for starting a > project. But I'd not expect any sponsorship with such approval. > If the project is not interesting for me, why I need to promise a > sponsorship. I'd prefer to say: "Well, I'm ok with such project, > but I will not help with it". IMHO, it will be better than say "we > sponsor your project" and does nothing for it after that. > > Thanks, Oleg. > > P.S. of course it depends on the definition of "sponsorship" term. > But I'd expect that this is a commitment to help with the project. > >> Groups of course have the ability to define the height of the >> acceptance bar because their members get to vote. If that bar is >> set too high, however, projects will be created somewhere else and >> not in OpenJDK -- which sometimes is appropriate -- but shouldn't >> occur so often that people feel unwelcome to participate. >> Hopefully, group members won't often propose projects that are >> really terrible ideas or inappropriate for a group. And while I >> certainly don't think we want to create a community of half-baked >> abandoned projects, I do believe we want to enable people who are >> excited about working together to solve problems or try out new >> directions. Disk space is cheap, ideas are not. >> -Ray From Jeff.Dinkins at Sun.COM Tue Jun 5 19:47:08 2007 From: Jeff.Dinkins at Sun.COM (Jeff Dinkins) Date: Tue, 05 Jun 2007 14:47:08 -0500 Subject: fbtoolkit discussion extension Message-ID: <16C1050C-CCDB-4CBD-BD70-5A424AA1C629@Sun.COM> As the AWT Group's Moderator I'd like to ask for a 1-week extension of the discussion period for the fbtoolkit proposal [1] so that the AWT Group can conduct a proper vote - we need a little more time to get an interim vote procedure written up. As Mark Reinhold likes to say, we have the airplane in the sky, but we're still attaching the wings. :-) thanks, jeff [1] http://mail.openjdk.java.net/pipermail/announce/2007-May/000001.html From mr at sun.com Wed Jun 6 04:42:02 2007 From: mr at sun.com (Mark Reinhold) Date: Tue, 05 Jun 2007 21:42:02 -0700 Subject: fbtoolkit discussion extension In-Reply-To: jeff.dinkins@sun.com; Tue, 05 Jun 2007 14:47:08 CDT; <16C1050C-CCDB-4CBD-BD70-5A424AA1C629@Sun.COM> Message-ID: <20070606044202.5045D6431@callebaut.niobe.net> > Date: Tue, 05 Jun 2007 14:47:08 -0500 > From: jeff.dinkins at sun.com > As the AWT Group's Moderator I'd like to ask for a 1-week extension > of the discussion period for the fbtoolkit proposal [1] so that the > AWT Group can conduct a proper vote - we need a little more time to > get an interim vote procedure written up. That sounds eminently reasonable to me. The proposal [1] is dated 13:01 PDT (= 20:01 UTC) on Wednesday, 23 May, so this change moves the end of the discussion period to the same time next Wednesday, 13 June. > As Mark Reinhold likes to > say, we have the airplane in the sky, but we're still attaching the > wings. :-) (Did I really say that?) - Mark [1] http://mail.openjdk.java.net/pipermail/announce/2007-May/000001.html From Konstantin.Voloshin at Sun.COM Sat Jun 9 18:15:43 2007 From: Konstantin.Voloshin at Sun.COM (Konstantin Voloshin) Date: Sat, 09 Jun 2007 22:15:43 +0400 Subject: CFV: Should we sponsor the fb-toolkit Project? In-Reply-To: <6D6F96D2-ADCD-43DF-9263-EA92446C95AA@Sun.com> References: <11FBA8E0-1E23-48DC-A9DC-3C498274EA36@Sun.com> <6D6F96D2-ADCD-43DF-9263-EA92446C95AA@Sun.com> Message-ID: <466AEE4F.8080109@sun.com> Vote: yes Though, I probably see this project from different point. Judging from my game development experience, virtually every game, including high-budget monsters like Half-Life 2, seem to every time invent a proprietary internal GUI logic. I mean UI, where the user can start new game, save/load, adjust options. That UI is very much alike "ordinary" UI (and also SWING). But it's usually considered a non-critical part, thus usually has a lot of inconveniences and incompletenesses. I think, we can invent some "pure" interface required by internal SWING-logic. And then, cut (abstract) SWING-logic from any native peculiarities. To be widely reused, and also to encourage use of Java :) AWT could then be split into 2 parts. One would provide native widgets support, and the other would implement that interface for SWING for supported operating systems. Some steps are already made in that direction (by having peers and toolkits), but I think OpenJDK can benefit from going there much further. P.S. Back to games, they usually don't want all power of SWING. So it would be nice, if they don't have to implement that SWING-interface completely. E.g. if they use only buttons and only with mouse, they should only have to implement drawing of rectangles and font-symbols, and provide mouse position. But these are issues for more detailed discussion. P.P.S. I saw some GUI-helpers bundled by Microsoft into some new version of DirectX. Can't tell for sure, but from the first glance, they seemed too heavy, clumsy, and monolithic. IMO, it could be nice, to compete, and provide clients with ease and flexibility of SWING also in this area. For free, and by improving OpenJDK code at the same time :) P.P.P.S. I also felt appropriate to CC this message to discuss at openjdk. Jeff Dinkins wrote: > > Tom Marble and Steph Meslin-Weber have proposed a framebuffer-based AWT > toolkit Project [1]. > > Should the AWT Group sponsor this Project? > > Please cast your vote by replying to this message with either > > Vote: yes > > or > > Vote: no > > as the first line of the message body. > > You may indicate the reason for your decision, if you wish, on subsequent > lines. This is optional and not required. > > Votes are due by midnight UTC this Tuesday, 12 June 2007, after which > time I'll tally the votes and post a summary to this list and to > discuss at openjdk.java.net. > > Only Members of the AWT Group are eligible to vote on this decision [2]. > > The current Members are: > > Artem Ananiev > Vyacheslav Baranov > Dmitry Cherepanov > Andrei Dmitriev > Denis Fokin > Yuri Nesterenko > Anthony Petrov > Oleg Sukhodolsky > Anton Tarasov > Alexey Utkin > Konstantin Voloshin > > thanks, > > jeff > > [1] http://mail.openjdk.java.net/pipermail/announce/2007-May/000001.html > [2] http://blogs.sun.com/mr/entry/cosmology > > From Jeff.Dinkins at Sun.COM Wed Jun 13 03:28:51 2007 From: Jeff.Dinkins at Sun.COM (Jeff Dinkins) Date: Tue, 12 Jun 2007 22:28:51 -0500 Subject: Vote results: AWT Group sponsorship of the fbtoolkit project PASSES (9:1) References: Message-ID: <8CF8CC20-DE69-4095-BC05-9C7E13B9E8A3@Sun.com> The proposal for the AWT Group to sponsor the creation of the fbtoolkit project [1] succeeds with 9 votes for and 1 vote against. In answer to the question "Should the AWT Group sponsor this Project?" the individual votes are: Artem Ananiev Yes Vyacheslav Baranov Yes Dmitry Cherepanov Yes Andrei Dmitriev Yes Denis Fokin Yes Anthony Petrov Yes Oleg Sukhodolsky No Anton Tarasov Yes Alexey Utkin Yes Konstantin Voloshin Yes [1] http://mail.openjdk.java.net/pipermail/announce/2007-May/000001.html From Joshua.Marinacci at Sun.COM Fri Jun 15 16:22:57 2007 From: Joshua.Marinacci at Sun.COM (Joshua Marinacci) Date: Fri, 15 Jun 2007 09:22:57 -0700 Subject: New Project approved: Framebuffer Toolkit (fbtoolkit) In-Reply-To: <20070614050431.789F96432@callebaut.niobe.net> References: <20070614050431.789F96432@callebaut.niobe.net> Message-ID: This is great news. I can't way to play with it. - Josh On Jun 13, 2007, at 10:04 PM, Mark Reinhold wrote: > Per the interim governance guidelines for Projects [1] I'm pleased to > announce the creation of the Framebuffer Toolkit Project [2,3] > following > the AWT Group's decision [4] to sponsor it. > > - Mark > > > [1] http://openjdk.java.net/projects/ > [2] http://mail.openjdk.java.net/pipermail/announce/2007-May/ > 000001.html > [3] http://openjdk.java.net/projects/fbtoolkit > [4] http://mail.openjdk.java.net/pipermail/discuss/2007-June/ > 000080.html - Blasting forth in three part harmony! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Vijayan.Jayaraman at Sun.COM Fri Jun 22 04:58:51 2007 From: Vijayan.Jayaraman at Sun.COM (Vijayan Jayaraman) Date: Thu, 21 Jun 2007 21:58:51 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <467B5513.30509@sun.com> References: <467B5513.30509@sun.com> Message-ID: <467B570B.1070901@Sun.COM> Is my script usefull?. Is that resolved your tag issue?. Vijayan. Xiomara Jayasena wrote: > > The OpenJDK source, Compiler source and Jtreg binary for the promoted > JavaSE 7 build b14 is available under the openjdk > https://openjdk.dev.java.net website under Source Code (direct link to > bundles: http://download.java.net/openjdk/jdk7 ) > > The OpenJDK sources are also available at the subversion repository > https://openjdk.dev.java.net/source/browse/openjdk > > Thanks, > -Xiomara > From mark at klomp.org Fri Jun 22 08:50:38 2007 From: mark at klomp.org (Mark Wielaard) Date: Fri, 22 Jun 2007 10:50:38 +0200 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <467B5513.30509@sun.com> References: <467B5513.30509@sun.com> Message-ID: <1182502239.6707.3.camel@dijkstra.wildebeest.org> Hi, On Thu, 2007-06-21 at 21:50 -0700, Xiomara Jayasena wrote: > The OpenJDK source, Compiler source and Jtreg binary for the promoted > JavaSE 7 build b14 is available under the openjdk > https://openjdk.dev.java.net website under Source Code (direct link to > bundles: http://download.java.net/openjdk/jdk7 ) Thanks. I found the following bug-list/changelog for the closedjdk: http://download.java.net/jdk7/changes/jdk7-b14.html I assume these are more or less the same as for openjdk? How often do you plan to push out these "promoted JavaSE7" builds? Is there a list like the above of issues being worked on for the next one? Cheers, Mark From Xiomara.Jayasena at Sun.COM Fri Jun 22 15:14:50 2007 From: Xiomara.Jayasena at Sun.COM (Xiomara Jayasena) Date: Fri, 22 Jun 2007 08:14:50 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <1182502239.6707.3.camel@dijkstra.wildebeest.org> References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> Message-ID: <467BE76A.5030408@sun.com> Mark Wielaard wrote: > Hi, > > On Thu, 2007-06-21 at 21:50 -0700, Xiomara Jayasena wrote: > >> The OpenJDK source, Compiler source and Jtreg binary for the promoted >> JavaSE 7 build b14 is available under the openjdk >> https://openjdk.dev.java.net website under Source Code (direct link to >> bundles: http://download.java.net/openjdk/jdk7 ) >> > > Thanks. I found the following bug-list/changelog for the closedjdk: > http://download.java.net/jdk7/changes/jdk7-b14.html > I assume these are more or less the same as for openjdk? > Yes it is. > How often do you plan to push out these "promoted JavaSE7" builds? > Bi-weekly for now and then after some time it will be weekly. > Is there a list like the above of issues being worked on for the next > one? > We have a tool to track changes and I think there is plans to make that available at some point. -Xiomara > Cheers, > > Mark > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Phil.Race at Sun.COM Fri Jun 22 17:09:45 2007 From: Phil.Race at Sun.COM (Phil Race) Date: Fri, 22 Jun 2007 10:09:45 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <1182502239.6707.3.camel@dijkstra.wildebeest.org> References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> Message-ID: <467C0259.9070606@sun.com> > Is there a list like the above of issues being worked on for the next one. The only place that information is maintained is the internal bug database and you'd have to query for bugs that were 'integrated' into, eg, b15. But that state occurs only as each group puts back its changes into the master workspace (still teamware). So its changing in real time, right up to the day that b15 happens. So in other words, even with access to that database, I couldn't tell you exactly what will be fixed in b15 until b15 is done, and as soon as its done, it will be pushed out, along with the list. -phil. Mark Wielaard wrote: > Hi, > > On Thu, 2007-06-21 at 21:50 -0700, Xiomara Jayasena wrote: >> The OpenJDK source, Compiler source and Jtreg binary for the promoted >> JavaSE 7 build b14 is available under the openjdk >> https://openjdk.dev.java.net website under Source Code (direct link to >> bundles: http://download.java.net/openjdk/jdk7 ) > > Thanks. I found the following bug-list/changelog for the closedjdk: > http://download.java.net/jdk7/changes/jdk7-b14.html > I assume these are more or less the same as for openjdk? > > How often do you plan to push out these "promoted JavaSE7" builds? > Is there a list like the above of issues being worked on for the next > one? > > Cheers, > > Mark > From Jonathan.Gibbons at Sun.COM Fri Jun 22 17:36:00 2007 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Fri, 22 Jun 2007 10:36:00 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <467C0259.9070606@sun.com> References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467C0259.9070606@sun.com> Message-ID: <467C0880.8010300@sun.com> Phil, You can do mildly better than that if you have access to the database, using the fields that describe which bugs have been fixed and made available, but not yet been integrated into the master. That at least would give you a preview of what's coming. -- Jon Phil Race wrote: > > > Is there a list like the above of issues being worked on for the > next one. > > The only place that information is maintained is the internal bug > database > and you'd have to query for bugs that were 'integrated' into, eg, b15. > But that state occurs only as each group puts back its changes into the > master workspace (still teamware). So its changing in real time, right > up to the day that b15 happens. > > So in other words, even with access to that database, I couldn't > tell you exactly what will be fixed in b15 until b15 is done, and > as soon as its done, it will be pushed out, along with the list. > > -phil. > > > Mark Wielaard wrote: >> Hi, >> >> On Thu, 2007-06-21 at 21:50 -0700, Xiomara Jayasena wrote: >>> The OpenJDK source, Compiler source and Jtreg binary for the >>> promoted JavaSE 7 build b14 is available under the openjdk >>> https://openjdk.dev.java.net website under Source Code (direct link >>> to bundles: http://download.java.net/openjdk/jdk7 ) >> >> Thanks. I found the following bug-list/changelog for the closedjdk: >> http://download.java.net/jdk7/changes/jdk7-b14.html >> I assume these are more or less the same as for openjdk? >> >> How often do you plan to push out these "promoted JavaSE7" builds? >> Is there a list like the above of issues being worked on for the next >> one? >> >> Cheers, >> >> Mark >> From Phil.Race at Sun.COM Fri Jun 22 17:43:27 2007 From: Phil.Race at Sun.COM (Phil Race) Date: Fri, 22 Jun 2007 10:43:27 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <467C0880.8010300@sun.com> References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467C0259.9070606@sun.com> <467C0880.8010300@sun.com> Message-ID: <467C0A3F.2000902@sun.com> Jonathan Gibbons wrote: > Phil, > > You can do mildly better than that if you have access to the database, > using the fields that describe which bugs have been fixed and made > available, but not yet been integrated into the master. That at least > would give you a preview of what's coming. But usually the build target in those 'fixed available' ones is the very non-specific 'beta' .. meaning it'll be integrated next time that teams integrates but which build is TBD. -phil. > > -- Jon > > > Phil Race wrote: >> >> > Is there a list like the above of issues being worked on for the >> next one. >> >> The only place that information is maintained is the internal bug >> database >> and you'd have to query for bugs that were 'integrated' into, eg, b15. >> But that state occurs only as each group puts back its changes into the >> master workspace (still teamware). So its changing in real time, right >> up to the day that b15 happens. >> >> So in other words, even with access to that database, I couldn't >> tell you exactly what will be fixed in b15 until b15 is done, and >> as soon as its done, it will be pushed out, along with the list. >> >> -phil. >> >> >> Mark Wielaard wrote: >>> Hi, >>> >>> On Thu, 2007-06-21 at 21:50 -0700, Xiomara Jayasena wrote: >>>> The OpenJDK source, Compiler source and Jtreg binary for the >>>> promoted JavaSE 7 build b14 is available under the openjdk >>>> https://openjdk.dev.java.net website under Source Code (direct link >>>> to bundles: http://download.java.net/openjdk/jdk7 ) >>> >>> Thanks. I found the following bug-list/changelog for the closedjdk: >>> http://download.java.net/jdk7/changes/jdk7-b14.html >>> I assume these are more or less the same as for openjdk? >>> >>> How often do you plan to push out these "promoted JavaSE7" builds? >>> Is there a list like the above of issues being worked on for the next >>> one? >>> >>> Cheers, >>> >>> Mark >>> > From Jonathan.Gibbons at Sun.COM Fri Jun 22 18:58:57 2007 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Fri, 22 Jun 2007 11:58:57 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <467C0A3F.2000902@sun.com> References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467C0259.9070606@sun.com> <467C0880.8010300@sun.com> <467C0A3F.2000902@sun.com> Message-ID: <467C1BF1.70600@sun.com> Phil, True, but anything which is Fix Available is likely to be of interest if you're interested in what bug fixes are coming your way soon. -- Jon Phil Race wrote: > > > Jonathan Gibbons wrote: >> Phil, >> >> You can do mildly better than that if you have access to the database, >> using the fields that describe which bugs have been fixed and made >> available, but not yet been integrated into the master. That at least >> would give you a preview of what's coming. > > But usually the build target in those 'fixed available' ones is the > very non-specific 'beta' .. meaning it'll be integrated next time > that teams integrates but which build is TBD. > > -phil. > >> >> -- Jon >> >> >> Phil Race wrote: >>> >>> > Is there a list like the above of issues being worked on for the >>> next one. >>> >>> The only place that information is maintained is the internal bug >>> database >>> and you'd have to query for bugs that were 'integrated' into, eg, b15. >>> But that state occurs only as each group puts back its changes into the >>> master workspace (still teamware). So its changing in real time, right >>> up to the day that b15 happens. >>> >>> So in other words, even with access to that database, I couldn't >>> tell you exactly what will be fixed in b15 until b15 is done, and >>> as soon as its done, it will be pushed out, along with the list. >>> >>> -phil. >>> >>> >>> Mark Wielaard wrote: >>>> Hi, >>>> >>>> On Thu, 2007-06-21 at 21:50 -0700, Xiomara Jayasena wrote: >>>>> The OpenJDK source, Compiler source and Jtreg binary for the >>>>> promoted JavaSE 7 build b14 is available under the openjdk >>>>> https://openjdk.dev.java.net website under Source Code (direct >>>>> link to bundles: http://download.java.net/openjdk/jdk7 ) >>>> >>>> Thanks. I found the following bug-list/changelog for the closedjdk: >>>> http://download.java.net/jdk7/changes/jdk7-b14.html >>>> I assume these are more or less the same as for openjdk? >>>> >>>> How often do you plan to push out these "promoted JavaSE7" builds? >>>> Is there a list like the above of issues being worked on for the next >>>> one? >>>> >>>> Cheers, >>>> >>>> Mark >>>> >> From dan at fabulich.com Fri Jun 22 19:17:11 2007 From: dan at fabulich.com (Dan Fabulich) Date: Fri, 22 Jun 2007 12:17:11 -0700 (Pacific Daylight Time) Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <467BE76A.5030408@sun.com> References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467BE76A.5030408@sun.com> Message-ID: The Windows binary plugs for build 14 still don't include t2k.lib, a critical missing file required to build on Windows. The t2k.lib bug remains open. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6555215 I know Kelly's working on this... Maybe I got too excited when I saw that a new build was available. :-) http://mail.openjdk.java.net/pipermail/build-dev/2007-June/000075.html Wouldn't it make sense at this point to just withdraw the Windows binary plugs until working plugs are available or become unnecessary? -Dan From Kelly.Ohair at Sun.COM Fri Jun 22 19:36:06 2007 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Fri, 22 Jun 2007 12:36:06 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467BE76A.5030408@sun.com> Message-ID: <467C24A6.1070908@sun.com> We ran into a legal snag for fixing this in Build 14. The changes were all ready, so it will be in Build 15 for sure. Sorry about that. -kto Dan Fabulich wrote: > > The Windows binary plugs for build 14 still don't include t2k.lib, a > critical missing file required to build on Windows. The t2k.lib bug > remains open. > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6555215 > > I know Kelly's working on this... Maybe I got too excited when I saw > that a new build was available. :-) > > http://mail.openjdk.java.net/pipermail/build-dev/2007-June/000075.html > > Wouldn't it make sense at this point to just withdraw the Windows binary > plugs until working plugs are available or become unnecessary? > > -Dan From dan at fabulich.com Fri Jun 22 19:40:36 2007 From: dan at fabulich.com (Dan Fabulich) Date: Fri, 22 Jun 2007 12:40:36 -0700 (Pacific Daylight Time) Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: <467C24A6.1070908@sun.com> References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467BE76A.5030408@sun.com> <467C24A6.1070908@sun.com> Message-ID: Kelly O'Hair wrote: > Dan Fabulich wrote: >> >> The Windows binary plugs for build 14 still don't include t2k.lib, a >> critical missing file required to build on Windows. The t2k.lib bug >> remains open. > We ran into a legal snag for fixing this in Build 14. The changes were > all ready, so it will be in Build 15 for sure. > Sorry about that. Thanks for your attention to this. Is Build 15 approximately another month away? -Dan From Xiomara.Jayasena at Sun.COM Fri Jun 22 21:13:03 2007 From: Xiomara.Jayasena at Sun.COM (Xiomara.Jayasena at Sun.COM) Date: Fri, 22 Jun 2007 14:13:03 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467BE76A.5030408@sun.com> <467C24A6.1070908@sun.com> Message-ID: <467C3B5F.50001@Sun.COM> It should be approximately a couple of weeks away. -Xiomara Dan Fabulich wrote: > Thanks for your attention to this. Is Build 15 approximately another > month away? > > -Dan From Kelly.Ohair at Sun.COM Fri Jun 22 22:34:17 2007 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Fri, 22 Jun 2007 15:34:17 -0700 Subject: JavaSE 7 build 14 is available at the openjdk.java.net website In-Reply-To: References: <467B5513.30509@sun.com> <1182502239.6707.3.camel@dijkstra.wildebeest.org> <467BE76A.5030408@sun.com> <467C24A6.1070908@sun.com> Message-ID: <467C4E69.9060602@sun.com> More like 2 weeks. -kto Dan Fabulich wrote: > Kelly O'Hair wrote: > >> Dan Fabulich wrote: >>> >>> The Windows binary plugs for build 14 still don't include t2k.lib, a >>> critical missing file required to build on Windows. The t2k.lib bug >>> remains open. >> We ran into a legal snag for fixing this in Build 14. The changes were >> all ready, so it will be in Build 15 for sure. >> Sorry about that. > > Thanks for your attention to this. Is Build 15 approximately another > month away? > > -Dan