[Vtigercrm-developers] vtigercrm-developers Digest, Vol 137, Issue 1 DEV Instance

TimeZone bernard.bailey at timezone.co.nz
Thu Jun 1 22:24:54 GMT 2017


Hey Matus, 

This is an excellent idea. :-) 

One DEV instance connected to a bug-capture module (rename HelpDesk if
you can). It could be kept in the same vtiger instance or linked to it. 

Everyone gets to read the identified bugs and commitment to fix, all in
the one place. 

You have more people able to test functionality for the base install and
you have the vtiger programmers able to confirm the issue as soon as
they can touch it. 

When the main bugs are clear, then it can go to RC in the same way, for
say 2 weeks. 

We all see it stable then and it becomes GA after a further 2 weeks. 

This is AGILE at its best. 

Best of all we all feel connected to the open source product. Everyone
can put in 1 hour a day to check their reqs, if it is simply login and

Not everyone needs to install on their local system (along with the
associated local issues) 

Score +1 from me for this Matus. 



On 2017-06-02 00:00, vtigercrm-developers-request at lists.vtigercrm.com

> Message: 4
> Date: Thu, 1 Jun 2017 12:36:25 +0200
> From: IT-Solutions4You <info at its4you.sk>
> To: vtigercrm-developers at lists.vtigercrm.com
> Subject: Re: [Vtigercrm-developers] Updating Vtiger 7.0.0 with Patch1
> Message-ID: <ogoqmv$pku$1 at blaine.gmane.org>
> Content-Type: text/plain; charset=utf-8; format=flowed
> Maybe create a separate dev installation with last change set so we can 
> try it in one installation (we all don't need install vtiger everytime). 
> I supose in this case we can better describe some bugs, scenario before 
> release a new path/version.
> Matus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20170602/43c76c39/attachment.html>

More information about the vtigercrm-developers mailing list