On Tue, Jan 20, 2009 at 1:19 PM, Dennis P. Nikolaenko <[email protected]> wrote: > till wrote: >> >> On Sat, Jan 17, 2009 at 12:44 AM, Dennis P. Nikolaenko >> <[email protected]> wrote: >> >>> >>> Hello, >>> It is safe to assume that current trunk is to become a 0.2.1 release? Is >>> it safe to track the trunk on production server? >>> Are there any RC specific guidance for svn repository concerning >>> branches? >>> >> >> I'm not sure what you are after, can you provide more details? >> >> In general, trunk contains the most recent code. So if you want to >> stay up to date, I suggest you you use trunk to make your update >> process slightly easier. This of course doesn't rid yourself of the >> need to read CHANGELOG, maybe commit messages, etc.. >> > > I do read commits. :) > I want the fixes which will go into 0.2.1 to be applied to my installation > as soon as possible. I do not want feature additions which are to included > in 0.3 to be applied to my installation. > If bugfixing occured in /branches/release-0.2-stable and then merged into > /trunk/roundcubemail it would be easier to track svn > (/branches/release-0.2-stable) on production servers.
I see what you are saying, but I don't think we can offer LTS releases just yet. ;-( Till _______________________________________________ List info: http://lists.roundcube.net/dev/
