Carlos Rodriguez wrote
Okay, let me see if I understand this, you are saying that there are no real technical reasons to provide a migration path from Beta to Final? That it is an arbitrary decision by the Gallery team to prevent this and break any Gallery created with a Beta version when the final is installed, just to avoid people from using Beta software for production? Is this what you are saying?
Your assumption is wrong. Matthias said there will not be an upgrade path from beta to final release.
Carlos Rodriguez wrote
In that case I will not test until the final version is available. This is for two reasons, first, this means that the final version will have new code execution paths that have not been thoroughly tested, as it will only be available in the Final release to break sites running on Beta software. And the second and most important reason is that I do not agree with the Gallery team's logic and decision of breaking Gallery implementations done with the Beta version. That is counter productive, I cannot understand you guys dedicating time to design, develop, and test code just to prevent people from running Beta software for production, this is totally wasted time. What is the added value of this? Just so that you can cover your rears? Bigger companies with more complex and serious software give you the warning of not using Beta software for production but if you do it is your problem. And also, being a open source project, when the final comes out with source code we can remove the code to break the sites using Beta and recompile, bypassing your poorly thought out design to prevent people from using the Beta for production. This can also be made public.
Wrong assumptions. Feel free not to test and come back when release is done. Not providing an upgrade path does not mean we will break anything. Software makers may require you to uninstall beta versions in order to install RTM ones. We are doing exactly that, to avoid unnecesary support issues. Like you said, it is your problem if you run it in production, but you are not even going to test, so what's the deal? Why are you going through so much pain with our efforts? You seem to be having a hard time with us, yet we simply said two things: DO NOT RUN BETAS IN PRODUCTION AND WE WILL NOT PROVIDE AN UPGRADE PATH FROM BETAS. However, "being an open source project", you can take GAL 3 version, bypass our poorly thought out design and recompile. And sure, why not, go ahead and make it public, we will all benefit. James Jegers did it before.
Carlos Rodriguez wrote
And notice that my intention is not to run Beta software for production but instead to start creating albums now with no public access and then apply the final when it becomes available. In this way I could do testing and get the Gallery ready for production, but the short sighted logic of the Gallery team to break albums made with the Beta prevents this. Therefore I cannot test until the Final release comes out, I want to do realistic testing with all the albums I need to create, not play with the module and then destroy the test albums.
All I can say is that you would still be running the beta in production, just not publicly. But then again, I am a shortsighted, poor designer that is working on the project.
Carlos Rodriguez wrote
Another suggestion, please proof-read your posts before you finish them, they are very difficult to understand. And by the way, my first language is not English either, which is why I am very careful when I write.
Matthias was as careful as usual, he may not be as profficient as you are in English, but to me he seems a lot more collaborative in his own rough German way.