Re: Revision numbers as MAJOR.MINOR.PATCH?

I go out of my way to avoid the development content being bound to any
release number. Only at actual release time is a given stabilised milestone
assigned the product version that the general populace need to know about.

That way, milestones can be regular occurrences and QA and product
management, independent of development can decide if the feature-set of a
given milestone warrants an actual public release.

Of course, this model suits us, it won't necessarily suit everyone.

Don't expose the users to details of your SCM. If you changes SCMs or even
the processes by which you use it, users should not notice (well apart from
quality and/or productivity improvements since that's the only reason you
change right).

--
Talden
On 7/2/07, Rob Hawkes <rob.hawkes@gmail.com> wrote:
>
> Heya,
>
> How can I make subversion output revision numbers in a
> MAJOR.MINOR.PATCH method rather than 1, 2, 3, 4, 5, 6.. etc?
>
> Regards,
> Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>