On Tue, Oct 8, 2013 at 7:34 AM, Artur Dryomov <artur.dryomov@gmail.com> wrote:
Hi guys,
Yep, I know tricks about commit messages, thank you for the advise anyway
;-) I still think it’s better to mark bugs as resolved when the app will be
released, let’s hope it will be done in near future.
I haven't had a chance to try out one of the daily builds* myself, but
assuming that they are running smoothly, I'd encourage the same
workflow we use with bugs in LibreOffice itself (Test fix with daily
build and mark as RESOLVED FIXED when bug is no longer present).
From a QA standpoint, standardizing our treatment of LO and SDRemote
bugs is important to keeping the QA process as simple and
straightforward as possible :-)
As Miklos mentioned above, there is some automation that adds a
comment and target to a LibreOffice bug when a patch has been pushed
for it. This information is slightly less useful for SDRemote bugs, as
our release schedule for the remote is not in lockstep with our
LibreOffice releases, but the links to daily builds may indeed be
followed to find an SDRemote daily build*.
Cheers,
--R
* http://dev-builds.libreoffice.org/daily/master/Android-ARM@24-Bytemark-Hosting/current/
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.