<!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 >I&nbsp;thought&nbsp;I&nbsp;had&nbsp;copied&nbsp;to&nbsp;the&nbsp;mailing&nbsp;list,&nbsp;yet&nbsp;to&nbsp;get&nbsp;it&nbsp;,&nbsp;so&nbsp;resending&nbsp;it.<br><br>Richie<br><br><br><br>============&nbsp;Forwarded&nbsp;Mail&nbsp;============<br>From&nbsp;:&nbsp;Richie&nbsp;&lt;richie@vtiger.com&gt;<br>To&nbsp;:&nbsp;fboudra@free.fr,vtigercrm-developers@lists.vtigercrm.com<br>Cc&nbsp;:&nbsp;vtigercrm-developers@lists.vtigercrm.com,gopals@vtiger.com<br>Date&nbsp;:Fri,&nbsp;8&nbsp;Sep&nbsp;2006&nbsp;03:58:36&nbsp;-0700<br>Subject&nbsp;:&nbsp;Re:&nbsp;[Vtigercrm-developers]&nbsp;naming&nbsp;conventions<br>============&nbsp;Forwarded&nbsp;Mail&nbsp;============<br><br>Team,&nbsp;<br>&nbsp;<br>This&nbsp;is&nbsp;yet&nbsp;another&nbsp;breakage&nbsp;from&nbsp;ourside&nbsp;which&nbsp;is&nbsp;not&nbsp;excusable.&nbsp;<br>Having&nbsp;a&nbsp;better&nbsp;control&nbsp;over&nbsp;GA&nbsp;release&nbsp;is&nbsp;as&nbsp;lame&nbsp;as&nbsp;any&nbsp;other&nbsp;excuses&nbsp;come&nbsp;by,&nbsp;it&nbsp;holds&nbsp;no&nbsp;water.&nbsp;<br>I&nbsp;sincerely&nbsp;regret&nbsp;this&nbsp;breakage.&nbsp;<br>&nbsp;<br>The&nbsp;core&nbsp;team&nbsp;is&nbsp;not&nbsp;excused&nbsp;of&nbsp;this&nbsp;fault.&nbsp;This&nbsp;will&nbsp;be&nbsp;made&nbsp;certain&nbsp;of.&nbsp;<br>Fathi,&nbsp;your&nbsp;anger&nbsp;is&nbsp;truly&nbsp;well&nbsp;justified.&nbsp;<br>Fathi,&nbsp;there&nbsp;is&nbsp;no&nbsp;restriction&nbsp;on&nbsp;speaking&nbsp;about&nbsp;reality.&nbsp;You&nbsp;are&nbsp;not&nbsp;seen&nbsp;by&nbsp;anyone&nbsp;<br>to&nbsp;be&nbsp;the&nbsp;bad&nbsp;guy.&nbsp;<br>&nbsp;<br>I&nbsp;am&nbsp;the&nbsp;bad&nbsp;guy&nbsp;if&nbsp;at&nbsp;all&nbsp;anyone&nbsp;can&nbsp;be&nbsp;called&nbsp;that.&nbsp;<br>It&nbsp;is&nbsp;my&nbsp;responsibility&nbsp;and&nbsp;I&nbsp;failed&nbsp;in&nbsp;it.&nbsp;<br>&nbsp;<br>From&nbsp;here&nbsp;on,&nbsp;Fathi&nbsp;will&nbsp;be&nbsp;consulted&nbsp;before&nbsp;we&nbsp;have&nbsp;a&nbsp;release.&nbsp;He&nbsp;will&nbsp;be&nbsp;the&nbsp;defacto&nbsp;<br>namer&nbsp;of&nbsp;the&nbsp;release&nbsp;in&nbsp;other&nbsp;words.&nbsp;<br>Yes,&nbsp;you&nbsp;could&nbsp;say&nbsp;that&nbsp;we&nbsp;had&nbsp;do&nbsp;better&nbsp;to&nbsp;read&nbsp;the&nbsp;release&nbsp;document&nbsp;but&nbsp;I&nbsp;would&nbsp;respectfully&nbsp;<br>&nbsp;disagree&nbsp;as&nbsp;if&nbsp;we&nbsp;had&nbsp;made&nbsp;sense&nbsp;of&nbsp;the&nbsp;naming&nbsp;convention,&nbsp;we&nbsp;would&nbsp;have&nbsp;fixed&nbsp;ourselves&nbsp;by&nbsp;now.&nbsp;<br>&nbsp;But,&nbsp;as&nbsp;we&nbsp;all&nbsp;see,&nbsp;we&nbsp;have&nbsp;conveniently&nbsp;disregarded&nbsp;the&nbsp;convention&nbsp;causing&nbsp;much&nbsp;consternation.&nbsp;<br>Let&nbsp;this&nbsp;be&nbsp;the&nbsp;immediate&nbsp;punishment&nbsp;till&nbsp;Fathi&nbsp;feels&nbsp;that&nbsp;we&nbsp;are&nbsp;good&nbsp;enough&nbsp;to&nbsp;<br>name&nbsp;the&nbsp;releases&nbsp;properly&nbsp;and&nbsp;lets&nbsp;us&nbsp;act&nbsp;independently.&nbsp;<br>&nbsp;<br>Remco,&nbsp;I&nbsp;can&nbsp;understand&nbsp;your&nbsp;chagrin&nbsp;too.&nbsp;<br>I&nbsp;am&nbsp;pained&nbsp;and&nbsp;there&nbsp;is&nbsp;no&nbsp;excuse.&nbsp;<br>I&nbsp;have&nbsp;mentioned&nbsp;the&nbsp;punishment&nbsp;to&nbsp;be&nbsp;put&nbsp;into&nbsp;effect&nbsp;immediately&nbsp;till&nbsp;we&nbsp;earn&nbsp;our&nbsp;'naming&nbsp;laurel'.&nbsp;<br>&nbsp;<br>Let&nbsp;me&nbsp;assure&nbsp;you,&nbsp;the&nbsp;core&nbsp;team&nbsp;does&nbsp;not&nbsp;believe&nbsp;in&nbsp;1&nbsp;man&nbsp;shows.&nbsp;This&nbsp;is&nbsp;a&nbsp;team&nbsp;effort&nbsp;and&nbsp;your&nbsp;views&nbsp;<br>are&nbsp;important.&nbsp;<br>&nbsp;<br>Richie<br><br><br><br><br>----&nbsp;Fathi&nbsp;Boudra&lt;fboudra@free.fr&gt;&nbsp;wrote&nbsp;----&nbsp;<br><br>&nbsp;&nbsp;hi&nbsp;gopal,<br><br>&gt;&nbsp;My&nbsp;only&nbsp;intention&nbsp;was&nbsp;to&nbsp;get&nbsp;more&nbsp;feedback&nbsp;from&nbsp;our&nbsp;developer&nbsp;community,&nbsp;so<br>&gt;&nbsp;that&nbsp;we&nbsp;can&nbsp;have&nbsp;a&nbsp;better&nbsp;control&nbsp;over&nbsp;GA&nbsp;release.<br><br>Could&nbsp;you&nbsp;explain&nbsp;me,&nbsp;how&nbsp;not&nbsp;respecting&nbsp;naming&nbsp;conventions&nbsp;help&nbsp;you&nbsp;to&nbsp;have&nbsp;a&nbsp;<br>better&nbsp;control&nbsp;over&nbsp;GA&nbsp;release&nbsp;?<br><br>&gt;&nbsp;So&nbsp;far&nbsp;we&nbsp;have&nbsp;gathered&nbsp;about&nbsp;100&nbsp;issues&nbsp;from&nbsp;our&nbsp;community,&nbsp;which&nbsp;may&nbsp;not<br>&gt;&nbsp;be&nbsp;possible&nbsp;with&nbsp;our&nbsp;core&nbsp;team&nbsp;in&nbsp;India.&nbsp;<br><br>and&nbsp;?&nbsp;is&nbsp;it&nbsp;a&nbsp;way&nbsp;to&nbsp;tell&nbsp;that&nbsp;core&nbsp;team&nbsp;do&nbsp;what&nbsp;they&nbsp;want&nbsp;?&nbsp;I&nbsp;don't&nbsp;<br>understand&nbsp;what&nbsp;you&nbsp;mean&nbsp;or&nbsp;maybe&nbsp;you&nbsp;must&nbsp;clearly&nbsp;rewrite&nbsp;your&nbsp;sentence.<br><br>&gt;&nbsp;I&nbsp;apologize&nbsp;for&nbsp;breaking&nbsp;the&nbsp;release&nbsp;management&nbsp;process&nbsp;this&nbsp;time.<br>&gt;&nbsp;Thanks&nbsp;for&nbsp;your&nbsp;understanding,<br><br>Sorry,&nbsp;i&nbsp;don't&nbsp;understand.&nbsp;Respecting&nbsp;naming&nbsp;conventions&nbsp;is&nbsp;a&nbsp;basic&nbsp;request&nbsp;<br>for&nbsp;release&nbsp;management&nbsp;that&nbsp;has&nbsp;been&nbsp;requested&nbsp;the&nbsp;first&nbsp;time&nbsp;in&nbsp;<br>ferbruary/march.&nbsp;your&nbsp;decision&nbsp;to&nbsp;not&nbsp;follow&nbsp;it&nbsp;cannot&nbsp;be&nbsp;justified&nbsp;by&nbsp;your&nbsp;<br>explanation&nbsp;which&nbsp;is&nbsp;far&nbsp;from&nbsp;credible.<br><br>My&nbsp;apologies&nbsp;to&nbsp;be&nbsp;again&nbsp;the&nbsp;bad&nbsp;guy&nbsp;who&nbsp;talk&nbsp;about&nbsp;the&nbsp;reality.<br><br>cheers,<br><br>Fathi<br><br>PS:&nbsp;and&nbsp;i&nbsp;don't&nbsp;talk&nbsp;about&nbsp;your&nbsp;licensing&nbsp;issue&nbsp;this&nbsp;time&nbsp;...<br>_______________________________________________<br>Get&nbsp;started&nbsp;with&nbsp;creating&nbsp;presentations&nbsp;online&nbsp;-&nbsp;http://zohoshow.com?vt<br></body></html>