It is better to be able to get a list of known bugs in an app. Reassigning or closing the bugs would prevent a user from finding out that their specific version has a known bug.<br><br>Before I deploy an application, I should be able to tell what is wrong with it to see if there are any show stoppers. For example, if there is a fatal flaw in the ability to send emails and I require emails then I want to know before deployment.
<br><br>Ideally, the bug tracker has the ability to note that a bug exists in multiple versions and when it was fixed. In lieu of that, leave the bugs open and create a new bug for the next milestone that references the previous version. When the bug is fixed, note that in the previous bug so they know to move up to
5.1.0 or if it is a patch then mark it as fixed in 5.0.1.<br><br>In summary, if 5.0.0 has a bug then it always will have a bug. Anyone running 5.0.0 will need to know about the bug even if it is fixed in 5.0.1.<br><br>Regards,
<br>Tim<br><br>OnwealdTim<br><br><div><span class="gmail_quote">On 9/15/06, <b class="gmail_sendername">Allan Bush</b> <<a href="mailto:allan.bush+vtiger_dev@gmail.com">allan.bush+vtiger_dev@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Congratulations on the release.<br><br>I'm sure everyone deserves a couple days off now.<br>
<br>I hate to nag but a release should never occur when there are<br>outstanding bugs will a target milestone of the release version. All<br>these bugs: <a href="http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=new&status=assigned&status=reopened&milestone=5.0.0">
http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=new&status=assigned&status=reopened&milestone=5.0.0</a><br>should have been cleared off (either closed or had their milestone<br>bumped) before the 5.0 release. It looks a little unprofessional to
<br>create a release with so many known outstanding issues.<br><br>Also all open bugs with a version of 5.0-RC<br>(<a href="http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=new&status=assigned&status=reopened&version=5.0-RC&order=priority">
http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=new&status=assigned&status=reopened&version=5.0-RC&order=priority</a>)<br>should be reviewed against the 5.0 release now and either marked as<br>fixed or have their version bumped to
5.0.<br><br>Moving forward their should probably be 2 new targeted releases; 5.0.1<br>and 5.1.0. A 5.0 branch should be created and all bug fixes should be<br>applied to it for a 5.0.1 release. Meanwhile all new features should
<br>be added to the trunk code which will become the 5.1 release in time.<br>Bug fixes applied to the 5.0 branch should also be applied to the<br>trunk code when appropriate.<br><br>This is of course all my opinion and open to discussion.
<br><br><br>On 9/14/06, Dennis Grant <<a href="mailto:dgrant@accuratetechnologies.com">dgrant@accuratetechnologies.com</a>> wrote:<br>><br>><br>><br>><br>> Congrats!<br>><br>><br>><br>> And great timing too!
<br>><br>><br>><br>> Now, could someone with more Subversion experience than I explain how to<br>> pull this release out of svn and sync my changes against my local copy of<br>> RC1 against the new version?
<br>><br>><br>><br>> Tanks,<br>><br>><br>><br>> DG<br>><br>><br>><br>> ________________________________<br>><br>><br>> From: Richie [mailto:<a href="mailto:richie@vtiger.com">
richie@vtiger.com</a>]<br>> Sent: Thursday, September 14, 2006 9:21 AM<br>><br>> To: <a href="mailto:vtigercrm-developers@lists.vtigercrm.com">vtigercrm-developers@lists.vtigercrm.com</a><br>> Subject: [Vtigercrm-developers] vtigercrm5 released
<br>><br>><br>><br>><br>><br>><br>><br>> Hi!<br>><br>> vtigercrm5 has been released!<br>> <a href="https://sourceforge.net/project/showfiles.php?group_id=117522&package_id=203942">https://sourceforge.net/project/showfiles.php?group_id=117522&package_id=203942
</a><br>><br>> I take this opportunity to thank each one of you for<br>> the help, encouragement and support that<br>> you have<br>> provided to enable us to release it today.<br>><br>> This has been 'the' toughest release in vtiger's
<br>> short history and also the most useful and<br>> knowledgeable one.<br>> The core-team learnt a lot about<br>> community-building, making mistakes, using<br>> trac and svn, handling volatile<br>> emotions,etc. It has been a sort of
<br>> self-discovery actually.<br>><br>> At this point of time, I cannot help but be<br>> philosophical about the output.<br>> We have given our best we could in the given<br>> circumstances.<br>> The result is for all of you to decide upon.
<br>> Yes, we could have done more but then I am not sure<br>> if that would have made the release any<br>> better.<br>><br>> There comes a time when we have to let go and take<br>> a step back and observe.
<br>> I think this is the time.<br>><br>> Thank You for taking out some time to read this mail.<br>> I want all of you to know that we need you and we<br>> respect you.<br>> We will make mistakes in the future too but we are
<br>> willing to learn and adapt also.<br>> So, please bear with us.<br>><br>> Do let us know how you feel about the release.<br>><br>> Thanks once again,<br>> Richie<br>><br>> _______________________________________________
<br>> Get started with creating presentations online - <a href="http://zohoshow.com?vt">http://zohoshow.com?vt</a><br>><br>><br>_______________________________________________<br>Get started with creating presentations online -
<a href="http://zohoshow.com?vt">http://zohoshow.com?vt</a><br></blockquote></div><br>