timeless wrote: > Gervase Markham wrote: > >>This is currently under discussion. We hope to have a solution soon >>which is acceptable to everyone. > > given your previous 'under discussion' actions I hope that this > discussion will be public unlike the previous ones.
It has been public. Look at the top of this thread, for example, we're just re-hashing the same suggestions over and over. It's all been argued for and against, what more "public" do you want? Drivers just needs to make a decision. My current proposal before drivers (a compromise with the evangelism team) looks like: 1. enshrine the rv: field as part of the Mozilla comment. Some sites are already looking for this and we don't want to break them. 2. the "date" part of the Gecko token will remain for compatibility, but for branches will be frozen at the date the branch split from the trunk. 3. appended to the date part will be "-<gecko rv>". This will for now be redundant with the rv value in the mozilla comment, but this is where we'd like people to look instead. The redundancy will have value when the browser becomes a true embedding client and potentially has a different version than the engine. 4. for daily branch builds add a comment after the Gecko token (bd:<date>) so that internally places like Bugzilla can defend against bad builds. This is removed as unnecessary clutter in releases Examples: official releases: Mozilla/5.0 (...; rv:1.0) Gecko/20020401-1.0 Mozilla/5.0 (...; rv:1.0.2) Gecko/20020401-1.0.2 daily builds Mozilla/5.0 (...; rv:1.1a) Gecko/20020402-1.1a (bd:20020402) Mozilla/5.0 (...; rv:1.0.3) Gecko/20020401-1.0.3 (bd:20020622) No "+" for daily builds, after the milestone we start right into implementing the next release and bump the version, with the "bd:" field indicating the preliminariness of it. Not as compact as my original "days plus" formulation, but easier to understand what it means by humans Haven't heard a peep back from drivers, so they might hate it for all I know. -Dan Veditz
