Jeroen van Meeuwen (Kolab Systems) wrote:
On 19.09.2011 17:26, Dave McMurtrie wrote:
Good day,


Hi Dave,

We've been tasked by our management with providing RSS support in Cyrus. Fortunately, the Cyrus httpd server that was recently developed makes
this much less onerous of a task.


Given the considerations of time(-limitations), I recognize this would need to be developed fast, and I recon that the work preferably be done based on a stable branch rather then a moving target -correct?

I would (greatly!) appreciate if any effort that could potentially destabilize the stable 2.4 branch did not go right into the designated branch for future stable 2.4 releases.

The current plan is this:

- I'm in the process of cherry-picking API additions from master that my current CalDAV code relies on. These are completely orthogonal to the existing code and don't change existing APIs so they shouldn't destabilize the code. I already have Bron's blessing on this.

- Once I have this in place, I will create a caldav-2.4 branch and backport everything from the caldav branch.


--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

Reply via email to