Open Source & Free  

Changes to 2017 Milestones and DST Hotfix

Changes to 2017 Milestones and DST Hotfix

Header Image

We released an important fix for an issue with daylight saving in north America (DST), if you are experiencing weird issues only on iOS that could be attributed to time problems then please send a new build to see if the fix works correctly. Our iOS VM code made some assumptions about DST which were apparently false. We chose to release it outside of our regular update schedule due to the significance of this issue.

Release Schedule

Due to the tight schedule of the bootcamp we’re postponing some of the previously announced to 2017 milestones so we won’t need to split our focus. The bootcamp ends on May 1st and might require some more effort after it completes and we don’t want to draw the attention from the release. Since our set of open issues is ridiculously large there is just no other way.

The 3.7 milestone was planned for May 9th. We’ve decided to postpone it to June 27th (a date I just randomly picked with no reason at all).

The 3.8 milestone was planned for October 4th, I’m not a fan of December releases and even November is problematic but I don’t want to slip the release into 2018 so we will go for November 14th as the new release date.

Our Activity During the Bootcamp

During the weeks of the bootcamp the blog won’t post updates unless there is something urgent that we need to communicate. We won’t do the standard Friday release either during those dates. Since the bootcamp is split in the middle we will have regular activity during the off week of the bootcamp.

Support which I usually handle will be split between employees with Steve taking most of the public support effort and the pro/enterprise support aliases. Things should function as usual for the most par however if you are one of the people who emails me directly instead of the support alias, or one of the people who doesn’t mention his pro/enterprise account in his email you might not get an answer.

So please make sure to include that information in support queries (in general not just now).


Leave a Reply