[loc-en-dev] status

Mon Dec 1 11:47:47 PST 2008

As I understand it (which is highly questionable), the 'gate' is put in
place so that any controls, such as enforcing ticket number/state
compliance, etc, can be done without breaking atomicity of commits.

Mercurial's model is: Commit first, verify later.  So, some change could be
committed, and then while the test is being run, another user could check
out the changes, merge, and commit an additional change.   If the first
check fails, Mercurial tries to say, 'oops, sorry it didn't work out' and
roll back the original change.

This is no longer possible if a derivative change is checked in.

Anyways, that's what I understood as to why a gate was used.

-Steven

  From:       "Douglas Felt" <dougfelt at gmail.com>                                       

  To:         locale-enhancement-dev at openjdk.java.net                                   

  Date:       12/01/2008 11:02 AM                                                       

  Subject:    status                                                                    

Hello all.  This is just a note to let folks know what the current status
is.

I've submitted my public key to openjdk.java.net and will soon
populate the locale-enhancement repository from the jdk repo.  We will
then be able to experiment with changes to it.

It's not clear to me whether I need to set up a 'gate' repository.  It
doesn't seem likely that anyone but us will be using this repository
and we ought to be able to manage with just the one.  If anyone knows
different, please let me know.

I know from past experience that Sun has a test runner that can be
used to run tests in the test directory.  Has this been made available
to users of openjdk so that we can run these tests?  We will want to
run the Locale tests at a minimum after any changes to the Locale
class.

Doug