I was just looking at this issue again because its causing trouble for a lot of our users. I noticed on the bug report for this on the issue list was updated to critical so I hope that means it will be fixed soon and we won't have to code a temporary work around. Does this status change mean you have an idea of when this will be fixed?
Regards,
Matt.
On Mar 14, 6:17 pm, "Ryan Boyd (Google)" <api.rb...@google.com> wrote:
Yes - I updated it to critical to reflect relative priority of this issue as I believe developers such as yourself see it (though I haven't gone through all bugs on the issue tracker and assigned priorities). The VTIMEZONE issue will be fixed in the next several weeks, but I don't have an exact date. Incidentally, the first Sunday in April is coming up soon, which will "fix" this issue as well for the time being. We also hope that the intermittent offset issue and intermittent parsing problems will be resolved at the same time as the deployment of the new VTIMEZONE definitions (though they are separate bugs).
Cheers, -Ryan
On Mar 22, 9:43 am, "Matt (GooSync)" <matt...@toffa.com> wrote:
> I was just looking at this issue again because its causing trouble for > a lot of our users. > I noticed on the bug report for this on the issue list was updated > to critical so I hope that means it will be fixed soon and we won't > have to code a temporary work around. > Does this status change mean you have an idea of when this will be > fixed?
> Regards,
> Matt.
> On Mar 14, 6:17 pm, "Ryan Boyd (Google)" <api.rb...@google.com> wrote:
> > Thanks for your post Matt.
> > Yes, we are aware of this issue and will update the VTIMEZONE > > definitions in the ical syntax as soon as possible.
> > Cheers,
> > -Ryan
> > On Mar 13, 8:51 am, "Matt (GooSync)" <matt...@toffa.com> wrote:
> > > In another post this has been mentioned so hopefully it can be > > > resolved quickly since the timezones have changed over already.
> > > On Mar 13, 1:24 pm, "Matt (GooSync)" <matt...@toffa.com> wrote:
> > > > Has Google Calendar been updated with the new timezone change because > > > > its seems to be an hour out when I extract recurring appointments?
|
