On Mon, Feb 25, 2013 at 4:40 AM, Michael Meeks <michael.me...@suse.com> wrote: > Thanks for looking into this ! so this is essentially a build > environment problem. If you want Unity integration to work - you will > need to get a build from your distributor.
Ah, okay. We definitely should make that more clear in our Release Notes. I had users trying to download the stock build because we didn't provide any other information or download/install links. > >> - Is there currently a source for builds with Unity menu integration? > > Sure - so downloading a PPA from Ubuntu should do it nicely. I believe > the same code also shipped with the last Ubuntu release as a back-port > (though I'm no expert there. I've just posted information on all of the LibreOffice PPAs I can find here: http://ask.libreoffice.org/en/question/11626/unity-integration-in-libreoffice-40-doesnt-work/ Bug is filed here: https://bugs.freedesktop.org/show_bug.cgi?id=61461 When you say last Ubuntu release, do you mean 12.10? >> - Did we miss something in testing the final rc 3? (and how can we >> prevent this type of issue next time?) > > This is basically an issue of how the feature was implemented, if you > do: > > git grep ENABLE_GMENU_INTEGRATION > > you can see the pieces that would need some abstract interface > implementing, and the bits that need splitting out into a plugin we can > dynamically load. Not a huge amount of work - a few man days perhaps. The technical details are certainly interesting, but I'd like to focus on just the issue of delivery to our users: In terms of testing, what should the QA team do to make sure that the set of features on the feature list correlates with the builds that we're pushing out the door? The simplest test I can think of is to get someone in QA to take the final rc (before release, natch!) and use the feature list as a checklist. If they can't get a particular feature to work, they file a (blocker?) bug. One way to clear the block is to just drop the feature from being listed for the release. > So - I guess we should release note this / tweak the features page to > make it clear that this is only available from distribution builds - is > that something you can chase ? Certainly. I'll try to figure out the appropriate people to contact. > Sorry about that ! > No worries -- I seem to have a knack at ferreting-out problems like these :-) It sounds like LibreOffice may be experiencing some growing pains...but I don't think growing pains are all bad. As the project gets bigger, we may need to adjust our mechanisms to account for the fact that one person or one team can't keep track of all the pieces of a release. As long as we're open-minded about how the project needs to adapt to the new challenges we face, and as long as put some checks in place to make sure that we don't keep making the same types of mistakes over and over, then I think we'll do all right :-) --R _______________________________________________ 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/