09-13-2009, 06:37 PM
I don't see the point of creating a branch for each weekly build. On average, we develop weekly builds Saturday and Sunday evenings, with around 5 changes to the gamemode. Creating a branch for five changes is a little far fetched. Fair enough I can understand things need to be tested, but why can't they be tested before the developer commits them? Most weekly changes are really minor tweaks and would require just a quick five minute test with another player. If we only commit things after they've been fully tested, trunk will remain stable.
If a circumstance occurs where a developer does make a lot of changes and they can't commit until the branch is created, which is on that Sunday, commiting lot's of changes to one revision isn't to good because it increases the chance of conflicts and makes it harder to revert changes in the future.
Additionally, over the weeks we've been most actively developing on a Sunday night, prior to the update. If we have to commit changes before 6.40 some of us may feel rushed to complete code or any important bug fixes, which may result in further bugs. It's stupid dis allowing commits before 6.40 - what if a bug is found during pre-update testing and a commit is needed before it goes live?
It's pointless making a backup of the compiled version. If a problem occurs and we need the older version, what good is the amx? The full source can be reverted using tortoise svn.
If a circumstance occurs where a developer does make a lot of changes and they can't commit until the branch is created, which is on that Sunday, commiting lot's of changes to one revision isn't to good because it increases the chance of conflicts and makes it harder to revert changes in the future.
Additionally, over the weeks we've been most actively developing on a Sunday night, prior to the update. If we have to commit changes before 6.40 some of us may feel rushed to complete code or any important bug fixes, which may result in further bugs. It's stupid dis allowing commits before 6.40 - what if a bug is found during pre-update testing and a commit is needed before it goes live?
Quote:Use SFTP to connect to the mainserver, goto the /Server/gamemodes/ folder, and rename lvp.amx to lvp.amx.YYYYMMDD, this way we can easily revert back if despite al testing something still crashes. Then upload the new build lvp.amx.
It's pointless making a backup of the compiled version. If a problem occurs and we need the older version, what good is the amx? The full source can be reverted using tortoise svn.