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


Hi Petr, 
I was thinking about cranking through the past emails like this one and
generating Development Summary pages on the wiki by hand.  
Then I discovered the related easy hack --
http://wiki.documentfoundation.org/Development/Easy_Hacks_Complete_List#Weekly_summary_.2F_Release_summary
  

I am now looking at adding a -w=<yyyy-ww> (weekly wikify) option to
lo-commit-stat that would generate a suitable weekly wiki page entire.  Then
only the page creation is manual labor that I can look forward to. I see
from the wiki that the bug number handling could be more powerful, there may
be ways to look more deeply at the commits and the resulting bug numbers on
the Wiki should be links back to the related bug @ xxx.  There is also the
extraction of commits common to all repos. 
I assume that you wrote lo-commit-stat... 
Anything else that should go into -wikify?
Any internal tips?  
What is standard week boundary here (i.e. Monday->Sunday)? 
Can I put a (c) TDF header on it?

Thanks,
LeMoyne

--
View this message in context: 
http://nabble.documentfoundation.org/development-summary-year-2011-week-23-tp3058199p3060991.html
Sent from the Dev mailing list archive at Nabble.com.

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.