<div>I wanted to clarify the perception difference that is being discussed on this thread. Please don't read me wrong - I'm certainly young compared to your expertise.</div><div><br></div><div>* Ondemand dev-team set the goals (every month) and focus</div>
<div>more on working on issues / features that can be rolled in the target cycle.</div><div><br></div><div>* Opensource dev-team set the goals in longer cycles as they collobrate</div><div>with Ondemand team changes + support customers bug-fixes + </div>
<div>community contributions + customizations + extensions.</div><div><br></div><div>Opensource product features match the Ondemand except they are few customization enabled for adapting the our billing system and service is enabled with round-the-clock support & IT team.</div>
<div><br></div><div>--</div><div>The practise of maintaing staging repository (instead of "hidden branch") has been their ever before ondemand started, the primary purpose was to eliminate the fear from young developers while committing the untested / validated code (and avoid loosing the changes!). The reviewed / validated code will be pushed to <a href="http://trac.vtiger.com">trac.vtiger.com</a> branches which need additional time.</div>
<div><br></div><div>--</div><div>vtiger6 development has been challenging with the agenda to </div><div>get the earlier version with least disruption to existing backend API</div><div>but yet enabled flexibity to provide adaptable UI (front end).</div>
<div><br></div><div>This had certainly raised the bars on dev-team who took few hard-bytes</div><div>refactoring the code very often and now settled with the better model.</div><div><br></div><div>Translation design / Module packages were the concepts that was </div>
<div>discussed few weeks back and is in process of implementation.</div><div><br></div><div>Which was the major reason to postpone commit to <a href="http://trac.vtiger.com">trac.vtiger.com</a> branch.</div><div><br></div>
<div>I appreciate your collaboration and look forward for greater assistance.</div><div><br></div><div>Regards,</div><div>Prasad</div><div>vtiger Team</div><div><br></div>On Friday, August 24, 2012, Joe Bordes <<a href="mailto:joe@tsolucio.com" target="_blank">joe@tsolucio.com</a>> wrote:<br>
> I couldn't have said it better :-)<br>><br>> Thanks<br>><br>><br>> On 24/08/12 14:51, Adam Heinz wrote:<br>>> On Fri, Aug 24, 2012 at 8:13 AM, Stefan Warnat <<a href="mailto:ich@stefanwarnat.de" target="_blank">ich@stefanwarnat.de</a>> wrote:<br>
>>> I think that it's no problem to wait, because vtiger is Open Source! It's<br>>>> not like commercial Software, you have pay for the functions.<br>>>> Nobody should expect any changes and be thankfull for every update you<br>
>>> become for FREE.<br>>> I don't think waiting is the problem. Joe's complaint reads to me<br>>> like, "Hey guys, why won't you let me help you sooner (by contributing<br>>> code and translations)!"<br>
>><br>>> So long as primary development is done in a hidden branch, community<br>>> contribution will always lag several months behind. My theory is that<br>>> they are trying to add value to their On Demand offering by delaying<br>
>> features into trunk, which is unfortunate for the development<br>>> community. I personally believe that that the contributions of<br>>> community developers already exceed that value. Even if vtiger<br>
>> doesn't want to open up the On Demand branch to the world, at least<br>>> give your translators and long-time community developers early access!<br>>> Joe has been a member of the community since 2006!<br>
>> _______________________________________________<br>>> <a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>><br>> _______________________________________________<br>> <a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>
>