6821003 and 6821777 (support for Windows 7) hasn't been backported to hsx16

[Erik Trimble]

Volker Simonis wrote:
> 6821003 and 6821777 (support for Windows 7) which was backported to
> hsx14 hasn't been backported to hsx14 and I think this should be done.
>
> Is there a general mechanism in place to aussure thatt all changes
> which were integrated into hsx14 will also be in hsx16 (i.e. that
> hsx16 is a true superset of hsx14)?
>
> Regards,
> Volker
>
>   
This is a hard problem.  Here's why:

(1)  hsN is forked, and hsN+1 becomes the new development branch for JDK 7
(2)  hsN now becomes targeted at a JDK 6 / OpenJDK 6 release (and, most 
likely, several releases)
(3)  fixes for hsN are not automatically relevant to hsN+1,  as the fix 
may pertain to something that (a) is being replaced by something better 
in hsN+1  (b) doesn't occur in hsN+1 due to it being used with a 
different JDK version, or (c) breaks something in hsN+1 due to a 
different JDK version.

Basically, we're in version hell, as with all large projects.

The only way to "sync" is to do it manually - that is, for every fix 
made to a hsN, the developer must manually evaluate it as to it's 
relevance into hsN+M, and push the fix manually.  It's what we do 
internally at Sun.

Sorry, but I can't see any other way of doing this, except as you've 
noted:  look through the fixes, and forward port anything desired.


-- 
Erik Trimble
Java System Support
Mailstop:  usca22-123
Phone:  x17195
Santa Clara, CA