Hey all, could someone explain what the idea is with the svn branches? I see Alec is doing updates of 0.5 from trunk patches. Does this mean there is a supported 0.5 branch, that will include most bugfixes from trunk? If one wanted to follow an svn repo to stay current, would you suggest following a branch, or trunk?
Regards,
Cor _______________________________________________ List info: http://lists.roundcube.net/dev/ BT/aba52c80
On 16.02.2011 13:08, Cor Bosman wrote:
I see Alec is doing updates of 0.5 from trunk patches. Does this mean there is a supported 0.5 branch, that will include most bugfixes from trunk?
Yes, I'll update this branch until 0.5.2 release, because there were some fixes worth a release. I don't think we'll have more releases in 0.5 and I don't like to have it up-to-date later.
All this is only because we cannot make a stable release directly from trunk now.
If one wanted to follow an svn repo to stay current, would you suggest following a branch, or trunk?
Trunk now is a playground for new features. In my opinion these features are not ready and may change. I'd say that trunk is in an alpha state now.
El mié, 16-02-2011 a las 13:08 +0100, Cor Bosman escribió:
Hey all, could someone explain what the idea is with the svn branches? I see Alec is doing updates of 0.5 from trunk patches. Does this mean there is a supported 0.5 branch, that will include most bugfixes from trunk? If one wanted to follow an svn repo to stay current, would you suggest following a branch, or trunk?
Regards,
Cor _______________________________________________ List info: http://lists.roundcube.net/dev/ BT/5456fcb4
Hi Cor
few days ago, i asked about the same to the list... because i needed to apply a bugfix to 0.5.0 that (by that time) will be applied to 0.5.1; but 0.5.1 wasn't released yet.
patches to bugfixes are applied to trunk, then they are tagged to a new version. So you want to follow trunk for development and testing. If you want to implement a stable roundcube use a stable release, but for developement and bleading edge bug fixing, you need to follow trunk (WARNING: it will include new bugs too!!)
regards!
El mié, 16-02-2011 a las 13:32 +0100, A.L.E.C escribió:
On 16.02.2011 13:08, Cor Bosman wrote:
I see Alec is doing updates of 0.5 from trunk patches. Does this mean there is a supported 0.5 branch, that will include most bugfixes from trunk?
Yes, I'll update this branch until 0.5.2 release, because there were some fixes worth a release. I don't think we'll have more releases in 0.5 and I don't like to have it up-to-date later.
All this is only because we cannot make a stable release directly from trunk now.
If one wanted to follow an svn repo to stay current, would you suggest following a branch, or trunk?
Trunk now is a playground for new features. In my opinion these features are not ready and may change. I'd say that trunk is in an alpha state now.
Alec:
i think it would be a great idea to document this procedure on the wiki at least, so you don't get asked every time. (there were only few weeks since i asked basically the same question).
regards
Well, your question was not quite the same. You asked how to get the branch. I know how to get it. Im asking a more fundamental question, what is the status of that branch. Alec answered that now. I would personally really like it if this was officially the default into the future. A bug-maintained release branch, separate from the trunk.
Cor
List info: http://lists.roundcube.net/dev/ BT/aba52c80
El mié, 16-02-2011 a las 13:52 +0100, Cor Bosman escribió:
Well, your question was not quite the same. You asked how to get the branch. I know how to get it. Im asking a more fundamental question, what is the status of that branch. Alec answered that now. I would personally really like it if this was officially the default into the future. A bug-maintained release branch, separate from the trunk.
Cor
you don't have any hay to get the branch "0.5.2-devel", that was what i was asking, and it is in the same spirit of your question (at least i was trying to do the same as you, get a stable release with new bugfixes applied, and not a trink/alpha-state release)
i think we should need to have some kind of policy, to release a new "stable+bugfixes" release every fixed time, say a week or so, so the bugfixes get a stable/usable release more often.
more and more people are using RC in production, so it would be great to have this supported "stable" release. At least i am pursuing that goal. Right now i'm digging into tickets which blocks stable releases and try to understand the problem and fix them, or help devs to fix them.
may be somebody could have write permission to svn and "backport" the bugfixes to a stable tree, some kind of dev model like are using the kernel developers with a policy like "trunk first" so we don't have duplicated work. I will do that work for a few days on my SVN to see how difficult it is and to see if i have de knowledge to do that work and how it mixes with my day to day work.
regards..
List info: http://lists.roundcube.net/dev/ BT/aba52c80
-
A.L.E.C -
Carlos Pasqualini -
Cor Bosman