Is /branches/releases/1.x safe to use? Is it stable?

MasterGod · Post by **MasterGod** » Wed Jan 30, 2008 5:27 am

I don't want to use the /trunk version but there are some things that I must upgrade in my irrlicht version so is /branches/releases/1.4 stable because I see it also gets updates..

P.S
- Those updates to /branches/releases/1.4 are for v1.4.1 right?
- I don't remember if someone did said it to me or not so I'll ask again, ANY warning I get when compiling /branches/releases/1.4 should be reported, right? (except the jpglib etc warnings..)

Thanks.

BlindSide · Post by **BlindSide** » Wed Jan 30, 2008 6:05 am

In my experience, nearly all SVN versions are pretty much safe to use.

I recommend just upgrading to the latest, and testing the waters.

hybrid · Post by **hybrid** » Wed Jan 30, 2008 8:28 am

The branches/releases/1.4 repository should be pretty safe to use. There are only a few enhancements done, nothing API breaking, and mostly minor bug fixes (well, small number of lines changed, sometimes with a huge impact on increased correctness, though).
The only thing which is still necessary to be fixed before a 1.4.1 release should be ready is the texture matrix usage in CMatrix.h. Some methods seem to work wrongly. I want those to be fixed before the release (hence they are second on my todo list, after the Collada and LWO loaders).
The actual released versions will be put into a new SVN directory /tags/release/1.x. They should be only used for diffing against, with no changes to those repositories.

MasterGod · Post by **MasterGod** » Wed Jan 30, 2008 1:17 pm

hybrid wrote:The actual released versions will be put into a new SVN directory /tags/release/1.x. They should be only used for diffing against, with no changes to those repositories.

But you always merge the trunk with the branch so you kinda lose the 1.4 branch. You plan on copying it and rename to 1.4.1 when you're done your TODO list?

And when I play with it should I report every single and little warning I get?

hybrid · Post by **hybrid** » Wed Jan 30, 2008 4:06 pm

Ehh, lose the 1.4 branch by merging into trunk? This is done in order to apply bug fixes made in the 1.4 branch also to trunk.
And no, there will be no 1.4.1 branch, because only the latest 1.x.y versions will be supported, hence we only need the 1.x branches.

MasterGod · Post by **MasterGod** » Wed Jan 30, 2008 4:26 pm

hybrid wrote:Ehh, lose the 1.4 branch by merging into trunk? This is done in order to apply bug fixes made in the 1.4 branch also to trunk.

I thought you merge the trunk into the branch, silly my

hybrid wrote:And no, there will be no 1.4.1 branch, because only the latest 1.x.y versions will be supported, hence we only need the 1.x branches.

So the code that is in the official release is overridden by the updates done to the 1.4 branch?
And I still don't understand, where do you keep then the 1.4.1 code? There shouldn't be a 1.4.1 directory (under /branches/releases) like 1.3.1?

hybrid · Post by **hybrid** » Wed Jan 30, 2008 10:50 pm

No. Until now, the branches/releases was used as a /tags directory. That's why versions such as 1.3.1 were kept. However, the branches directory is now used for the bugfix releases, while the released versions will be kept under /tags (which does not yet exist).