title: Why does the first Joda DateTime instance gets a non-UTC Chronology?
body: <p><code>date1</code> and <code>date2</code> are not equal here because of the different Chronologies:</p>
  
  <pre><code>val formatter = ISODateTimeFormat.dateTimeNoMillis
  val date1 = formatter.parseDateTime("2012-01-03T00:00:00Z")
  val date2 = new DateTime(2012, 1, 3, 0, 0, DateTimeZone.UTC)
  println(date1.getChronology) // ISOChronology[Europe/Bucharest]
  println(date2.getChronology) // ISOChronology[UTC]
  assert(date1 === date2)      // fails
  </code></pre>
  
  <p>Here they're equal though:</p>
  
  <pre><code>val formatter = ISODateTimeFormat.dateTimeNoMillis
  val date1 = formatter.withZone(DateTimeZone.UTC).parseDateTime("2012-01-03T00:00:00Z")
  val date2 = new DateTime(2012, 1, 3, 0, 0, DateTimeZone.UTC)
  println(date1.getChronology) // ISOChronology[UTC]
  println(date2.getChronology) // ISOChronology[UTC]
  assert(date1 === date2)      // succeeds
  </code></pre>
  
  <p>I know <code>DateTime</code> instances should have same Chronologies in order to be treated as equal, but I would have expected that the Z designator in the string would make the formatter parse <code>date1</code> in the UTC Chronology. I'm pretty sure I'm confused on the difference between <code>Chronology</code> and <code>DateTimeZone</code>, so I'd really appreciate if someone can point it out what exactly is that I'm conflating.</p>
  
  <p>BTW, the code is in Scala and the assertions are from ScalaTest, but this shouldn't make any difference.</p>