hi guys,
I've retested and migrated most of the mab4.2 to the mab4.3 list.
m
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change
On Mon, 08 Dec 2014 11:45:59 +0100, Tommy wrote:
hi guys,
I've retested and migrated most of the mab4.2 to the mab4.3 list.
of the original 83 mab4.2 issue that were still open on the 4.2.x END OF
LIFE (november 19th) a few were marked as RESOLVED WORKSFORME
see list here:
https://bugs.free
On Mon, 08 Dec 2014 11:45:59 +0100, Tommy wrote:
hi guys,
I've retested and migrated most of the mab4.2 to the mab4.3 list.
of the original 83 mab4.2 issue that were still open on the 4.2.x END OF
LIFE (november 19th) a few were marked as RESOLVED WORKSFORME
see list here:
https://bugs.free
Hi,
On Saturday, 2014-12-06 21:18:05 -0500, Robinson Tryon wrote:
> * If a bug is fixed on the Master branch (or in Fresh), but is still
> present on Fresh/Still, it can be helpful to tag the bug and bibisect
> it, in addition to resolving it as WFM. I'll send out a separate email
> to the QA lis
Hi all,
The tag libreoffice-4.4.0.0.beta2 (AKA 4.4.0 Beta2) on the corresponding
branch libreoffice-4-4 has been created last week.
The branch will be used for fine tuning of the 4.4 codeline.
Branch-off marks feature freeze, see
https://wiki.documentfoundation.org/ReleasePlan/4.4#4.4.0_release f
On Mon, 08 Dec 2014 13:38:58 +0100, Eike Rathke wrote:
Hi,
On Saturday, 2014-12-06 21:18:05 -0500, Robinson Tryon wrote:
* If a bug is fixed on the Master branch (or in Fresh), but is still
present on Fresh/Still, it can be helpful to tag the bug and bibisect
it, in addition to resolving it
On Mon, 08 Dec 2014 11:52:59 +0100, Tommy wrote:
here's the list of the last mab4.2 "survivors":
https://bugs.freedesktop.org/showdependencytree.cgi?id=65675&hide_resolved=1
good to see that we were able to reduce the number to just 5:
54398: FILESAVE: DOC files created in LO los
Hey Tommy,
Any FDO cleanup - if you cc me on it I'll address the issue. Only a few
people have rights as of now.
>
>>
> I see that somebody did the clean up but forgot to remove just the
> 4.1.6.1 rc
Resolved :) Thanks!
Best,
Joel
___
List Name: Libreo
Dear Community,
The Document Foundation is pleased to announce the second Beta
release of LibreOffice 4.4.0. The upcoming 4.4.0 will be the ninth
major release of LibreOffice, coming with a bunch of new features
beside the usual bugfixes.
The Beta2 can be installed alongside the stable version, s
Dear Community,
The Document Foundation is pleased to announce the second release
candidate of LibreOffice 4.2.8. The upcoming 4.2.8 is an additional
bugfix release to finish off the 4.2 codeline
line. Feel free to give it a try instead of 4.2.7.
The release is available for Windows, Linux and Ma
On Mon, Dec 8, 2014 at 3:43 PM, Tommy wrote:
> if we don't mark it as FIXED WFM how do we distinguish a NEW bug without a
> fix from a NEW bug which is FIXED in master but not yet present in the
> stable branch?
Sure -- and this highlights a granularity problem we have with current
bug reports: W
On Tue, 09 Dec 2014 05:29:23 +0100, Robinson Tryon
wrote:
How do we decide which bugs to tag? I suggest that for now we only tag
backportRequests if the bug was reported against an active Still or
Fresh branch.
So to put that into context with our current builds, here's my proposal:
I
12 matches
Mail list logo
