On Fri, Sep 30, 2011 at 8:42 AM, Fathi Boudra <email address hidden> wrote:
> --version should show the version as available in setup.py.
That's easy for the case where the user runs l-m-c from a bzr branch,
but that's probably the case where the -v option is least needed. The
setup.py file is not available in the package, so we need to carry the
version info into the package somehow. Is there a standard way of
doing this?
>
> as you do a post release bump, --version should show YYYY.MM.1. a better distinction will be to add a devel string.
> e.g. version="2011.09.1 (devel)"
Yeah why not; the '.1' worked better in the 0.4.x version scheme.
>
> when installed as a package, common practice is to use upstream version,
> not the package version.
On Fri, Sep 30, 2011 at 8:42 AM, Fathi Boudra <email address hidden> wrote:
> --version should show the version as available in setup.py.
That's easy for the case where the user runs l-m-c from a bzr branch,
but that's probably the case where the -v option is least needed. The
setup.py file is not available in the package, so we need to carry the
version info into the package somehow. Is there a standard way of
doing this?
>
> as you do a post release bump, --version should show YYYY.MM.1. a better distinction will be to add a devel string.
> e.g. version="2011.09.1 (devel)"
Yeah why not; the '.1' worked better in the 0.4.x version scheme.
>
> when installed as a package, common practice is to use upstream version,
> not the package version.