? Pending

User tests: Successful: Unsuccessful:

avatar zero-24
zero-24
2 May 2016

Summary of Changes

https://github.com/joomla/joomla-cms/search?utf8=%E2%9C%93&q=+__DEPLOY_VERSION__&type=Code

Testing Instructions

Nothing to test as it is just a doc block change!

avatar zero-24 zero-24 - open - 2 May 2016
avatar zero-24 zero-24 - change - 2 May 2016
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 2 May 2016
Labels Added: ?
avatar andrepereiradasilva
andrepereiradasilva - comment - 2 May 2016

i was about to do this. Thanks.
But will 3.6 be the next version?

avatar roland-d
roland-d - comment - 2 May 2016

@zero-24 If we hardcode this, shouldn't we change it every time with a new release?

avatar zero-24
zero-24 - comment - 2 May 2016

@andrepereiradasilva yes see: https://developer.joomla.org/news/644-version-number-shifting.html

@roland-d I'm not sure what you mean? The __DEPLOY_VERSION__ string is a placesholder the framework use to set the correct version on time of the release.

But the CMS don't use this kind of automation. This is the last i know. Maybe @mbabker can help.

avatar andrepereiradasilva andrepereiradasilva - test_item - 2 May 2016 - Tested successfully
avatar andrepereiradasilva
andrepereiradasilva - comment - 2 May 2016

I have tested this item :white_check_mark: successfully on 19dad0c


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10183.

avatar andrepereiradasilva
andrepereiradasilva - comment - 2 May 2016

BTW shouldn't it be 3.6.0 instaead of 3.6. Is there any rule for that?

avatar brianteeman brianteeman - change - 2 May 2016
Title
__DEPLOY_VERSION__
__DEPLOY_VERSION__
avatar brianteeman brianteeman - change - 2 May 2016
Category Code style Documentation
avatar andrepereiradasilva
andrepereiradasilva - comment - 2 May 2016

@zero-24 can you replace with 3.6.0

avatar mbabker
mbabker - comment - 2 May 2016

There isn't a rule on whether it's just major.minor or if it's major.minor.patch. The CMS has mainly used the former while the Framework ends up using the latter because the job that creates the release tag runs this command and uses the user's input version number:

find . -name "*.php" -type f -exec sed -i "s/__DEPLOY_VERSION__/$Version/g" "{}" \; -exec git add {} \;

The CMS doesn't have a fully automated job like that and IMO it shouldn't either for reasons not relevant to this discussion.

avatar roland-d
roland-d - comment - 2 May 2016

All clear, I was just wondering :)

avatar wilsonge
wilsonge - comment - 3 May 2016

We have as of recently in build/bump.php - but that's for another PR.

avatar wilsonge wilsonge - change - 3 May 2016
Status Pending Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2016-05-03 15:20:41
Closed_By wilsonge
avatar wilsonge wilsonge - close - 3 May 2016
avatar wilsonge wilsonge - merge - 3 May 2016
avatar wilsonge wilsonge - reference | 5fda338 - 3 May 16
avatar wilsonge wilsonge - merge - 3 May 2016
avatar wilsonge wilsonge - close - 3 May 2016
avatar wilsonge wilsonge - change - 3 May 2016
Milestone Added:

Add a Comment

Login with GitHub to post a comment