Why is a release branch changed?

Discuss about anything related to the Irrlicht Engine, or read announcements about any significant features or usage changes.
Post Reply
CuteAlien
Admin
Posts: 9736
Joined: Mon Mar 06, 2006 2:25 pm
Location: Tübingen, Germany
Contact:

Why is a release branch changed?

Post by CuteAlien »

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?
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
MasterGod
Posts: 2061
Joined: Fri May 25, 2007 8:06 pm
Location: Israel
Contact:

Post by MasterGod »

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
Image
Dev State: Abandoned (For now..)
Requirements Analysis Doc: ~87%
UML: ~0.5%
hybrid
Admin
Posts: 14143
Joined: Wed Apr 19, 2006 9:20 pm
Location: Oldenburg(Oldb), Germany
Contact:

Post by hybrid »

No, the branches will be versions which are going to be releases or which will bring patch level updates to releases. I'll update a tags directory at top-level in order to get access to the released versions from SVN.
Post Reply