[local-time-devel] merging the 1.0 branch

[Attila Lendvai]

Daniel,

from past experience (e.g. cffi) it creates major confusion if there's
a long standing branch where all development happens and this branch
is not the main one. recently i've started to see error reports due to
people using the old local-time.

what i propose is that we should record a tag in the old branch
(e.g. "before big refactor") and push the patches after it. people who
don't want the new stuff should simply not pull.

maybe we should be more user friendly, and switch the two branches
keeping a local-time-stable or local-time-old next to it for those who
have production code based on local-time and want to receive fixes to
the old codebase.

any thoughts?

-- 
 attila

ps: we are using local-time-1.0 without any trouble, although not in
our production codebase yet.