I completly agree with Brian.<br><br>Another problem is :<br>It seems that some people are using vtiger on Windows. Is there an easy and realiable system to patch vtiger on Windows ?<br><br>David V.<br><br><div><span class="gmail_quote">
2007/1/19, Brian Devendorf <<a href="mailto:developer@infointegrated.com">developer@infointegrated.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">Richie,<div><br></div><div>Patch releases may seem easier to manage, but they really become quite a bit more difficult. You will have to manage issues of which patches have been installed, or coming up with a mechanism to track patches. Then if some patches are replaced by other patches, you may need to come up with tools to revert the patches. From the support side of things, you will need to keep track of these patches independently. I think the problems are going to be very similar to the ones you saw when releasing dot releases a month apart.
<div><br></div><div>I understand that there are still many issues in vtiger that need patching, updating, and fixing. I'm sure you are noticing that there is a significant overhead to any type of release. What I mean by this is that you don't just decide to release and hit your Easy button. You've got testing, validation, documentation updates, staging, packaging, and more.
<div><br></div><div>Don't put more administrative work on your group than you need to. It reduces the effort you spend actually fixing and improving the product. And, it "cheapens" the product. When I see a product with many patch releases, I think, it's too bad they don't have better control of the quality of this product.
</div><div><br></div><div>Brian<div><br></div><div><br><div><div><span class="e" id="q_1103a8fc23e1ab2c_1"><div>On Jan 19, 2007, at 4:42 AM, richie wrote:</div><br></span></div><blockquote type="cite"><div><span class="e" id="q_1103a8fc23e1ab2c_3">
Hello!<br> <br> I would like to initiate the discussion on providing patch mode of release post the 5.0.3.<br> <br> Reason for patch mode of release post 5.0.3:-<br> <br> Much easier format of release.<br> Less pressure on team.
<br> Easy to identify the breakage segment(patch version that is)<br> Easier to rollback the patch if need be (ie we can always say that pl. do not use the patch and give a better one if need be. It is much easier to do).
<br> <br> I know that we have had a lot of debate about the release versionings and have arrived at the current one. But owing to the reasons mentioned above, I would like to have the convention flexible enough to allow patch releases too.
<br> <br> For this to happen, what all are the areas that ought to be taken into consideration.<br> <br> Fathi, Jeff ...?<br> <br> <b>Richie</b><br> <br></span></div><div style="margin: 0px;">_______________________________________________
</div><div style="margin: 0px;">Reach hundreds of potential candidates - <a href="http://jobs.vtiger.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://jobs.vtiger.com</a><span> </span></div>
</blockquote></div><br></div></div></div></div></div>
<br>_______________________________________________<br>Reach hundreds of potential candidates - <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://jobs.vtiger.com" target="_blank">http://jobs.vtiger.com
</a><br><br></blockquote></div><br>