Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline for
releases (and branch it even more for child workspaces), but I don't
know if the main codeline also includes the newer features and
On Sat, May 31, 2008 at 11:25 AM, Clytie Siddall
[EMAIL PROTECTED] wrote:
Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline for
releases (and branch it even more for child workspaces), but I
On 31/05/2008, at 6:36 PM, Ain Vagula wrote:
On Sat, May 31, 2008 at 11:25 AM, Clytie Siddall
[EMAIL PROTECTED] wrote:
Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline
for
releases (and
Hi Clytie,
For example, we have been testing the DEV300 codeline, which will
eventually become the OpenOffice.org 3.0 release. The BEA300 codeline so
far has contained the 3.0 Beta m1 and m2 builds.
you can see the DEV300 codeline as TRUNK for all development that is
done for versions
On 31/05/2008, at 6:36 PM, Ain Vagula wrote:
On Sat, May 31, 2008 at 11:25 AM, Clytie Siddall
[EMAIL PROTECTED] wrote:
Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline
for
releases (and
On 31/05/2008, at 6:51 PM, Joost Andrae wrote:
Hi Clytie,
For example, we have been testing the DEV300 codeline, which will
eventually become the OpenOffice.org 3.0 release. The BEA300
codeline so far has contained the 3.0 Beta m1 and m2 builds.
you can see the DEV300 codeline as TRUNK
