Hi
Quote:
|
1) The source tar balls are for release 4.5.5 and 4.5.6 which are just few patches to 4.5, but how could i get just release 4.5 without patches? I think using svn repository that should be possible.
|
Releases 4.5.5 and 4.5.6 are full releases - both binary and source packages, not patches. SVN broke somewhere between 4.5.4 and 4.5.5 and I don't think it contains versioned branches, so I don't think it's currently possible to download the source for the original 4.5.
Quote:
|
2) If a developer wants to contribute to open source and applies some patch to just release 4.5 (with no patch) for which source code is present in svn how will he confirm that the code snapshot he/she is having is for release just 4.5? By downloading source tar balls it becomes little bit difficult for versioning. Ofcourse a person would not directly commit and would certainly follow the Zimbra and/or Open Source processes but without using svn don't you think it becomes little bit difficult for the developer?
|
Unless you have a wierd and wonderful reaosn, you do NOT want to patch or develop against original 4.5 - patch or develop against the latest source you can, ie 4.5.6..
You can determine the release of the code you have by looking at these files:
ZimbraBuild/RE/MAJOR.ZimbraBuild/RE/MINOR.ZimbraBuild/RE/MICRO-ZimbraBuild/RE/BUILD
The last svn tree I have (I think probably the latest), this gives:
4.5.4_GA-754
Doing any form of development from tarballs without svn is very difficult, I agree. It has been raised in this forum several times (search back) and Zimbra have stated their mechanism for synching their internal source with sourceforge svn is broken and they are working on getting it fixed.
The source tarballs accompanying each binary release are currently the best you can do with regards to accessing the source code.
On an unrelated note to this discussion:
Red Hat flags OSI offenders on partner site | The Register