Digest #166

Thu Feb 3 13:51:08 CET 2011

Thank you, Danny. We all owe you a lot! :)

Cheers,

mutlu

--- Danny Allen <danny at commit-digest.org> schrieb am Do, 3.2.2011:

> Von: Danny Allen <danny at commit-digest.org>
> Betreff: Re: Digest #166
> An: "Marco Krohn" <marco.krohn at googlemail.com>
> CC: "digest" <digest at kde.org>
> Datum: Donnerstag, 3. Februar, 2011 03:56 Uhr
> Hi all,
> Still working on the Git commits issue, has taken up 2 of
> my evenings now!
> KDE sysadmins didn't tell me that the format of the emails
> was changing, and it's taking me a while to catch all the
> cases.
> 
> This should be fixed on Thursday.
> I have temporarily disabled everyone's access to the commit
> review interface as a precaution, as I can't guarantee the
> state of the commits there at the moment (but no work will
> have been lost so don't worry :))
> 
> With cutting down commits included in the Digest, think 5%
> to 10% depending on the week - basically, all commits should
> just be interesting, that's the primary criteria.
> 
> I have read all the emails about various technical issues
> and most will be fixed on Thursday evening.
> 
> Also, I will look over #164 and get it published on
> Thursday.
> 
> Cheers,
> Danny
> 
> 
> ----- Original Message -----
> From: "Marco Krohn" <marco.krohn at googlemail.com>
> To: "digest" <digest at kde.org>
> Cc: "Danny Allen" <danny at commit-digest.org>
> Sent: Wednesday, 2 February, 2011 7:47:22 PM
> Subject: Re: Digest #166
> 
> Hi Danny,
> 
> Thanks, I can see the git commits coming. However, some of
> the show
> "1970-01-01" as date. Also the "oldest" git commits seem to
> be from
> 1/31/2011, but I would expect that we missed older git
> commits
> starting around 1/25/2011.
> 
> Have a nice day,
>   Marco
> 
> 
> On Wed, Feb 2, 2011 at 10:58 AM, Danny Allen <danny at commit-digest.org>
> wrote:
> > Hi all,
> > I've found the reason why Git commits have stopped
> being imported into Enzyme: the format of the commit message
> mails has been changed! Grrrr.
> > This has taken all the time I set aside to work on
> Enzyme to fix (fix will go up tonight) - i'll try and do an
> extra evening of work to do some other stuff I wanted too.
> >
> > With regards to the next Digest issue: if it can be
> brought up to where it is ready for release, i'll look it
> over tonight and get it published.
> > Going forward, I think we can have other people
> actually releasing the issues too - I think you're ready for
> it! :)
> >
> > Danny
> >
> >
> >
> > ----- Original Message -----
> > From: "Danny Allen" <danny at commit-digest.org>
> > To: "mutlu_inek" <mutlu_inek at yahoo.de>
> > Cc: "digest" <digest at kde.org>
> > Sent: Monday, 31 January, 2011 4:47:01 PM
> > Subject: Re: Digest #166
> >
> > Good stuff everyone!
> > I'm going to spend some time on features/bug fixes
> tonight for Enzyme to address some of the issues brought up
> over the past week (and my own todo list! :))
> >
> > Cheers,
> > Danny
> >
> >
> > ----- Original Message -----
> > From: "mutlu_inek" <mutlu_inek at yahoo.de>
> > To: "digest" <digest at kde.org>
> > Sent: Monday, 31 January, 2011 4:44:03 PM
> > Subject: Re: Digest #166
> >
> > Hi team,
> >
> > Digest #166 is taking shape. I have injected and
> formatted the feature article and also formatted the still
> not fully completed synopsis. I hope I will have the time to
> go through the commits once more during the coming days...
> if Marco doesn't beat me to it. You are doing loads of work,
> kudos! Anyways, judging from the state of this digest, I
> would say it is definitely ready to go some time this week.
> >
> > Digests #164 and #165 also seem to look great! We
> really are catching up.
> >
> > Cheers,
> >
> > mutlu
> >
> >
> > --- Marco Krohn <marco.krohn at googlemail.com>
> schrieb am Mi, 26.1.2011:
> >
> >> Von: Marco Krohn <marco.krohn at googlemail.com>
> >> Betreff: Re: Digest #166
> >> An: "digest" <digest at kde.org>
> >> Datum: Mittwoch, 26. Januar, 2011 14:56 Uhr
> >> Ok, thanks Danny!
> >>
> >> Another feature wish:
> >> * Sometimes I would like to add some context or a
> link to a
> >> commit
> >> message. For example, the message "Added
> libalkimia to
> >> build system"
> >> does not mention what "libalkimia" actually is (I
> have
> >> _not_ selected
> >> the message for the CD). In these (few cases) I
> would like
> >> to add a
> >> comment for our readers like "libalkimia is a
> library with
> >> common
> >> classes and functionality used by finance
> applications for
> >> the KDE
> >> SC".
> >> * Also sometimes I would like to give a reason
> (for the CD
> >> team) why I
> >> selected a specific commit message, e.g., I found
> the
> >> message "Someone
> >> somewhere on the internet said this would crash, I
> had to
> >> prove him
> >> wrong :-)" from David Faure quite funny.
> >>
> >> The feature wishes are not high priority, though.
> I am now
> >> working on
> >> reducing the backlog a bit ...
> >>
> >> Have a great day,
> >>   Marco
> >>
> >> On Wed, Jan 26, 2011 at 12:56 PM, Danny Allen
> <danny at commit-digest.org>
> >> wrote:
> >> > It could be difficult to get a good commit
> overview as
> >> I get less information from Git and its all
> decentralised,
> >> but i;ll investigate and see what I can come up
> with!
> >> >
> >> > Cheers,
> >> > Danny
> >> >
> >> >
> >> > ----- Original Message -----
> >> > From: "Marco Krohn" <marco.krohn at googlemail.com>
> >> > To: "digest" <digest at kde.org>
> >> > Sent: Wednesday, 26 January, 2011 11:46:31
> AM
> >> > Subject: Re: Digest #166
> >> >
> >> > Yes, there are many commits now ... actually
> too many.
> >> I'll see what I
> >> > can do about that ...
> >> >
> >> > By the way this also fixed part (1) as I see
> more
> >> interesting commits
> >> > now. Do you think it is possible to link the
> messages
> >> to the commits
> >> > such that we can see the details, i.e., which
> files
> >> were modified
> >> > which code changed, again?
> >> >
> >> > Thanks and best regards,
> >> >  Marco
> >> >
> >> > On Mon, Jan 24, 2011 at 6:14 PM, Danny Allen
> <danny at commit-digest.org>
> >> wrote:
> >> >> Hi Marco,
> >> >> 1) Yep, I knew this would happen:
> basically, with
> >> these decentralised Git repositories people feel
> more free
> >> to commit and also that their commits won't really
> be seen,
> >> so they tend to be less informative in the commit
> message.
> >> Also, Git allows people to work offline and push
> at a later
> >> date, so people commit more often and with less
> thought than
> >> they used to. Obviously this causes issues for us,
> i'll have
> >> to think about how to improve this...
> >> >>
> >> >> 2) You had filters set on your account
> (/kdevelop,
> >> /koffice, /kdelibs, /kdebase) so i've removed them
> for now,
> >> there should be commits to review now?! :)
> >> >>
> >> >> Cheers,
> >> >> Danny
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Marco Krohn" <marco.krohn at googlemail.com>
> >> >> To: "digest" <digest at kde.org>
> >> >> Sent: Monday, 24 January, 2011 4:30:38
> PM
> >> >> Subject: Re: Digest #166
> >> >>
> >> >> On Mon, Jan 24, 2011 at 3:36 PM, Danny
> Allen
> >> <danny at commit-digest.org>
> >> wrote:
> >> >>
> >> >>> 1) Git commits were only recently
> introduced,
> >> and I noticed a sharp fall in SVN commits over
> this time as
> >> projects moved quickly to Git
> >> >>
> >> >> I noticed that git commit messages tend
> to be less
> >> informative and
> >> >> interesting than svn commits. It this
> because a)
> >> we do not see all git
> >> >> commits (because many of them happen
> locally) and
> >> the merge message is
> >> >> not interesting or (b) developers do not
> care to
> >> comment their commits
> >> >> (c) something else?
> >> >>
> >> >>> 2) Commits have only been reviewed in
> Enzyme
> >> up to 10th January - i'll try and send an email to
> inactive
> >> reviewers to get this to a more realtime activity.
> Also, if
> >> anyone here can help out, that'd be really welcome
> too!
> >> >>
> >> >> Interesting, I just double-checked: my
> review page
> >> is still empty...
> >> >>
> >> >> Have a nice day,
> >> >>  Marco
> >> >>
> _______________________________________________
> >> >> Digest mailing list
> >> >> Digest at kde.org
> >> >> https://mail.kde.org/mailman/listinfo/digest
> >> >>
> >> >
> _______________________________________________
> >> > Digest mailing list
> >> > Digest at kde.org
> >> > https://mail.kde.org/mailman/listinfo/digest
> >> >
> >> _______________________________________________
> >> Digest mailing list
> >> Digest at kde.org
> >> https://mail.kde.org/mailman/listinfo/digest
> >>
> >
> >
> > _______________________________________________
> > Digest mailing list
> > Digest at kde.org
> > https://mail.kde.org/mailman/listinfo/digest
> > _______________________________________________
> > Digest mailing list
> > Digest at kde.org
> > https://mail.kde.org/mailman/listinfo/digest
> > _______________________________________________
> > Digest mailing list
> > Digest at kde.org
> > https://mail.kde.org/mailman/listinfo/digest
> >
> _______________________________________________
> Digest mailing list
> Digest at kde.org
> https://mail.kde.org/mailman/listinfo/digest
> 