Hi michalkleiner,
Thank you for your feedback.
SVN tag 1.5.2.6 is missing
Sorry, I don’t create the tag of the ver 1.5.2.6. It version is trunk( lastest version).
Please download from here.
https://downloads.wp.xz.cn/plugin/wp-admin-ui-customize.zip
Thanks,
gqevu6bsiz
Why not to create a tag even from the latest version? It’s free 🙂
It’s a correct way how to reference the version, even if it’s the same as what trunk contains. Without the tag people using http://wpackagist.org/ have to use dev-trunk which doesn’t necessarily mean the same version at all times. With dev-trunk one can get different code in different environments when using any sort of continuous delivery/deployment tools in a case you commit a change. Tags are supposed to be more stable (yes, they can change too but that’s a really bad practise).
Thanks
Michal
Hi michalkleiner,
Thank you for your feedback.
I think I was able to maybe understand be said of you.(Sorry my english is not good enough.)
I create tag just before latest version.(i.e. 1.5.2.5)
About the reason I don’t have latest version to tag, because there are times when rewrite a small part only latest version of the files.
Part of the readme.txt.(Tested up to)
In other words,
If I create the 1.5.2.6 to tag and if 1.5.2.6 is correspond to WordPress 4.2,
I think it need to create tag the 1.5.2.6.1.(only different the “Tested up to” part)
I have this work in inconvenient. So I have trunk with the latest version.
When not correspond to the latest WordPress or If I will add the new feature/bug fix,
I create the version tags.
Tags are supposed to be more stable
I think so too. And, I’m not very knowledgeable about the SVN management.
If you have ideas tell for me, I’m happy!
Thanks,
gqevu6bsiz
Hi gqevu6bsiz,
that rewriting of a small part from the latest version, that is exactly what I was referring to when I said that you can get different version each time you download/fetch from trunk. Even when it’s only “Tested up to” part of a readme file.
This is ok to have it only in trunk and publish it as a tag with a feature release or a bugfix.
But any feature release or tag should be tagged and “stabilised” to be accessible under that version tag. You shouldn’t refer to 1.5.2.6 (version somewhere in your code or readme file) and not have it as a tag in SVN if you know what I mean?
So what I would recommend is to tag a version each time you publish any bugfix/change/feature that will allow people relying on tags to use it properly and also at the same time you can keep updating “Tested up to” in your trunk. People downloading via https://downloads.wp.xz.cn/plugin/wp-admin-ui-customize.zip will get latest/trunk version and people using tags will still get stable version with latest changes/bugfixes, just not the readme file changes which is completely ok.
Happy to discuss further if it can help you.
Cheers
Michal
Hi michalkleiner,
Thank you for your reply and your recommend.
Maybe, I think I was managing at the different/wrong concept.
(For I don’t want to have the hassle)
I tried to http://wpackagist.org/ and your problem is I can see.
And, My understanding is following.
My think SVN managing is corresponding of WordPress version.
e.g.) Compatible version managing
This think is I could not care about the Tag users.
I think you and people are looking for version control as product(tag) version.
e.g.) Tag version managing
There is no difference = stabilised
not have it as a tag in SVN if you know what I mean?
And, this plugin is tags(Always have not only latest version): http://plugins.svn.ww.wp.xz.cn/wp-admin-ui-customize/tags/1.5.2.5/
You shouldn’t refer to 1.5.2.6 (version somewhere in your code or readme file)
I think this is difficult. I think described in the header in making plugin/theme.
File_Header
And, I think that sometimes be version information as cache of CSS/JS.
e.g.) http://example.com/example.js?ver=1.5.2.6
To summarize them all,
Lastest version is also better to create the Tag(1.5.2.6) for Tag Users(people/wpackagist.org/other api/etc…).
Could you tell me please my understanding is correctly?
If my understanding is correctly, I will create the Tag in a little bit also of difference.
Many thanks to your reply.
gqevu6bsiz
Yes, I think you understood it right. Latest stable version having all bug fixes and features up-to-date should have a tag as well.
And last note: Of course you can refer to your version in the code, it was meant that if you refer to any version/tag in your code/readme file, a tag for that should also exists.
Cheers
Michal
Hi michalkleiner,
Thank you for your reply. I am glad to get a good reply from you.
I will have the latest version with tag and also I will small update will be tag.
Thanks,
gqevu6bsiz
