I just noticed that the release branch for 1.4 still seems to be in development. I'm somewhat confused by that. Isn't the point of release-branches to have the sources for important release versions available? How can I do patches against a certain release version if that version is still changed after the release? Or how can I check if a bug did happen in a certain version? Should I remember the specific svn version number and always do a rollback for such situations?
Maybe this is rather usual - I must admit that I don't know how that sort of thing is typically handled. But it seems to me that it would make more sense to create immediately after a release for example an 1.4.1 folder which will get the patches for 1.4 instead of still working on that branch. Or is this some restriction on sourceforge because of the harddisc space needed for more branches?
Why is a release branch changed?
Why is a release branch changed?
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
I'm not sure how much help it would be but read the last two posts here:
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=26872
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=26872