<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body >Hi!
<br>
<br>Be assured there are no impatient VCs breathing down our neck. It is just the way we work to get the features out fast and quick. You must accept that
<br>we have slowed down since quite some time ;-)!
<br>
<br>The only VC is me if anyone who is driving the things. So, I do take all the blame.
<br>I will have a look at Plone and respond to that point in leisure.
<br>
<br>I will also respond to the release cycle issue soon.
<br>
<br>Richie<br><br><br><br><br>---- Jeff Kowalczyk<jtk@yahoo.com> wrote ---- <br><br><blockquote style='border-left: 2px solid #0000FF; padding: 6px;'><html>
<xbody>
I'd like to make sure that the factors driving vtiger teams's decisions<br>are out in the open for the community's comment.<br><br>Sometimes there are big unannounced codebase changes, or dubious change<br>from alpha to beta status, etc. I'm sure I'm not alone in wondering how we<br>got from point A to point B sometimes. I'd like to think it's not some<br>dread meeting with impatient VCs that dictates features, release dates,<br>version numbering, etc.<br><br>There are many viable models for managing open source development in a<br>complex application. I've been a big fan of how Plone does it. See their<br>next semi-annual release for examples worthy of emulation:<br><br> <a href="http://plone.org/products/plone/releases/2.5">http://plone.org/products/plone/releases/2.5</a><br><br> - Features (PLIPs) proposed, vetted, implemented, merged. Persons owning<br>PLIP must maintain a branch for their PLIP.<br><br> - Releases scheduled (6 months), PLIPs proposed, dropped if not finished<br>on time.<br><br> - Prerelease version and maturity policies rigorously followed, live<br>migration from any (pre)release version forward is guaranteed.<br><br>We don't have to get too formal about it. A trac ticket is enough for an<br>improvement proposal (VTIP?), but I'd like to see everyone using trac to<br>the maximum benefit, expecially on their checkin messages.<br><br>IMO, We should adopt some of Plone's successful guidelines, and adapt the<br>parameters to our needs and vtigercrm's current maturity. I'd suggest<br>perhaps two 3-month timed releases, then move to a 6 month cycle in 2007.<br><br>_______________________________________________<br>This vtiger.com email is sponsored by: Zoho Writer. Are you still using your desktop word processor for typing documents? Try the AJAX enabled, collaboration-friendly online word processor, Zoho Writer for FREE instead!<br><a href="http://zohowriter.com/?vt">http://zohowriter.com/?vt</a> <br>
</xbody>
</html></blockquote></body></html>