On Sun, Jun 19, 2016 at 11:12 PM, John Ralls <jra...@ceridwen.us> wrote:
> Aaron, > > Actually it's worse than that. Store a transaction in the summer, then > look at it in the winter and it's the day before. > > The reason for not changing it to date-only now is file compatibility. A > newly stored file would have no time part, and that would fail to load in > 2.6.12. If we change it now to scrub to 1100Z (sailor/flyer/military for > 11:00AM UTC) then it will continue to load on older versions and will > magically not flip dates even on those older versions for all but the few > users in the time zones I mentioned at the start of the thread. This would > also be a good time to change the input code to not blow up if there's no > time part, but instead to set a timespec at 1100Z on the date indicated. > > Regards, > John Ralls > All that sounds good to me; in particular, the backwards compatibility story seems well-developed here. _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
