hello,
as i am currently not happy with the rc1 in svn, i wonder which version should be used to stay close to the "next to be stable" version.
trunk? branches/devel-vnext?
please provide some information on the list and/or the wiki to clear things up :)
kind regards, raoul bhatia
Hi Raoul!
On 6/5/07, Raoul Bhatia [IPAX] r.bhatia@ipax.at wrote:
hello,
as i am currently not happy with the rc1 in svn, i wonder which version should be used to stay close to the "next to be stable" version.
RC is an opensource project, and opensource means that when you are not happy with it, you write a patch and submit.
rc1 is an efford to release more often - if you follow the list the last official release of RC had been a pretty long time ago.
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.
For (even) more info: http://trac.roundcube.net/trac.cgi/wiki/Plugin_API_Draft
Regards, Till
Everyone is not a developer!
Do you build a new engine and install it if you own a car and not happy
with it?
I guess everyone is an engineer too :)
On Tue, 05 Jun 2007 21:59:58 +1000, till klimpong@gmail.com wrote:
Hi Raoul!
On 6/5/07, Raoul Bhatia [IPAX] r.bhatia@ipax.at wrote:
hello,
as i am currently not happy with the rc1 in svn, i wonder which version should be used to stay close to the "next to be stable" version.
RC is an opensource project, and opensource means that when you are not happy with it, you write a patch and submit.
rc1 is an efford to release more often - if you follow the list the last official release of RC had been a pretty long time ago.
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.
For (even) more info: http://trac.roundcube.net/trac.cgi/wiki/Plugin_API_Draft
Regards, Till
On 6/5/07, Chris Fordham chris@xhost.com.au wrote:
Everyone is not a developer! Do you build a new engine and install it if you own a car and not happy with it? I guess everyone is an engineer too :)
Of course I do! 8)
Just kidding.
Well, I assumed (maybe wrong) that he's on top of things when he got as far as SVN. Anyway, feedback is always helpful and "not happy with" is a bit too vague. I think everyone here is very open to suggestions, and of course patches. :D
Cheers, Till
sorry that i did not clearly outline my intension.
till wrote:
Hi Raoul!
On 6/5/07, Raoul Bhatia [IPAX] r.bhatia@ipax.at wrote:
hello,
as i am currently not happy with the rc1 in svn, i wonder which version should be used to stay close to the "next to be stable" version.
RC is an opensource project, and opensource means that when you are not happy with it, you write a patch and submit.
rc1 is an efford to release more often - if you follow the list the last official release of RC had been a pretty long time ago.
basically i wanted to know
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.
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.
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?
kind regards, raoul bhatia
ps: yes, i know what opensource is, yes, i know how subversion is working (at least the basics) and yes, i know that the directory structure can be abused :)
On 6/5/07, Raoul Bhatia [IPAX] r.bhatia@ipax.at wrote:
- 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.
I think rc1 is a fixed/closed branch (since it's been released). All patches are applied to trunk and devel-vnext. But correct me if I am wrong.
Maybe Thomas can comment later on.
Till
Raoul Bhatia [IPAX] wrote:
basically i wanted to know
- 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.
- 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
-
Chris Fordham -
Raoul Bhatia [IPAX] -
Thomas Bruederli -
till