Re: [general] milestones and roadmap (round 1 summary)
Geir Magnusson Jr wrote: I think this captures the input so far w/ a minimum of editorializing on my part for now :) let me know if anything was left off, or if there are new things to be added Thanks! A useful reminder :) One thing I can think of to be added is improved test coverage - I take it the coverage information at http://wiki.apache.org/harmony/Coverage_information is still being updated regularly? If so, it's a good indicator of where people can pick up jobs. Also I seem to remember us discussing splitting snapshots into JRE, JDK and HDK flavours. I think it received general agreement at the time - is this something worth adding to the snapshots category? Regards, Oliver General === - switch to java 5 - get some of the principal JDK tools in place - use system libraries, dynamically where appropriate - libz, libpng, libjpeg, liblcms, libicu*, etc. - modularity -- DRLVM - refine and document the internal interfaces and API such that one can substitute parts of VM (ex, can the MMTk activities be a first step?) -- classlib - is there opportunity for refactoring classlib natives to be more modular WRT portlib? Build/Test Framework - regular schedule for snapshots. Maybe every two weeks for now? -- classlib -- classlib + DRLVM -- classlib + classlib adapter + jchevm - Build/CI/test framework - Mark/IBM get us booted? -- make it easy for anyone to setup the CI infrastructure and report back to a website here - Performance -- measure baseline -- start looking for hotspots - Stability and reliability -- stress testing - application-driven advancement -- which apps work -- tool for users to generate missing classes reports for us - JCK -- acquire -- integrate - federated build -- agreement between parts on things like debug/release flag, structure of artifacts (model after classlib for now), common dependency pool where possible, etc Classlib - concurrency : integration of Doug Lea's java.util.concurrency package. -- Nathan is looking at it -- need support from DRLVM + JCHEVM - CORBA - yoko? - JMX -- Mark has MX4J in place -- need to see if we can host MX4J as separate distributable of the Harmony project - package completion roadmap Ports = - em64t platform support - ipf platform support - amd64 - linux/ppc64 - osx/intel - osx/ppc Community = - make things accessible to users - increase commmitter pool - get out of incubator -- I think it's too early now, and we aren't suffering being in here, so I'd prefer to drop this one... (p.s. I just got a osx/intel box, so I'm really hoping that port is easy...) - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Oliver Deakin IBM United Kingdom Limited - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [general] milestones and roadmap (round 1 summary)
Weldon Washburn wrote: On 7/6/06, Tim Ellison [EMAIL PROTECTED] wrote: Geir Magnusson Jr wrote: I think this captures the input so far w/ a minimum of editorializing on my part for now :) let me know if anything was left off, or if there are new things to be added I agree. It looks like a good start. It would be good to expand on some of these topics with specific tasks, then put them on the website so people can see what needs doing (and volunteer!) Good idea! Once the top level structure is in place, perhaps we can create multiple mailing lists that reflect the structure. With the volume of mail on harmony-dev, its very easy to overlook messages you are interested in. I'm against this for now because I still think it's too early, although we'll certainly do this in the future. For now, I think that we can do well if we're careful about prepending subject lines. geir - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [general] milestones and roadmap (round 1 summary)
Geir - looks accurate to me. A couple of comments in line: Geir Magnusson Jr wrote: I think this captures the input so far w/ a minimum of editorializing on my part for now :) let me know if anything was left off, or if there are new things to be added General === - switch to java 5 - get some of the principal JDK tools in place - use system libraries, dynamically where appropriate - libz, libpng, libjpeg, liblcms, libicu*, etc. - modularity -- DRLVM - refine and document the internal interfaces and API such that one can substitute parts of VM (ex, can the MMTk activities be a first step?) -- classlib - is there opportunity for refactoring classlib natives to be more modular WRT portlib? Build/Test Framework - regular schedule for snapshots. Maybe every two weeks for now? -- classlib -- classlib + DRLVM -- classlib + classlib adapter + jchevm - Build/CI/test framework - Mark/IBM get us booted? -- make it easy for anyone to setup the CI infrastructure and report back to a website here - Performance -- measure baseline -- start looking for hotspots - Stability and reliability -- stress testing - application-driven advancement -- which apps work -- tool for users to generate missing classes reports for us No I'm sure we have this. I wrote one (stand-alone and simple minded) which is still in JIRA (Hamony 165), then I believe that Mark wrote something more sophisticated later on. All we really need to do for identifying missing classes is for people to run their apps a few standard operations with java -verbose:class and capture the output. I volunteer to look at this if anyone wants to do it Or - you could look at Harmony 165 and tell me what needs to be improved - I'm afraid it's Perl though so you may have to learn a new language :-) - JCK -- acquire -- integrate - federated build -- agreement between parts on things like debug/release flag, structure of artifacts (model after classlib for now), common dependency pool where possible, etc Classlib - concurrency : integration of Doug Lea's java.util.concurrency package. -- Nathan is looking at it -- need support from DRLVM + JCHEVM - CORBA - yoko? - JMX -- Mark has MX4J in place -- need to see if we can host MX4J as separate distributable of the Harmony project - package completion roadmap Ports = - em64t platform support - ipf platform support - amd64 - linux/ppc64 - osx/intel - osx/ppc Community = - make things accessible to users - increase commmitter pool - get out of incubator -- I think it's too early now, and we aren't suffering being in here, so I'd prefer to drop this one... Well - yes. Too early now - but it's what we are all working towards isn't it? So what's the harm in stating it as a goal? (p.s. I just got a osx/intel box, so I'm really hoping that port is easy...) - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [general] milestones and roadmap (round 1 summary)
Geir Magnusson Jr wrote: I think this captures the input so far w/ a minimum of editorializing on my part for now :) let me know if anything was left off, or if there are new things to be added It would be good to expand on some of these topics with specific tasks, then put them on the website so people can see what needs doing (and volunteer!) snip Ports = - em64t platform support - ipf platform support - amd64 - linux/ppc64 - osx/intel - osx/ppc ...and more and more. Again, a plan of how we start to widen the platform coverage a factor at a time (add 64-bitness, little-endian-ness, weak memory model, non-ascii, ...) Community = - make things accessible to users - increase commmitter pool - get out of incubator -- I think it's too early now, and we aren't suffering being in here, so I'd prefer to drop this one... I don't see it as a case of 'suffering' or not, if we meet the criteria for graduation then we should go for it. Graduation means that our infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects and that the project is fully endorsed by the ASF -- they sound like things we should aim for. Regards, Tim -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[general] milestones and roadmap (round 1 summary)
I think this captures the input so far w/ a minimum of editorializing on my part for now :) let me know if anything was left off, or if there are new things to be added General === - switch to java 5 - get some of the principal JDK tools in place - use system libraries, dynamically where appropriate - libz, libpng, libjpeg, liblcms, libicu*, etc. - modularity -- DRLVM - refine and document the internal interfaces and API such that one can substitute parts of VM (ex, can the MMTk activities be a first step?) -- classlib - is there opportunity for refactoring classlib natives to be more modular WRT portlib? Build/Test Framework - regular schedule for snapshots. Maybe every two weeks for now? -- classlib -- classlib + DRLVM -- classlib + classlib adapter + jchevm - Build/CI/test framework - Mark/IBM get us booted? -- make it easy for anyone to setup the CI infrastructure and report back to a website here - Performance -- measure baseline -- start looking for hotspots - Stability and reliability -- stress testing - application-driven advancement -- which apps work -- tool for users to generate missing classes reports for us - JCK -- acquire -- integrate - federated build -- agreement between parts on things like debug/release flag, structure of artifacts (model after classlib for now), common dependency pool where possible, etc Classlib - concurrency : integration of Doug Lea's java.util.concurrency package. -- Nathan is looking at it -- need support from DRLVM + JCHEVM - CORBA - yoko? - JMX -- Mark has MX4J in place -- need to see if we can host MX4J as separate distributable of the Harmony project - package completion roadmap Ports = - em64t platform support - ipf platform support - amd64 - linux/ppc64 - osx/intel - osx/ppc Community = - make things accessible to users - increase commmitter pool - get out of incubator -- I think it's too early now, and we aren't suffering being in here, so I'd prefer to drop this one... (p.s. I just got a osx/intel box, so I'm really hoping that port is easy...) - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
