On Sat, 2011-02-05 at 14:35 +0700, Samphan Raruenrom wrote:
> The intention for my original post is two fold:-
> 1) I'd like to know when/which-version will this fix land in.
Definitely 3.4 anyway. *maybe* a 3.3.X
> 2) I'd like to understand the policy for development vs. release
> branches. For
On Sat, Feb 5, 2011 at 2:09 AM, Caolán McNamara wrote:
> On Fri, 2011-02-04 at 09:44 +, Michael Meeks wrote:
> > Caolan - are you happy for this:
> > commit 6c01edfe66d6e350b20178d9ab367806d956cb46
> > Author: Caolán McNamara
> > Date: Thu Nov 11 13:31:33 2010 +
> > Resolves:
On Fri, 2011-02-04 at 09:44 +, Michael Meeks wrote:
> Caolan - are you happy for this:
>
> commit 6c01edfe66d6e350b20178d9ab367806d956cb46
> Author: Caolán McNamara
> Date: Thu Nov 11 13:31:33 2010 +
>
> Resolves: #i25247#, #i25561#, #i48064#, #i92341# CTL/Other Default
> Fon
Hi Samphan,
On Fri, 2011-02-04 at 15:38 +0700, Samphan Raruenrom wrote:
> I found that the patch to fix this bug
> https://bugs.freedesktop.org/show_bug.cgi?id=33044
> was submitted in master. However, I still see the bug in LibO 3.3 so
> the patch must landed somewhere outside the libreoffice-3-3
> For patches to make it into the now stable 3.3.0 branch it would need
> approval of 3 developers.
Well, LibreOffice 3.3.0 has already been released, so that branch is
effectively "stopped dead" now, there will be nothing more released (source
tarballs. or TDF builds) from it. Committing anyth
For patches to make it into the now stable 3.3.0 branch it would need
approval of 3 developers. Once that is done the patch is pushed to the
stable branch
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailm
I found that the patch to fix this bug
https://bugs.freedesktop.org/show_bug.cgi?id=33044
was submitted in master. However, I still see the bug in LibO 3.3 so the
patch must landed somewhere outside the libreoffice-3-3 branch.
I don't understand much about LibreOffice git branches. However, the bu
