[Libreoffice-qa] [ANNOUNCE] Branch libreoffice-4-3-2 and Tag libreoffice-4.3.2.1 created

2014-09-11 Thread Christian Lohmaier
Hi all,

The tag libreoffice-4.3.2.1 (AKA 4.3.2 RC1) and the corresponding
branch libreoffice-4-3-2 have been created.
The branch will be used for fine tuning of the 4.3.2 release. (there
is one additional RC planned)

The following rules apply:

+ preferably just translation or blocker fixes
+ only cherry-picking from libreoffice-4-3 branch
+ 2 additional reviews needed; 2nd reviewer pushes
+ no regular merges back to anything

The 'libreoffice-4-3' branch is still active and will be used for the
4.3.3 bugfix release. Please read more at
   http://wiki.documentfoundation.org/ReleasePlan/4.3#4.3.2_release
   http://wiki.documentfoundation.org/Development/Branches
   http://wiki.documentfoundation.org/Release_Criteria

Now, if you want to switch your clone to the branch, please do:

./g pull -r
./g checkout -b libreoffice-4-3-2 origin/libreoffice-4-3-2

To checkout the tag, use

./g fetch --tags
./g checkout -b tag-libreoffice-4.3.2.1 libreoffice-4.3.2.1

Hopefully it will work for you :-)  Most probably, you will also want to
do (if you haven't done it yet):

git config --global push.default tracking

When you do git push with this, git will push only the branch you are
on; e.g. libreoffice-4-3-2 when you have switched to it.  This will
save you some git shouting at you.

Linux distro packages might find source tarballs at
http://dev-builds.libreoffice.org/pre-releases/src/
They will soon be available from the official page together with the builds.

Attached is the list of changes against 4.3.1 RC2 (4.3.1 final)

Happy hacking,
Christian
+ OOXML import: Respect table background properties a bit more (bnc#480256) [Matúš Kukan]
+ fix reading even/odd page breaks from .docx (bnc#519228) [Luboš Luňák]
+ I can't remove a path in AutoText dialog (bnc#529470) [Tor Lillqvist]
+ avoid opening embedded OLE object as text (bnc#648251) [Tor Lillqvist]
+ sd: check that master page matches when setting parent style (bnc#708518) [Michael Stahl]
+ we need the proper alpha mask (bnc#719994) [Tor Lillqvist]
+ copy first-header-footer test from ww8 to ooxml (bnc#751077) [Luke Deller]
+ make changing table text color in impress always work (bnc#770711) [Matúš Kukan]
+ copy first-header-footer test from ww8 to ooxml (bnc#780843) [Luke Deller]
+ fix reading a .doc that has frame anchored to the end of page (bnc#787942) [Luboš Luňák]
+ better algorithm to find placeholder shape. (bnc#821916) [Matúš Kukan]
+ let's not even try to export invalid chart objects. (bnc#822170) [Kohei Yoshida]
+ if number type is not set, skip numbering (bnc#822347) [Tomaž Vajngerl]
+ PPTX import: Properly show data labels in percent format. (bnc#862510) [Matúš Kukan]
+ DOCX import: handle w:hideMark table cell property (bnc#865381) [Miklos Vajna]
+ improved handling of placeholder shapes (bnc#880448) [Matúš Kukan]
+ set the date time mode to non-fixed after the import is done. (bnc#885548) [Kohei Yoshida]
+ do not set TextAutoGrowHeight for vertical text. (bnc#887227) [Matúš Kukan]
+ fix build, Unchecked dynamic_cast (coverity#1209547) [Caolán McNamara]
+ allow passing FilterOptions via cli (fdo#36313) [Tomas Hlavaty]
+ DOCX import: list styles don't support automatic updates (fdo#38414) [Miklos Vajna]
+ mac Keyboard shortcut Option key ko in Customize dialog (fdo#39477) [Julien Nabet]
+ don't remove 'edit' pop-up menu entry from form in design mode (fdo#44081) [Lionel Elie Mamane]
+ write OOXML externalReferences, externalLinks, (fdo#45286) [Eike Rathke]
+ don't loop autosave if userautosave fails (fdo#46635) [Maxim Monastirsky]
+ pyuno: fix deadlock in Runtime::any2PyObject() (fdo#46678) [Michael Stahl]
+ disable the Automatically currency unless already used (fdo#48110) [Eike Rathke]
+ make Draw use paper size when printing (fdo#63905) [Eilidh McAdam]
+ TextField in table should use same formatting as floating TextField (fdo#67615) [Lionel Elie Mamane]
+ avoid crashing on Accellerator in poorly initialized context (fdo#69162) [Norbert Thiebaud]
+ don't loop autosave if userautosave fails (fdo#71625) [Maxim Monastirsky]
+ sub-grid shouldn't be allowed as 0 (fdo#77516) [Caolán McNamara]
+ (+dup File crashes while opening. (fdo#78906) [Umesh Kadam]
+ labels are truncated (fdo#79227) [Caolán McNamara]
+ make generic autocorr files (German/Spanish/Italian) (fdo#79276) [Julien Nabet]
+ check for empty slots' valid NULL pointer, (fdo#79441) [Eike Rathke]
+ use \highlightN instead of \chcbpatN in RTF import and export (fdo#79599) [nrb...@gmail.com]
+ add 'Save a Copy' to Calc/Impress/Draw (LO4.3-Branch) (fdo#79917) [Heiko Scheidt]
+ handle autocomplete with dot in formula name, (fdo#80058) [Markus Mohrhard]
+ fix the check whether the window is active on OS X. (fdo#80474) [Jan Holesovsky]
+ bad default value (0) for the number of rows (fdo#80534) 

Re: [Libreoffice-qa] BSA 2.0 - First Draft of Concept Questions

2014-09-11 Thread Jay Philips
On 09/11/2014 04:40 AM, Joel Madero wrote:
 
 On 09/10/2014 04:32 PM, Jay Philips wrote:
 Hey Joel,

 Yes i think a step by step process is a nice user friendly way to go.
 When Calligra Words crashed on me, their step by step bug report was fun
 to go through.

 About your doc, here are some thoughts.

 1) I'm assuming that many users coming to the BSA are coming through the
 Help  Send Feedback menu item and the libreoffice version number will
 be provided through this link, so the first question should be for the
 user to enter in the libreoffice version they are using and that the
 list be automatically set to the version present in the link. After the
 user selects his version, or simply clicks ok as his version is already
 selected, then either it takes him to the 'please upgrade your version'
 notice or step 2.
 Not sure I'm following this.

About suggestion 1, when a user goes to Help  Send Feedback, its a link
that looks like this 
http://www.libreoffice.org/get-help/feedback/?LOversion=4.4.0.0.alpha0LOlocale=en-USLOmodule=StartModule
 and in the LOversion part of the url, that is the libreoffice version
number, so that should be used to automatically set it in the drop down.

Forgot to mention that in the 'Reproducible Steps:' step, the module
selection should be there as well, and the link mentioned above will
also help in its auto selection.

 2) I think we should ask them to download the latest stable/still
 version if they are running an EOL version or if they are on an older
 version of the current stable/still.
 I strongly disagree - if it's fixed in Fresh - that is sufficient 95% of
 the time (ie. we're not going to go dig through to find a backport if
 stable isn't fixed). The idea here is to lessen the load on QA, not to
 increase, and this would increase it. Else they download stable, confirm
 that their minor bug is still in it, report, we find that it's fixed in
 Fresh, and just set to WFM. This is not the ideal situation. They can
 always download stable - we'll just direct them to the Fresh page, if
 they go to the Stable branch, fine.

 3) Step 2 should be asking the user for his operating system, with that
 being automatically selected by means of javascript through the user's
 browser agent (florian already has that code).
 Takes more work to implement. Florian's thing is a concept, not
 currently workable without additional steps by user.

The main point here is that step 2 should be the user choosing his
operating system and the javascript can assist with that selection. If
the javascript is never implemented, that is also not a problem for this
to be step 2. This should be very easy to implement and Liongold or I
can assist with it with Florian's code.

 3) Step 3 should be asking them if this is a bug report or an
 enhancement request and this step should be skipped if the user clicks
 the two different links on 
 http://www.libreoffice.org/get-help/feedback/ , as presently they link
 to the same page.
 Again this takes more work and coding WITHIN LibreOffice but I'm not
 opposed to the idea.

I'm assuming cloph or Liongold can easily make this minor change and
worst case, i'll can do it if i get the keys. :D

 4) Step 4 is only for users who are submitting a bug report and that
 asks them if this bug had happened in a previous version and shows the
 version list with the first entry being something like i'm not sure.
 Yup agreed.

 5) I think it would be great to have bug priority set by simple yes/no
 questions, but think that is the job of the QA team to set that feature,
 and a simple yes/no question of whether it hangs/crashes is sufficient
 for BSA bug reporters.
 This would just set a quasi setting that could always be changed, I
 disagree that we can't ask users to help us. Else - the reality is we
 don't have the time to even triage bugs let alone deal with prioritizing
 them. A rough idea through 4 questions seems fine and if users are
 unhappy answering 4 simple questions, I have little patience for taking
 my time to triage their bugs.
 
 Best,
 Joel
 
 ___
 List Name: Libreoffice-qa mailing list
 Mail address: Libreoffice-qa@lists.freedesktop.org
 Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
 Problems? 
 http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
 Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
 List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
 
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/