harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasily Levchenko" <vasily.v.levche...@gmail.com>
Subject Re: Releasing scheduling
Date Mon, 14 Apr 2008 04:55:32 GMT
On Mon, Apr 14, 2008 at 8:32 AM, Stepan Mishura <stepan.mishura@gmail.com>
wrote:

> Hi folks,
>
> As I understood the thread it is doable to make interim release
> targeted to assist inclusion of Harmony verifier to the nearest
> Eclipse TPTP release. Let me share my understanding of the request and
> a possible way to resolve it (please correct me if I'm wrong): The
> Eclipse team needs an 'official' (i.e. published on the web-site as
> milestone build) Harmony release. The Eclipse team only interesting in
> changes in verifier since M5 so the main criteria for the interim
> release is no regressions in verifier functionality (i.e. I assume
> that not critical regressions are acceptable for interim release. I
> believe that is important for having a shorten freeze/test/release
> period for the interim release)
>
> So I think we may consider:
> - making sure that all artifacts required are in place (i.e. committed
> to the trunk)
> - declaring short code freeze
> - running testing cycle to see if there are any issues with verifier
> and overall code.  (BTW, are there any know issues with verifier that
> needs to be fixed?)
>
> Having said that I thought that we are testing up to 6 snapshots per
> week so we may pick up any interim snapshot that has everything
> required and shows good testing results, make it 'official' - i.e.
> publish it ... with proper label - M5.5_Eclipse or something else to
> avoid confusions and to state clearly that the release it targeted to
> the Eclipse TPTP release.
>
> Does it make sense and works for all parties?
>
> The only issue that still unclear for me is ABI requirements: has the
> Harmony team build/test the code to satisfy ABI or you can do it?
> (Alexey Petrenko asked this before but I don't see any answer)


I suppose we can do it, but it should be in the released package too. If
we're going to share building of the module how it will looks like?
1. you'll give us revision
2. and we'll return the compiled libraries

or some other way?


>
>
> Thanks,
> Stepan.
>
> On 4/12/08, Vasily Levchenko <vasily.v.levchenko@gmail.com> wrote:
> > Hello folks,
> > Recently I and some Eclipse folks have finished prototyping java 6
> support
> > for Eclipse/TPTP project using Harmony verifier for recalculation stack
> map
> > tables after instrumentation, thanks to Mikhail Loenko to realize our
> > requirements to extend verifier functionality. Unfortunately extended
> > functionality wasn't included  in M5 release  of HDK, so we're in
> position
> > when we need some official snapshot (intermediate release), because of
> some
> > difference in releasing cycles between Eclipse and Harmony. Actually we
> have
> > less then couple of weeks to launch legal review for binary contribution
> of
> > Harmony verifier in Eclipse CVS.
> >
> > Additionally:
> > Eclipse have some ABI limitation for native code: Windows all code is
> > compiled with VC6, here I expect some incompatibility with Harmony
> binaries,
> > for Linux all sources are compiled gcc 2.96.
> > We're also interested that
> > https://issues.apache.org/jira/browse/HARMONY-5706 (introducing "C"
> > interface) will be on the trunk.
> >
> > So the question  is:  is it possible to make special unscheduled but
> > official release to meet Eclipse legal and ABI requirements?
> > --
> > --vvl
> >
>



-- 
--vvl

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message