8 ms·
Well, the point being is that users shouldn't really be exposed to the details of internal branching. It is perfectly fine to use hierarchical versions internal
by latitude 15y ago
Well, the point being is that users shouldn't really be exposed to the details of internal branching. It is perfectly fine to use hierarchical versions internally, but they should be mapped to something simpler for the public releases. A one-to-one mapping, there should be no such thing as two different #37 releases.
- yuliyp 15y agoAh, I guess you then run into some blurring when you get to external beta testers and partners, or if you're developing an open-source product. But if you've got a closed-source product that you can manage the external releases to a single stream, then yeah, you can go with simpler public revision numbers.