Raoul Bhatia [IPAX] wrote: > > basically i wanted to know > > 1) which branch/tag to switch to so i a) have got the current patches > and b) do not stray far away from the to-come -rc2/-stable versions > so i can c) test, debug and write bugreports and even patches.
To test and report bugs, please always use the trunk version. > > 2) which tag/branch is meant for which purpose as it is not clear and > there is no easy-to-find explanation on the website. having this > information would allow me (and perhaps others) to figure out which > directory to "svn switch" to. If someone wants to run the SVN version, the trunk is your choice. Branches are either for development (to not disturb the trunk in case you have large changesets) or for "public" releases in order to create important patches that need to be published before the next release. > >>> trunk? branches/devel-vnext? >> >> As for a basic explaination of "devel-vnext" - I am trying to refactor >> the code as I see and implement a PLUGIN api. I restarted my work last >> week and it's based on rc1. If you have additions (requests, patches) >> etc., please let me know. > > thank you for this explanation - what are the other branches and trunk > meant for? which of the branches is closed and should not be worked on? > which is open for development? Branches beginning with 'devel-' are for development and should only be touched by the according developers. Other branches are named the same as previous releases and are meant for the reason stated above. Hope this helps ~Thomas
