Hi, First, I would like to apologize for not stepping into this discussion earlier. I was not aware of the importance of having an "official" TPTP committer in this discussion. Vasily Levchenko is driving this effort from the TPTP side and is doing an excellent job in communicating our needs with regard to the Verifier work.
We were able to "relax" the legal process a little bit, and get approval to change the Harmony code "consumption" mode from "unmodified binary" to "unmodified source". Therefore, we do not need an "official binary package" from Harmony anymore, but we do need an "official source package". By this, I assume that a tagged SVN version corresponding to a milestone build is "official enough", and there is no need to provide a special link in the Harmony web site. I will verify this with Eclipse Legal. The review itself is actually quite simple: the code is scanned by an automated tool for 3rd-party dependencies, and since we know that there are no such dependencies, then it is safe to assume that we will get an approval (a major factor is that APL is compatible with the Eclipse Public License). Eclipse Legal is going out of their way to help us including this code into the upcoming Eclipse release (Ganymede). Their main requirement is that we submit the code of an "official" release (M5.5, M6 or whatever it is called now). The main reason behind this is that any change in the consumed code requires re-aproval from Eclipse Legal. Therefore, they like to get stable source code they can review once (and only once). The main issue we have is that we are running out of time. The original deadline for submission was April 25th, but after discussing this issue with the TPTP Project Management Committee (PMC), it seems that we still have a chance if we can submit the Harmony code for review before May 2nd (another extension may be possible but not likely). Just to reiterate (should be a well known fact already): the TPTP project is only interested in the source files required to build the verifier-ext library (vmcore/src/verifier-3363 and required include files). As far as I know, there are currently two open issues reported against these files: https://issues.apache.org/jira/browse/HARMONY-5794 : this is considered a BLOCKER by TPTP because we must be able to build the code on Linux. https://issues.apache.org/jira/browse/HARMONY-5764 : this is a MAJOR issue, but we may be able to work around it in TPTP (e.g., by changing instrumentation or excluding certain classes from instrumentation). If I understand correctly, code freeze for Harmony M5.5/M6 happens this week. Can anyone assess the chances of having the code ready for consumption by the end of this week? Thanks, Asaf ----- Original Message ---- From: Stepan Mishura <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, April 25, 2008 7:42:27 PM Subject: Re: [general] freeze for M5.5_Eclipse_TPTP On 4/25/08, Vasily Levchenko <[EMAIL PROTECTED]> wrote: > On Fri, Apr 25, 2008 at 2:26 PM, Stepan Mishura <[EMAIL PROTECTED]> > wrote: > > > On 4/25/08, Tim Ellison <[EMAIL PROTECTED]> wrote: > > <SNIP> > > > Let me make a concrete suggestion. > > > > > > We feature freeze today, and start a code freeze on Mon 28th April. > > > We can expect testing and bug fixing to continue for at least one week, > > > until Mon 5th May, then we have final vote and distribution probably > > taking > > > until Fri 9th May. > > > > > > > Wow, it is so easy! Tim, where you have been 2 weeks ago! :-) > > > > Well, I'm afraid it is too late for Eclipse but anyway ... hey, > > Eclipse folks if you are still reading this thread could you let us > > know if it works for you or not? > > > First of all I'm glad to say thank you for great work done to enable Harmony > technologies in Eclipse and understanding the significant of momentum. > > We need some binary package to be officially published on > harmony.apache.orgto meet Eclipse IPZilla requirements that revision > number has some official > status (like M5.5_Eclipse_TPTP). > I'm afraid we came to the initial point - the request to make "an officially released binary package". So I have to agree with Tim - this is not possible to make *any* "official release" right now. We tried to do our best to satisfy your request and did a several full testing cycles to test the verifier code. AFAIK all know verifier issues have been fixed in r651296 - you may take this revision for your evaluation if you wish. But it is not "officially released revision" - it has not gone through our formal release procedure. Thanks, Stepan. > Talking about M6, I've mentioned that we're very limited in time (end of > April). If we'll lost this opportunity we have to wait approximately one > year to start the process again. > > > > > > > Thanks, > > Stepan. > > > > > The dates need to be flexible so if we find problems we will, as always, > > > slip dates to get better quality. > > > > > > What do you think? A real M6, no arguments :-) > > > > > > Regards, > > > Tim > > > > > > > > > -- > --vvl > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
