Jelmer Vernooij

This is not backwards compatible, "bzr up" is a noop for "bzr branch" type clones. That's easy to address though, by adding a "bzr bind" command to convert from a...

> This is not backwards compatible, "bzr up" is a noop for "bzr branch" type clones. That's easy to address though, by adding a "bzr bind" command to convert from...

Hi @sbidoul , would you perhaps be able to help review this branch after the last changes or suggest a course of action? Thanks!

> > would you perhaps be able to help review this branch after the last changes or suggest a course of action? Thanks! > > Hi, I've had a look...

> > My changes are backwards compatible now > > I'm not sure. If you look at the `obtain` method in `versioncontrol.py`, it does `fetch_new` if the directory does not...

I've added a comment in the code explaining why it's calling "bzr bind".

Maybe the best approach here is to have a separate port for the metrics. That's consistent with what other web apps do - so you don't have your metrics exposed...

We need to expand rrules: * [ ] During regular filtering * [ ] When expanding for indexes, i.e. generate and store the full list of relevant timestamps You could...

I've done some work on this, and my draft branch does work but I'm not happy with it in its current form. It currently expands ics files when generating indexes,...

That all sounds quite reasonable to me.