Releases in 3 months

[Michael Jansen]

On Thursday, July 11, 2013 01:06:59 PM Sebastian Kügler wrote:
> On Tuesday, July 09, 2013 12:53:50 Philip Muskovac wrote:
> > On Monday 08 July 2013 18:59:12 Michael Pyne wrote:
> > > On Mon, July 8, 2013 17:45:10 Philip Muskovac wrote:
> > > > What would at least make my life easier here would be a way to easily
> > > > get a
> > > > list of all patches that were applied to a stable release (esp. when
> > > > someone bothers to backport a fix after the last point release is
> > > > out).
> > > > The only way to do that, that I found so far, is filtering out mails
> > > > from
> > > > kde- commits, which is neither very easy nor reliable.
> > > 
> > > I'm assuming a variant of 'git log --oneline v4.x.y..KDE/4.x' is not
> > > adequate  for some reason? Admittedly sometimes we need to be reminded
> > > to
> > > push the release tags but that seems like it should work for all modules
> > > in the kde.org-released software.
> > 
> > Good point, that's at least more reliable than filtering mail.
> > It still requires me to have a local clone of some 150 repositories and
> > some extra handling for the svn branch so I would prefer something that
> > doesn't require me to pull all of those just to get some statistics. I'll
> > play with that though, thanks!
> 
> If that's the concern, we can certainly run such a script on one of the
> build machines, and it probably only needs someone puppy-eyeing a sysadmin
> to install it.
> 
> Cheers,

Why not make a job on the jenkins/hudson machine(s)? They can be parametrized (you give the 
labels) or the relevant ones are added and run regularly. Would perhaps increase the visibility of 
those machines a bit.
-- 
Michael Jansen
http://michael-jansen.biz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20130712/30c834d0/attachment.htm>