Re: [Libreoffice-qa] [ANN] LibreOffice 3.5.3 RC1 test builds available
Hi Fridrich, *, this mail never reached the l10n@ and projects@ but only the LibO-QA. Is there a problem with the mail-system or something else? Greetings k-j Am 20.04.2012 12:44, schrieb Fridrich Strba: Hi *, for the upcoming new version 3.5.3, the RC1 builds now start to be available on pre-releases. This build is slated to be first release candidate build on the way towards 3.5.3, please refer to our release plan timings here: http://wiki.documentfoundation.org/ReleasePlan#3.5_release Builds are now being uploaded to a public (but non-mirrored - so don't spread news too widely!) place, as soon as they're available. Grab them here: http://dev-builds.libreoffice.org/pre-releases/ If you've a bit of time, please give them a try report *critical* bugs not yet in bugzilla here, so we can incorporate them into the release notes. Please note that it takes approximately 24 hours to populate the mirrors, so that's about the time we have to collect feedback. The list of fixed bugs relative to 3.5.2 is here: http://dev-builds.libreoffice.org/pre-releases/src/bugfixes-libreoffice-3-5-3-release-3.5.3.1.log So playing with the areas touched there also greatly appreciated - and validation that those bugs are really fixed. Thanks a lot for your help, Fridrich (following words copyrighted by Thorsten) ___ 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/ -- Grüße k-j ___ 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/
[Libreoffice-qa] Information in Master builds About box
The new About box in branch 3.6.x is indeed extremely nice. But the version information is extremely incomplete version 3.6.0alpha0+ (Build ID: e00e693) For QA this is mostly useless. The only information you can get from this is about the core repository... Any other build using the same core will have the same info, even if all else changed. Please go back to LibreOffice 3.5.3.1 Build ID: 21cb047-d7e6025-9ba54fc-b4a51a8-f42372b We already wasted a lot of time to reach this conclusion... (I still think that some democracy would help this project) Regards, Pedro -- View this message in context: http://nabble.documentfoundation.org/Information-in-Master-builds-About-box-tp3927916p3927916.html Sent from the QA mailing list archive at Nabble.com. ___ 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/
Re: [Libreoffice-qa] Bug Triage best practice: Change or not change assignee?
Hi, On Sat, Apr 21, 2012 at 09:53:22AM +0200, Rainer Bielefeld wrote: I believe it is a very bad idea to use that field to show who should contribute additional information to the bug report, the Assigned To field should remain reserved for the competent person person who will fix the bug (or at least will manage the fixing), please also see Bugzilla Help, and I never saw an other usage for that field (and I saw a lot, you know.) Assignee is and has always been the guy who owns the bug. Thats the guy who needs to take the next action for the bug to be resolved. It doesnt make any difference if that action is changing code, bisecting, designing a new feature or providing additional info. And fixing the bug is not the changing code part -- that is very easy once the issue is identified. Additionally assigning a NEEDINFO-bug to competent person who will fix the bug makes no sense at all -- as long as the bug is NEEDINFO, there is no way to know who that would be. So I can't see that the new Wiki text describes common sense or general use, but it defines a new standard. This is how ~every other open source project manages its bugs, so its is only natural to do the same on LibreOffice. Diverting from that standard is want needs justification, not the other way around. Everyting else (like this infoprovider-nonsense) will only cause confusion. Dont do things you need to explain, do things that explain themselves. Assigning the bug back to the reporter selfevidently makes clear that he is required to take action to move the bug along. This is how bug tracker users everywhere have been working for ages: - bug needs more info to be solved = assign to reporter - bug is triaged = assign to dev - bug is fixed = assign to QA or reporter for verification - bug is verified = assign to the guy who makes the release for closing when release in the product c) Generally please do not modify existing proceedings without discussion, people like me use information in Bugzilla for queries, and every change breaks those queries and causes additional work (like this discussion, too) Please dont expect users to do things different then everywhere else because you would need to adjust your queries. d) IMHO it has become a standard that people add themselves to assigned to, this standard would be broken with the proceeding due to Wiki Its no standard at all, as it is not done like that anywhere else. So I suggest proceeding: - only set Status NEEDINFO with text request in comment, but without assignation to reporter I dont see that vital, but it usually helps to bring the point across (better than any Dear Reporter comment, although that helps too). - if info is required not from reporter ad infoprovider key word. No, that would be absolutely useless. This infoprovider nonsense is rarely used in bug trackers -- the only major user of this aberration is the Novell bugzilla, all others use the sane workflow above. It is unintuitive and uncommon and would require end users (who are the most likely infoproviders) to read the doc -- which they do not (unlike QA volunteers). In addition it dilutes the clear responsibility of the assignee field: The assignee is the current owner of the bug and the guy who is expected to move it along. That usually helps move things along or someone else will pick the bug up. You are risking lots of silent deadlocks of the assignee-thinks-infoprovider-has-to-action- this-and-infoprovider-thinks-assignee-has-to-action-this-kind by this. If there is info needed from someone else than the reporter, it is assigned to that guy. Thats common sense and how it is done everywhere else. If you want to do that different for LibreOffice, you need some serious justification. Needing to adjust queries is not one (we should never have done it like that in the first place). So please revert the wiki again and let LibreOffice handle this like pretty much every other open source project. We should get over that infoprovider-nonsense as quick as possible and good riddance. Best, Bjoern ___ 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/
Re: [Libreoffice-qa] Information in Master builds About box
On Sat, Apr 21, 2012 at 03:18:41AM -0700, Pedro wrote: For QA this is mostly useless. The only information you can get from this is about the core repository... Which is where 99% of the action is, so please refrain from exaggerations. LibreOffice 3.5.3.1 Build ID: 21cb047-d7e6025-9ba54fc-b4a51a8-f42372b I dont know why the change was done, but I think a better way would be to use 'git submodules' to include the state of the other repos in the core commit-id. Norbert was having a look at that, IIRC. @Norbert: Any conclusions from your research for gerrit wrt git submodules? (I still think that some democracy would help this project) LibreOffice is proudly founded on meritocratic foundations. Best, Bjoern ___ 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/
Re: [Libreoffice-qa] minutes of ESC call ...
On Thu, Apr 19, 2012 at 10:47 AM, Francois Tigeot ftig...@wolfpond.org wrote: Hey, On Thu, Apr 19, 2012 at 04:11:18PM +0100, Michael Meeks wrote: * tinderboxen / status (Norbert) + bytemark machine #2 + working on *BSD in virtualbox with little joy help appreciated (Norbert) + need 3x BSD virtual-boxes (ideally) I'd like to know a bit more about this item; Norbert, would you prefer real boxes if possible ? We do not have the resources for that.. but if you volunteer such a box... sure, by all means... what is needed ? - a box that do build, preferably in reasonable time... but since right now there are no *BSD tinderbox, anytime is more reasonable than +inf :-) - download the contrib/buildbot repo : http://cgit.freedesktop.org/libreoffice/contrib/buildbot/ - read http://cgit.freedesktop.org/libreoffice/contrib/buildbot/tree/README.tinbuild2 - bear in mind that the tinbuild2 script and dep and un-apologetically bash. I have zero interest in wasting time to get to the lowest common denominator. (*) - look at https://wiki.documentfoundation.org/Development/Tinderbox#List_of_registered_Tinderboxes and when the time comes, register your box there... be mindful of the naming convention... - once all that is up and running, and if there is a need/benefit to have dailies uploaded, then we will work on the next step to get the right credential to do that. Norbert (*) as tinbuild2 has never been exercised aaik on *BSD platform, there may-be some quirk. fortunately tinbuil2 has a way to do 'platform overload' look at http://cgit.freedesktop.org/libreoffice/contrib/buildbot/tree/bin/tinbuild_internals_Darwin.sh for such example for MacOS see the comment in the top of http://cgit.freedesktop.org/libreoffice/contrib/buildbot/tree/bin/tinbuild2 for some more explanations ___ 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/
Re: [Libreoffice-qa] minutes of ESC call ...
On Sat, Apr 21, 2012 at 09:09:34AM -0500, Norbert Thiebaud wrote: On Thu, Apr 19, 2012 at 10:47 AM, Francois Tigeot ftig...@wolfpond.org wrote: On Thu, Apr 19, 2012 at 04:11:18PM +0100, Michael Meeks wrote: * tinderboxen / status (Norbert) + bytemark machine #2 + working on *BSD in virtualbox with little joy help appreciated (Norbert) + need 3x BSD virtual-boxes (ideally) I'd like to know a bit more about this item; Norbert, would you prefer real boxes if possible ? We do not have the resources for that.. but if you volunteer such a box... sure, by all means... There was some talk recently in the DragonFly BSD project about providing test boxes for external developers; I'm collecting information in that context. what is needed ? - a box that do build, preferably in reasonable time... but since right now there are no *BSD tinderbox, anytime is more reasonable than +inf :-) We were thinking of Xeon E3 machines, perhaps in a mini-cluster form like this one: http://www.supermicro.nl/products/nfo/MicroCloud.cfm - download the contrib/buildbot repo : [...] and when the time comes, register your box there... be mindful of the naming convention... If boxes are finally set up, they will be DragonFly + pkgsrc packages only, special software will have to be maintained by the developers themselves. I won't be able to help on that front, my hands are already full integrating LO into pkgsrc :-/ -- Francois Tigeot ___ 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/
