Re: [Libreoffice] development summary: year 2011, week 24

2011-07-07 Thread Petr Mladek
Cor Nouws píše v Pá 01. 07. 2011 v 11:16 +0200:
 Hi John, Petr,
 
 John LeMoyne Castle wrote (24-06-11 11:38)
 
  The intention is to make as few changes as possible in lo-commit-stat while
  getting to where a Weekly Development Summary wiki page is generated easily.
 
 For 'external use' it would be most helpful if there is a output 
 comparing subsequent releases.
 
 But if In understood the information correctly, that can be easily 
 accomplished with giving the right parameters?

Yes, the list of changes between releases is easy. You just need to get
the summary between the tags:

   bin/lo-commit-stat --log-suffix=release-x.y.z . tag1..tag2

I suggest the following steps:

# make sure that you have all tags
./g fetch --tags
# find the last tags for the release, e.g. 3.4.0 and 3.4.1
git tag | grep libreoffice-3.4.0
git tag | grep libreoffice-3.4.1
# produce the summary
bin/lo-commit-stat --log-suffix=release-3.4.1 .
libreoffice-3.4.0.2..libreoffice-3.4.1.3

It produces log file with plain text. John is working on the wiki
output.

See also  bin/lo-commit-stat --help for more details.

Hmm, we might want to create the tag libreoffice-3.4.0-final that will
be identical to the last used rc tag. It would make these queries
easier.


Best Regards,
Petr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] development summary: year 2011, week 24

2011-07-01 Thread Cor Nouws

Hi John, Petr,

John LeMoyne Castle wrote (24-06-11 11:38)


The intention is to make as few changes as possible in lo-commit-stat while
getting to where a Weekly Development Summary wiki page is generated easily.


For 'external use' it would be most helpful if there is a output 
comparing subsequent releases.


But if In understood the information correctly, that can be easily 
accomplished with giving the right parameters?




I generated two wiki pages:
http://wiki.documentfoundation.org/Development/2010/MasterWeek39  --  and


A page like that would be really useful information for those wanting to 
know about special bugs/fixes.


Kind regards,

--
 - Cor
 - http://nl.libreoffice.org

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] development summary: year 2011, week 24

2011-06-28 Thread Petr Mladek
Petr Mladek píše v Po 27. 06. 2011 v 20:06 +0200:
 John LeMoyne Castle píše v Pá 24. 06. 2011 v 02:38 -0700:
  ** Please Note: Many of the commits listed for this week were actually
  merged into master as late as Spring 2011. The commits listed here have a
  patch date within week 39 of 2010. **
 
 Great catch!
 
  In light of this snafu created by late submit and necessarily later merge, I
  will again approach/expose/question my confusion by attacking the utility of
  wiki-dev-sum as I had originally intended it: I don't think the present
  wiki-dev-sum script helps fill in the missing wiki summaries...
 
 You might try to play with git log options. There are various options
 about filtering the merged commits.

I have discussed it with Kendy. He suggested to try something like:

git log --after=start_date --before=end_date origin/branch@{end_date}

e.g.

git log --before=2010-11-10 --after=2010-11-01 origin/master@{2010-11-10}

where origin/branch@{end_date} selects a commit in the master
branch around the given date. You could even use time, e.g.
origin/master@{2010-11-10 00:00:00}. See man gitrevisions.

Then the after/before options should select only commits around the
defined one. The defined one should be from the original branch. It
should not count commits that were later merged from other branches.

I havn't tested it, though.


Best Regards,
Petr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] development summary: year 2011, week 24

2011-06-27 Thread Petr Mladek
Hi John,

I am happy that your are working on it and have some nice results.

John LeMoyne Castle píše v Pá 24. 06. 2011 v 02:38 -0700:
 Hi Petr, 

 Sorry about the confusion I created on a previous summary thread in my
 brainstorming attempt to get development summaries into the wiki.  
 I know it was bad because it even seemed to infect your response a little.  

I am not aware of any confusion. It is normal to have different views on
something and exchange ideas :-)

 This should be clearer.  
 
 Here is an example of a wrapper (wiki-dev-sum) 
 http://nabble.documentfoundation.org/file/n3103449/wiki-dev-sum wiki-dev-sum 

OK, if I understand it correctly, it has the following purpose:


1. purpose is to generate the statistic for all active branches.

   Well, this might make sense. I actually use a similar
   wrapper that updates the repository to a given branch
   and get the last changes. It is written in bash. Please,
   find it attached.

   It would be great to pass the list of branches via the
   command line options.

   You could use --option=param even in bash. You could get
   the param via:

  param=`echo $arg | sed s/--option=//`

 
   Note that the situation is a bit complicated. I have separate
   git tree for master, libreoffice-3-4* and libreoffice-3-3*
   branches because they are not compatible:

 + libreoffice-3-3 uses build repo as the
   toplevel dir ; bootstrap repo is in
   build/clone/bootstrap.

 + libreoffice-3-4 uses bootstrap as the top level
   module

 + master is going to be switched to single git
   repository, see
http://wiki.documentfoundation.org/Development/One_Git_Conversion


   Well, it might be interesting to move this functionality to
   the lo-commit-stat script. You could add new option:

  --branches=branch[,...]

   I created extra wrapper because it was easier to do it in
   bash and I wanted a quick solution ;-)


2. purpose is to define the start and end day according to the
   week.

  It would be great to have it in the lo-commit-stat script. It
  is very useful also for generating the plain log for E-mail.

  Could you please add --year=year --week=week --last-week
  options int lo-commit-stat? You could do something like:

 if (defined $last_week) {
$year = get_this_year();
$week = get_this_week();
 }

 if (defined $week  ! defined $year) {
$year = get_this_year();
 }

 if (defined $week  defined $year) {
die Error: Do not define extra git arguments together
with --year, --week, --this-week options
if (@git_args);
@git_args = get_git_args_for_feek($year, $week);
$log_suffix = week-$year-$week unless (defined
   $log_suffix)
 }

   You need not process these options in the wiki-dev-sum
   wrapper. It might be enough to pass them to the
   lo-commit-stat script.
   
3. Is there any other purpose of the wiki-dev-sum script?


BTW1: I was not sure what the --echo option means. Such functionality is
usually enabled via the option --verbose ;-)

Also the following negative condition looks a bit cryptic:

(! defined $echo) || show_call

I think that 

(defined $verbose)  show_call(...)

or

show_call(...) if (defined $verbose);

is slightly better readable ;-)


BTW2: Using /tmp/commit-log-$branch-wiki.log is a bit dangerous because
any user could write to this file (security hole, write access
problems). I suggest to create a temporary directory
under /tmp/wiki-dev-sum-XX and put files under it. The question is
why you need the temp file at all. It would be better if lo-commit-stat
generates the right file to the final location and no postprocessing is
needed.


 that operates on a slightly modified lo-commit-stat script (basically just
 adds --wiki format option)
 http://nabble.documentfoundation.org/file/n3103449/lo-commit-stat
 lo-commit-stat 

It looks great. I am just not sure about the change:

--- cut ---
-(defined $top_dir) || die Error: top directory is not defined\n; 
+if (! defined $top_dir) { 
+   usage(); 
+   exit; 
+} 
--- cut ---

I think that the user might be confused why it prints help and what is
the exact problem.


 The intention is to make as few changes as possible in lo-commit-stat while
 getting to where a Weekly Development Summary wiki page is generated easily. 

Do not hesitate to do more changes in lo-commit-stat ;-)

 I attached full scripts and not patches because the pair is brand new and
 neither fully