Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 20/06/2011 Michael Meeks wrote:
      We need people who in addition to coping with the tedium of reacting to
the security issues, providing fixes and testing them on older branches
- also like to write them up.
This is an important factor for people considering to upgrade their
current LibreOffice installation
      Sure - so - there is certainly a space to do this sort of thing in the
security team if you want to get stuck in ? and of course, we can't use
usual means for this - the bugs / patches are not tracked in bugzilla
etc. so it needs some manual effort.

If I can help with anything here please count me in: I would be mostly
concerned with properly informing end users about security issues and
communicating them to projects that share the same code base.

Regards,
  Andrea.


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.