Am 22.07.2013 10:42, schrieb Tobi Gritschacher: > The tags were made (as explained already several times in the past) to have a > defined and frozen snapshot of the whole application with all parts working > together for e.g. demo time & updating the test system. As far as I know this > can also be achieved by using the deployment branches, so I'm not opposing to > stop our present tagging policy.
The tags are not for deployment, and never were; We use branches for that. The tags are utterly meaningless to "consumers", they are just an internal tool for the team. The tags (usually) represent sprints and are used to indicate what whas demoed together, and when. They are also useful for pulling to right version for demoying on the test systems. Using the deployment branches for this purpose has the disadvantage that they are not fixed: we may backport stuff to them, so after a few weeks, it's no longer clear what we actually demoed. Also, we may demo more often than we deploy, or the other way around - both have happend in the past. I think tags are the right tool for what we use them for, and we should keep using them. I don't care about the naming scheme as long as it's easy to find which tags applied to which spring/demo session, and it stays consistent. -- daniel _______________________________________________ Wikidata-tech mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
