Only P1-P3 bugs fixes are allowed to push into jdk9 now

[Lindenmaier, Goetz]

Hi,

I think we need a bit relaxed rules for the ports because we often
lag behind a bit. So I only managed to implement the reserved stack 
zone recently.  Other features pushed short before the deadline might
need work in the ports we can only do once the main change is pushed.
We would like to deliver a VM that implements all the new features x86 
does on ppc and s390.  
But I think it can be considered a bug if a new feature is not 
implemented.

By the way, I think aarch does not yet implement the reserved stack zone
(JEP 270). 

Best regards,
  Goetz
 

> -----Original Message-----
> From: jdk9-dev [mailto:jdk9-dev-bounces at openjdk.java.net] On Behalf Of
> Andrew Haley
> Sent: Donnerstag, 5. Januar 2017 12:00
> To: jdk9-dev at openjdk.java.net
> Subject: Re: Only P1-P3 bugs fixes are allowed to push into jdk9 now
> 
> On 04/01/17 19:30, Vladimir Kozlov wrote:
> > On 1/4/17 2:23 AM, Volker Simonis wrote:
> >>
> >> Just for clarification: do the "Rampdown phase rules" also apply to
> >> non-Oracle platforms like ppc64 or s390x? In the past, we were allowed
> >> to push non P1-P3 bugs or enhancements even in later phases as long as
> >> they didn't touch shared code. Is this still allowed or do we now have
> >> to strictly conform to the process even for ppc64/s390x-only changes?
> >
> > JDK 9 schedule was approved by all, including Java Community outside
> Oracle.
> 
> My opinion is that we want the non-Oracle targets to be just as
> reliable as the Oracle ones, so it's not in the community's interest
> to relax the rules very much.
> 
> s390x is perhaps different in that it's very new, so might need a more
> flexible approach.
> 
> Andrew.