Avidemux Forum

Avidemux => Main version 2.6 => Topic started by: Jan Gruuthuse on September 04, 2014, 02:36:31 AM

Title: Reflection on 2.6.8-DDMMYY new scheme FIXED
Post by: Jan Gruuthuse on September 04, 2014, 02:36:31 AM
fixed in [Build] Change date format so that is increasing
Just noticed this reflects not the source creating / writing / pushing date, but represents the compilation date. This seems troublesome to me.
A compiled version from 04092014 could be identical to one from 03092014. You don't know if there is a difference or not between the two. Is there a way the source could reflect the creation date and that is used instead of compilation date?

Could you change the date scheme DDMMYY to YYMMDD? This way the files would be sorted alphabetically and shown correctly ascending/descending by year then month and then days keeping them together:

20140911
20140930
20141201
20150113

now you would have all the ninth days from each month/year together:

09092014
09012015
09032015

thanks for looking in to this.
Title: Re: Reflection on 2.6.8-DDMMYY new scheme
Post by: AQUAR on September 06, 2014, 12:39:58 PM
I think the older incremental revision number for versioning provided a good approach.
It was easy to sort those in the correct order off source change/creation.
If the revision number is getting to big then maybe it could start afresh with each version number bump.
I do keep every DL version of avidemux in my archive (not sure why!).

But mean probably has other reasons for changing the approach.
Title: Re: Reflection on 2.6.8-DDMMYY new scheme
Post by: mean on September 06, 2014, 12:46:45 PM
There is no "revision" number with git, so we can no longer use that
Title: Re: Reflection on 2.6.8-DDMMYY new scheme
Post by: AQUAR on September 06, 2014, 01:06:40 PM
Thanks for that.

I was a bit curious as to the why, and found there were a lot of opinions on this issue.
Did note that for a single project branch it seems Bazaar allows for version numbers.

Title: Re: Reflection on 2.6.8-DDMMYY new scheme
Post by: Jan Gruuthuse on September 08, 2014, 03:51:01 AM
Quote from: Jan Gruuthuse on September 04, 2014, 02:36:31 AM
20140911
20140930
20141201
20150113
most important would be: now you would have ascending serial numbers
Title: Re: Reflection on 2.6.8-DDMMYY new scheme
Post by: AQUAR on September 08, 2014, 12:53:29 PM
Of course - a date code of YYYYMMDD for versioning gives you a numeric file sort in ascending order.
The chinese will identify with that date code, most countries expect the other way around.

Ability to sort the versions is more important IMHO than date code used. 
Title: 2.6.8-DDMMYY new scheme wan't install due to lower daynumber
Post by: Jan Gruuthuse on October 04, 2014, 12:09:39 PM
Currently Ubuntu protests when installing version build 04102014 on a version build on 24092014 as that number is lower then the installed version.
To keep ascending version numbers for now an in future best would be Year + Month + Day as suggested before YYYYMMDD. 20141004 build would install on 20140924 build. The version number would always increase.
Title: Re: Reflection on 2.6.8-DDMMYY new scheme FIXED
Post by: Jan Gruuthuse on October 05, 2014, 02:15:20 PM
avidemux3-core-2.6.8-141109-Linux (2014 nov 09)
fixed 2014/10/05. Thanks
Title: Re: Reflection on 2.6.8-DDMMYY new scheme FIXED
Post by: macduke on November 14, 2014, 01:45:12 PM
Nightly builds seems still with DDMMYYY format. At least to Oct 19th in win dirs.
Title: Re: Reflection on 2.6.8-DDMMYY new scheme FIXED
Post by: Jan Gruuthuse on November 14, 2014, 04:31:10 PM
your observation is correct: avidemux_r191014_21bf_win64.7z