Multiple versions of libjingle-0.5.1.zip were released.

[GoogleCodeExporter]

Hi,

Today I rebased my project from libjingle-0.5.1 to libjingle-0.5.2. To do this 
I downloaded the .zip files for both versions, did a diff, and applied the 
resulting patch to my source tree. While working through my rejects, I was 
surprised to find that some of them applied to parts of the code that I had not 
touched in any way.

After a bit more digging around, I discovered that the libjingle-0.5.1.zip that 
I downloaded today is different from the libjingle-0.5.1.zip that I downloaded 
on November 4th. The difference between the two versions is attached, and I can 
provide the original diff if that would be helpful. The date on 
libjingle-0.5.1.zip on the jingle download page is November 8th, confirming 
that changes were made after I downloaded.

This is rather disturbing to me as it can cause a lot of pain for people trying 
to track your project:
- Creating a diff between two versions does not accurately reflect all changes 
that occurred between those versions.
- Hard coding a specific version to use does not guarantee that you are getting 
the same version, which could lead to subtle and hard to track debugging 
sessions. (We have the exact same version, and they are behaving differently.)

I would like to kindly request that once a release is made, any subsequent 
changes be made to a new revision number.

I think that in this case it would also be helpful to make it clear on the 
downloads page that there are two different version 0.5.1 releases, and provide 
both .zip files so that people like me who are manually rebasing don't get 
burned.

Finally, as far as I can tell, releases are not being tagged in the repository, 
which makes it difficult to use the repository to get stable versions.

Best regards,
Blaise Gassend

PS: I would like to add that I am very grateful that libjingle is being made 
available to the community, and am thankful for the effort that has and is 
going into it. I am just trying to suggest ways in which it can be made more 
beneficial.

Original issue reported on code.google.com by blaise.g...@gmail.com on 18 Jan 2011 at 12:14

Attachments:

• diff.txt

[GoogleCodeExporter]

Point taken, thanks for the feedback. I think in the past we only bump the 
version number if there was a major release. To get some smaller fixes pushed 
quicker, we just flushed the zip package with update, however, if this becomes 
a pain, we'll pack all changes into a major release with newer version number 
in the future.

Original comment by jun...@google.com on 3 Feb 2011 at 12:03

• Changed state: Done