[annotator-dev] Branching v2.0.x

[Randall Leeds]

In the interest of moving forward toward Annotator v2 I've just forked the
current master branch to two branches: v1.2.x and v2.0.x.

I would like to propose that maintenance fixes only land on v1.2.x. We
should make a release there shortly with anything that's landed since the
last tag.

We should aim to land Nick's WIP branch on v2.0.x.

Kristof Csillag will follow up over the next few weeks with e-mails
proposing changes to v2.0.x that integrate work we've done at Hypothes.is
which may break backward compatibility.

In this way, we can continue to support the existing formats and ecosystem
and make rapid changes to v2.0.x, stabilizing over time until we feel we
can tag v2.0.0.

I wanted a way to start landing changes upstream without worrying about
v1.2.x compatibility. That way we don't have to land the WIP branch with
tons of other changes and call it v2.0.0 immediately. We can iterate to
v2.0.0 but things can be landed instead of staying on side branches
indefinitely.

Happy Annotating,
R
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/annotator-dev/attachments/20131029/7de95a21/attachment-0001.html>