Silent updates to 7.02.07 unacceptable!

Have there been changes to 7.02.07 files since being given notice of the critical patch which I downloaded on 18th June?

Depending on when you downloaded the updates these files were changed to my knowledge.
maincore.php and mimetypes_include.php

Actually we are all very unfamiliar with Github. But I stumbled across this feature called compare in GitHub.

https://github.com/PHPFusion/PHPFusion/compare/7.02.06...7.02.07

The .7 file structure is different than .6. We just need to fix the folders to be able to use this function. Then you can see the version comparison code change logs.

I assume we can also type a command on git to download the change logs between forks?

Github is for development. At some point you decide to bundle these changes at github and provide an update package and a new version full package. But the point is these packages you offer here change without notification.

For us, the majority of users, depend on you releasing update packages and NOT watching github where daily changes are made. Even changes on changes, changes withdrawn etc. That is not doable, even with a nice compare feature in github.

What is the proposal then? Let Arda note down every push merge?

Well looked at that compare function in Github.
This would be my proposal.

[olist=1]After a new (sub) version release all changes after that release should go to a new version in Github. (You released v7.02.07 so all changes after that should go to v7.07.08)
Then when some changes, fixes and securtity updates are gathered there comes a point to bundle them again in a new (sub) version release. (v7.07.08)[/olist]

Now you start back at #1 again and +1 the version number.

This way released version numbers don't have changing files. The only changing files are in the new next not yet released version.

We are using GitHub for a reason. You can catch up all updates from diff logs.

Sample for master branch:
https://github.com/PHPFusion/PHPFusio...its/master

Sample for 7.02.07 branch:
https://github.com/PHPFusion/PHPFusio...ts/7.02.07

See, it's not that hard.

I myself didn't want to release a new version number yet, because this was not a major version fix (only some small additions), and this itself would prevent our support team's hours of work and would help them focus on development or their in real life situations. Also, those mime types are still not complete for some people because of compressors or editors etc., and even I wanted them to test with a debug code I've provided but they didn't.

http://www.php-fusion.co.uk/forum/vie...d_id=32886

We just can't whitelist all, they need to test so it becomes more stable.

Or I'll appreciate if someone does it and makes a pull request. I'll test and accept gladly. I'll even force our dev team to push a new number.

Oh and, master and dev branches are not to use on development directly. We also have version numbers as branches, which the downloads are served from.

You missed the point from my previous posts.
But apparently I am the only one who sees this as a problem.

With no support from other users I'll drop the subject.

I see you, Wanabo.

You have a point, and a pretty important one. When should we announce that code on Github has been updated and hence changed the release available from Github.

With the previous SVN at SF we did make code changes that were not announced as releases. So in a way, that has not changed. We should, however, consider making code improvements and then decide whether to release them or not, as an active decision. That would leave ongoing code changes on Github in a Beta state, until we push a release.

I have to agree with Arda, until all bugs/issues have been worked out of v7.02.07 there is no need to have a new version number for every bug that's fixed, that's just crazy. But maybe instead have a thread that let people know about any fixes and a download link for the fixed/updated files so they can download them.

I find out about fixes by following the suspected bugs thread but it can be confusing at times to sort through all the posts, as I'm sure many other do too, which is why you see so many new threads about the same issues being started.

So maybe have a locked thread dedicated to the updated/fixed files for the current version and a link to download them would be a big help to the community.

Minor updates that are essential can and should be done on a call to call basis.
I agree with the view that we can´t do version upgrades everytime we are updateing the mime reference files or other minor things that needs to be adjusted.
Administrators need to keep in mind that we have this feature as a security feature. Most of us want this to work. It is that important.
If people have problems with their uploads we can easily help them when the question comes to our forums. A helping post will let people know that the MIME check as in the case have been updated and it will keep getting updated until we covered what needs to be covered.

Everything that can be said have been said here.
Thank you for your input!

[ LOCKED ]