[Vtigercrm-developers] Vtiger CRM 7.3.0 (Hotfix2) Released

Rubén A. Estrada Orozco rulotec1 at gmail.com
Wed Oct 14 15:58:24 GMT 2020


A possible hack would be to include an "empty" migration script. I think
that would be better than having different versions for 7.3.0.

Best case scenario would be to decouple db changes from version numbers.

Saludos

Rubén


On Wed, Oct 14, 2020 at 9:59 AM Oleg Antonov <oleg.a at pinstudio.ru> wrote:

> Hi Uma
> Thank you for the explanation.
>
> I believe the upgrade and patching process should be reviewed.
> We all need to know which version exactly is installed, especially for the
> module development. Because modules can act differently according to the
> version number.
> I think we should increment the last digit and have 7.3.2
>
> ср, 14 окт. 2020 г. в 10:41, Uma S <uma.s at vtiger.com>:
>
>> Hi Martin,
>>
>> No worries! I will try to give some insight on the upgrade process.
>>
>> *Version upgrade process:*
>> Version upgrade is carried through Migration/Index.php, applyDBChanges()
>> api,
>> This depends on getAllowedMigrationVersions() for the scripts to execute
>> for successful migration.
>>
>> After which we are updating the vtiger_version in DB with the source
>> version, which should be in sync with the migration script.
>>
>> *Hotfix patch without version upgrade:*
>> As hotfix patch without DB changes, will not have a respective migration
>> file. So the DB version can't be updated as per the process. Hence version
>> change will only be present with source vtiger_version.php
>>
>> Has source and DB versions are not in sync, further migrations are hard.
>>
>> *Conclusion*: Migration versions are bound to source versions, which
>> should be sync always.
>>
>>
>>
>> On Wed, Oct 14, 2020 at 12:17 PM Martin Allen <martin.allen at clystnet.com>
>> wrote:
>>
>>> Uma,
>>> Could you explain how (and why) the version numbering is tied to
>>> migration? I'll be the first to admit i've never even looked at the upgrade
>>> process code, so my knowledge of this is severely lacking.
>>>
>>> Martin Allen
>>>
>>>
>>> *01392 248692 - Main Office01392 690659 - Direct Line*
>>>
>>> *[image: signature2]*
>>>
>>> Have you visited our website recently? http://www.clystnet.com
>>>
>>>
>>> The information in this email is confidential If you are not the
>>> intended recipient, you must not read or use that information. This email
>>> and any attachments are believed to be virus free however no responsibility
>>> is accepted by Clystnet for any loss or damage arising in any way from
>>> receipt or use thereof. Clystnet Ltd (company reg number 7164503) is based
>>> at Silverdown Park, Fair Oak Close, Clyst Honiton, EX5 2UX
>>>
>>>
>>> On Tue, 13 Oct 2020 at 16:35, Uma S <uma.s at vtiger.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Sorry! I understand the sentiment with version numbering.
>>>>
>>>> But, as per vtiger structure. Versioning is tightly bound to migration
>>>> changes.
>>>> Only if post release carries migration changes, we can increment the
>>>> version. If not repackaging with patch_version upgrade is the choice.
>>>>
>>>> >>Or even call it 7.3.0.2,
>>>> Alan! As we are following the x.y.z format of versioning, We couldn't
>>>> support this change.
>>>> We do have specific tags
>>>> <https://code.vtiger.com/vtiger/vtigercrm/tags> created for each
>>>> release.
>>>>
>>>> >>https://code.vtiger.com/vtiger/vtigercrm/merge_requests/735
>>>> Matus! As this moreover looks like a bug, We can make this for an
>>>> upcoming release.
>>>>
>>>>
>>>> On Tue, Oct 13, 2020 at 8:26 PM Ing. Matus Sopko <sopko at its4you.sk>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> and why this hotfix was not added ?
>>>>>
>>>>> https://code.vtiger.com/vtiger/vtigercrm/merge_requests/735
>>>>>
>>>>> Hotfix3 now ;-)
>>>>>
>>>>>
>>>>> S pozdravom / Best regards / Mit freundlichen Grüßen
>>>>> Ing. Matus SOPKO
>>>>>
>>>>> IT-Solutions4You s.r.o.
>>>>> Kancelária: Slovenská 69
>>>>> Sídlo: Frantiskanske nam.5
>>>>> 080 01 Prešov
>>>>> SLOVAKIA
>>>>> Tel./ Fax +421/ 51/ 7732370
>>>>> email: sopko at its4you.sk
>>>>> http://www.its4you.sk
>>>>> skype: matussopko
>>>>>
>>>>> Dňa 13. 10. 2020 o 16:42 Alan Lord napísal(a):
>>>>> > On 13/10/2020 15:35, Martin Allen wrote:
>>>>> >> Is there a reason why this still isn't version 7.3.1 ?
>>>>> >> It's impossible to tell if a CRM has the hotfix installed without
>>>>> >> delving into the code otherwise! If the version number is
>>>>> incremented
>>>>> >> (as per semantic version numbering guidelines) then we could tell
>>>>> >> from the UI which EXACT version it is.
>>>>> >
>>>>> > +1
>>>>> >
>>>>> > Al
>>>>> >
>>>>> > PS: Maybe it should actually be 7.3.2 now as there have been two
>>>>> > independent hotfixes.
>>>>> >
>>>>> > Or even call it 7.3.0.2, but I completely agree with the sentiment.
>>>>> > Each release should have a tag in in the repo and it should NEVER
>>>>> > change in Sourceforge or where ever the download lives. There are
>>>>> now
>>>>> > three _different_ versions of the 7.3.0 tarball in the wild.
>>>>> > _______________________________________________
>>>>> > http://www.vtiger.com/
>>>>>
>>>>> _______________________________________________
>>>>> http://www.vtiger.com/
>>>>
>>>>
>>>>
>>>> --
>>>> With
>>>> Best Regards
>>>> Uma.S
>>>> Vtiger Team
>>>> _______________________________________________
>>>> http://www.vtiger.com/
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>
>>
>>
>> --
>> With
>> Best Regards
>> Uma.S
>> Vtiger Team
>> _______________________________________________
>> http://www.vtiger.com/
>
> _______________________________________________
> http://www.vtiger.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20201014/b57718a0/attachment-0001.html>


More information about the vtigercrm-developers mailing list