version

[primalmotion]

Hi,

It seems that your fork is more advanced and more stable than the official one. Thanks for this.

But I'd like to know why the version is lower than the official one? Official one is xmpppy-0.5.0rc1 and yours is 0.4.0.

[snakeru]

Hmm...
Your mail is somewhat confusing.
On one hand subject says 'normanr/xmpppy', on other, email seems to be
directed to me (snakeru).
I am the original author of xmpppy, but since then a lot of different
people contributed. So it is effectively not my 'own' project anymore.
Norman is current maintainer of library.
As for the numbering - there is no such thing as straight-line
numbering. People often try to pretend like there is but it is only
possible if there is just one single developer. So don't pay attention
to this. For instance it may mean the 'official' version number it was
originally based on.

Hope this helps.
Alexey

On Tue, May 3, 2011 at 1:08 PM, primalmotion
reply@reply.github.com
wrote:

Hi,

It seems that your fork is more advanced and more stable than the official one. Thanks for this.

But I'd like to know why the version is lower than the official one? Official one is xmpppy-0.5.0rc1 and yours is 0.4.0.

Reply to this email directly or view it on GitHub:
#4

[normanr]

@snarkru: I think you got an email notification because you're a collaborator on my repo.

@primalmotion: it looks like the version number increment was never commited to git. The git version is effectively post 0.5.0-rc1, just it doesn't look like it.

[primalmotion]

Ah ok, great.

Is there any chance to update this version in the source? as my project is linked to the latest version of xmpppy, and when I want to use the master branch it complains it can't find the correct version, which then needs to update my own setup.py but I guess this is not very relevant to link to a previous version to get a newer one :)

BTW, thanks to both of you for your work on this lib.

[normanr]

I'm not clean on what version number should be in git, any thoughts? It's not 0.5.0-rc1, neither 0.5.0-rc2, maybe just 'git'? or 'latest'?

[primalmotion]

What I usually do is that I use in my source the future version.
For example, if I released the version 1.0, my source will get the estimated next release number. so It would be 1.1

Cause my problem is that I want users get the 0.5.0rc1 from pypi and let them use the master branch if they want.

I'm not sure I'm very clear :)

[normanr]

according to http://docs.python.org/distutils/setupscript.html#additional-meta-data I think 0.5.1a1 might be the sanest version number at the moment

[primalmotion]

As it's greater that my require which is xmpppy>=0.5.0rc1, I'm happy.

[normanr]

Done.

[primalmotion]

Thanks!

Antoine Mercadal

Le 3 mai 2011 à 14:21, normanr reply@reply.github.com a écrit :

Done.

Reply to this email directly or view it on GitHub:
#4 (comment)