Elmo/Meetings/2012-08-27

« previous meeting — index – next week » ^create?

Meeting Details

• Time and location: Monday, 10am PST, conf bridge 251
• irc.mozilla.org #elmo for back-channel

Previous Action Items

Meeting Notes

• Attendees: peterbe, laura, Pike, mathjazz
• UTC?

( http://stackoverflow.com/questions/10065190/migrating-mysql-datetime-fields-from-django-1-3-to-django-1-4 )

• • https://bugzilla.mozilla.org/show_bug.cgi?id=762536
    • peterbe action: obselete patch and make assumption that input datetime is UTC always
  • Where datetime.now() is used

http://www.hastebin.com/xeluqofaqo.avrasm

• • Can we use this?? https://docs.djangoproject.com/en/dev/ref/utils/#django.utils.timezone.make_aware
    • maybe not
    • (Challenge 1) We need a function that can convert datetime.datetime.now() to datetime.datetime.now().replace(tzinfo=UTC) WITH DST conversion done correctly.
    • (Challenge 2) Is it possible to just change the model instance value and hit save or do we need to change something inside MySQL??
  • Phase 1: UTC datetimes
  • Phase 2: timezone aware datetimes in models
    • Maybe we don't need this???
  • Plan:
    • 1) Change API to assuming UTC input (#762536)
    • 2) Migration and change of defaults to utcnow()
    • 3) Upgrade to Django 1.4
    • 4) Upgrade to timezone aware datetimes

Action Items