[Vtigercrm-developers] Vtiger 7.1 RC Released

[Alan Lord]

Why are there so many commits to the master branch?

What is the difference between the master branch and the 7.1.0 branch? 
Surely, until a version is actually "released" nothing should be pushed 
to master? (And then I'd expect it would just be a merge of the released 
status of the 7.1.0 branch or tag).

Could one of you explain your procedure and what each branch really 
signifies so we know which one we should be basing our development and 
testing efforts against?

TIA

Al

On 08/01/18 09:53, Satish Dvnk wrote:
> Hi All,
> 
> We would like to update you that Vtiger community edition *V7.1 RC* has 
> been published in sourceforge.net 
> <https://sourceforge.net/projects/vtigercrm/files/vtiger%20CRM%207.1.0%20RC/> 
> which will includes the following features and fixed 100+ bugs
> 
>  1. *Follow A Record* (Following a record is a nice fashion of marking a
>     record as a favorite. This will act as a shortcut to get to favorite
>     or active records. By following a record you get updates on it as
>     the users modifies the record).
>  2. *Duplicate Record Prevention* (Prevent duplicate records in Vtiger
>     from all sources by enabling the duplicate check)
>  3. *Webform Attachments *(Allow user to attach files to web forms)
>  4. *Import Users Using .CSV file* (Supports importing User data using
>     .csv file)
>  5. Supporting*Mysql V5.7*
>  6. *Customize modules* icons and *bugs *
> 
> 
> *regards,
> Satish.Dvnk*
> 
> 
> _______________________________________________
> http://www.vtiger.com/
>