[p4] Script files and versioning

Rick Macdonald rickmacd at shaw.ca
Wed Nov 5 07:36:26 PST 2008

I just have questions, not answers.

For me, versioning implies branching, but a question that I would need 
to ask is what is your intention and requirement for the versions. 
Having created a new release 3.0, do you have people still using version 
2.8? Do you need to give the version 2.x users new features and bug 
fixes relative to their 2.x version, or do you simply make them upgrade 
to 3.1 or whatever the latest version is at the time to get their bugfix?

Also, are your php, python and sql components independent to the point 
that you might push out a new version of the sql/database, or would all 
three always go out as one big release?


Robert Schneider wrote:
> I hope one of you can give me some advise. I still don't know how to do it.
> We have a bundle of developed php files that make up a certain intranet site that gets deployed on our customer servers. Until now there was no version for this php application. We just had the terms 'the old version' or 'the version that is installed on ...'. Awkward, I know.
> Now I'd like to introduce a versioning scheme for the php application. So we can talk about e.g. 'Version 3.2'. But my problem is, that I don't know how to achieve this correctly. At least I know that all files should be seen as one group that get one version.
> Should each php file get a comment with a version? Could I use keyword expansion? If so, which keywords? Should the version be visible in the application, so it is visible in the browser? What could you recommend? How would you do it?
> I have similar issues with some Python script files that build up a server. And also with a SQL script that creates a database. It would be also interesting how to version these items too. Same way or different?
> Thank you,
> Robert
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

More information about the perforce-user mailing list