If this is your first visit, check our documentation. To post, register or login.
Forums / Support Site Issues & Questions / version stamping...

version stamping...

Started by carlwhat on 18 May 2017, 1:25 AM · Views: 55

Results 1 to 2 of 2
18 May 2017, 1:25 AM
#1
carlwhat avatar

carlwhat

zennedOut

Join Date:
Nov 2005
Location:
los angeles
Posts:
2,974
Plugin Contributions:
8

version stamping...

hi,
quick question. when i look at the following file:

includes/classes/navigation_history.php

it appears to have changed since the version was stamped with a date at the top of the file. i have verified the situation in v1.5.5e... ie change made after the version stamp and set up for download.

is this a common practice... or was something missed?

i only ask as i use the date to verify if i have the latest version when working with a file, and now i'm not sure whether i can trust the date or not.

thanks.

author of square Webpay, now with Apple Pay and Google Pay.
mXworks
donations: venmo or paypal accepted.
premium consistent excellent support. available for hire.

18 May 2017, 3:55 AM
#2
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,512
Plugin Contributions:
176

Re: version stamping...

It was missed.

In practice we usually only do a full-sweep update of date stamps when we publish a new number-release ... not with a "letter-release" (ie: patches only).
Updating the dates at other times can actually create version-control problems in git when trying to sync updates to the v160 side too. So sometimes we avoid touching the dates when doing interim patch-only commits.

Also note that there are a few things in github that have been added since v1.5.5e, which will become part of either v1.5.5f or v1.5.6 depending what happens with the next release of the v1.5.x series.

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.