Corey O'Connor wrote:
I released a new version of data-spacepart that resolved some of the
issues with the previous release. One issue I had was the previous
release used the version numbering scheme I use at work:
[date].[release] Which does not appear to work as well as the
traditional X.Y.Z
Am Mittwoch, 11. Februar 2009 23:02 schrieb Corey O'Connor:
The way I read changes in version numbers for a scheme using the
format X.Y.Z is:
* A change in Z indicates bug fixes only
* A change in Y indicates the interface has changed but not in an
incompatible way. For instance, maybe a
On Wed, 2009-02-11 at 14:02 -0800, Corey O'Connor wrote:
On Wed, Feb 11, 2009 at 2:48 AM, Duncan Coutts
duncan.cou...@worc.ox.ac.uk wrote:
On Tue, 2009-02-10 at 10:21 -0800, Corey O'Connor wrote:
I released a new version of data-spacepart that resolved some of the
issues with the previous
On Thu, Feb 12, 2009 at 4:12 AM, Duncan Coutts
duncan.cou...@worc.ox.ac.uk wrote:
As Wolfgang mentioned, you may choose to follow the common package
versioning policy.
http://haskell.org/haskellwiki/Package_versioning_policy
We are planning to develop tool support for this. To let packages
On Tue, 2009-02-10 at 10:21 -0800, Corey O'Connor wrote:
I released a new version of data-spacepart that resolved some of the
issues with the previous release. One issue I had was the previous
release used the version numbering scheme I use at work:
[date].[release] Which does not appear to
On Wed, Feb 11, 2009 at 2:48 AM, Duncan Coutts
duncan.cou...@worc.ox.ac.uk wrote:
On Tue, 2009-02-10 at 10:21 -0800, Corey O'Connor wrote:
I released a new version of data-spacepart that resolved some of the
issues with the previous release. One issue I had was the previous
release used the
Corey O'Connor wrote:
Part of the reason they seem awkward to me is that I expect the
difference between version numbers to indicate something about what
has changed between the two versions. This only ends up being a
heuristic but a useful one. Date based version numbers don't
communicate much
On Wed, Feb 11, 2009 at 10:20 PM, wren ng thornton w...@freegeek.org wrote:
For projects which are released very frequently (i.e. on the order of daily)
or very infrequently (e.g. semiannually, annually) then date-based releases
can make sense. However, the releases do need to be quite regular
I released a new version of data-spacepart that resolved some of the
issues with the previous release. One issue I had was the previous
release used the version numbering scheme I use at work:
[date].[release] Which does not appear to work as well as the
traditional X.Y.Z release numbering scheme
* Corey O'Connor coreyocon...@gmail.com [2009-02-10 10:21:54-0800]
I released a new version of data-spacepart that resolved some of the
issues with the previous release. One issue I had was the previous
release used the version numbering scheme I use at work:
[date].[release] Which does not
10 matches
Mail list logo
