Daniel Veditz wrote: > > So let me throw out some alternates using Netscape 6.2 as an example. > > as shipped: Gecko/20011019 > > some alternatives to get the juices flowing: > > Gecko/20010904.45 // pulled 45 days into a branch > Gecko/20010904:20011019 // pulled 10/19 from a 9/4 branch > Gecko/20011019 (rv:0.9.4) // pulled 10/19 based on 0.9.4 > Gecko/0.9.4.20011019 // ditto
How about Gecko/NS-62.20011019 - that is, Gecko/BranchName.Timestamp For mozilla 1.0, the equivalent would be Gecko/Moz-10.20020108 (if we were to have a mozilla 1.0 branch right now, and reference today's build on it). The choice of a globally unique branch name shouldn't be too hard, should it? (I used the convention of vendor-version for the branch name, which could perhaps be enforced by the policy too). We could either give a policy for branches-from-branches (eg Gecko/Moz-094.NS-62.20011019) or just use the fact that the branch name is globally unique (so NS-62 would be valid on it's own, and you'd need external knowledge to determine that it was based on Moz-094). Thoughts? -- Stuart Ballard, Programmer FASTNET - Internet Solutions 215.283.2300, ext. 126 www.fast.net
