[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Re: kde-runtime does not finds kactivites
From: Anne-Marie Mahfouf <annemarie.mahfouf () free ! fr>
Date: 2012-06-10 8:48:19
Message-ID: 4FD45F53.4000203 () free ! fr
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 06/10/2012 10:32 AM, Andreas Pakulat wrote:
> Hi,
>
> On Sun, Jun 10, 2012 at 1:05 AM, Manuel Tortosa <manutortosa@gmail.com
> <mailto:manutortosa@gmail.com>> wrote:
>
> El Diumenge, 10 de juny de 2012, a les 00:52:28, Andreas Pakulat
> va escriure:
>
> Ok, great, then please let the kactivities team know about this.
> The release-team cannot really do anything about it (other than
> trying to reach the kactivities team). Basically the same goes to
> all the rest of your mails, if things don't build, the first
> person to speak to is the corresponding development
> team/maintainer so such problems get fixed asap.
>
> Actually as been fixed already by Allen in git.
>
> I don't know what do you have against sending mails for warning
> about the issues i am finding on compiling the tarballs, i just
> try to be constructive helping to fix a release before actually
> making the tarballs public and preventing some bigger problems.
>
> I don't have a problem with reporting broken tarballs or the fact that
> there are build-problems to the release-team. But I think the way
> you're doing it right now is not very efficient for the release-team,
> its harder to keep track of the overall state when the information is
> spead across multiple mail threads.
>
> If this is the release-team mailing list the release team should
> be updated about the problems about the upcomming release, really
> i don't understand you at all.
>
> I think it would be more efficient to send the build-problems to the
> corresponding module-dev-lists immediately and assemble a list of
> things over the time of a day or two and send the assembled list to
> the release-team. I think that would make it easier to follow up on
> the states once they're fixed.
>
> Feel free to create a filter in your mail program to ignore my
> messages, you are a kde coder, i am a kde translator, we both are
> part of kde and we both should ensure the quiality of the release.
>
> Not much of a coder these days unfortunately :) Sorry, didn't want to
> stop your efforts or diminish them, I'll be a bit clearer next time I
> raise concerns.
>
> Andreas
>
We will need to sort out how to efficiently report these problems (this
is something that is noted and that will be addressed, as part of the
new Quality Team effort). Until then, I'll forward to the relevant
mailing lists the problems that are reported, hoping the relevant people
will address them. We face an unusual number of problems this time due
to the lack of manpower to manage the releases and we'll try to address
all that for the next time.
Best regards,
Anne-Marie
[Attachment #5 (text/html)]
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 06/10/2012 10:32 AM, Andreas Pakulat wrote:
<blockquote
cite="mid:CAExHGmS+6skwTCy27NG8_Cjd9tvxE-7CHHT-_COTokAuqfnMzw@mail.gmail.com"
type="cite">Hi,<br>
<br>
<div class="gmail_quote">On Sun, Jun 10, 2012 at 1:05 AM, Manuel
Tortosa <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:manutortosa@gmail.com" target="_blank">manutortosa@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:'DejaVu
Sans';font-size:9pt;font-weight:400;font-style:normal">
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">El
Diumenge, 10 de juny de 2012, a les 00:52:28, Andreas
Pakulat va escriure:<br>
</p>
<div class="im">
<p
style="margin-top:12px;margin-bottom:12px;margin-left:40px;margin-right:40px;text-indent:0px">Ok,
great, then please let the kactivities team know about
this. The release-team cannot really do anything about
it (other than trying to reach the kactivities team).
Basically the same goes to all the rest of your mails,
if things don't build, the first person to speak to is
the corresponding development team/maintainer so such
problems get fixed asap.</p>
<p
style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
</div>
<p
style="margin-top:12px;margin-bottom:12px;margin-left:40px;margin-right:40px;text-indent:0px">Actually
as been fixed already by Allen in git.</p>
<p
style="margin-top:12px;margin-bottom:12px;margin-left:40px;margin-right:40px;text-indent:0px">I
don't know what do you have against sending mails for
warning about the issues i am finding on compiling the
tarballs, i just try to be constructive helping to fix a
release before actually making the tarballs public and
preventing some bigger problems.</p>
</div>
</blockquote>
<div>I don't have a problem with reporting broken tarballs or
the fact that there are build-problems to the release-team.
But I think the way you're doing it right now is not very
efficient for the release-team, its harder to keep track of
the overall state when the information is spead across
multiple mail threads.</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:'DejaVu
Sans';font-size:9pt;font-weight:400;font-style:normal">
<p
style="margin-top:12px;margin-bottom:12px;margin-left:40px;margin-right:40px;text-indent:0px"> If
this is the release-team mailing list the release team
should be updated about the problems about the upcomming
release, really i don't understand you at all.</p>
</div>
</blockquote>
<div>I think it would be more efficient to send the
build-problems to the corresponding module-dev-lists
immediately and assemble a list of things over the time of a
day or two and send the assembled list to the release-team. I
think that would make it easier to follow up on the states
once they're fixed.</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:'DejaVu
Sans';font-size:9pt;font-weight:400;font-style:normal">
<p
style="margin-top:12px;margin-bottom:12px;margin-left:40px;margin-right:40px;text-indent:0px">Feel
free to create a filter in your mail program to ignore my
messages, you are a kde coder, i am a kde translator, we
both are part of kde and we both should ensure the
quiality of the release.<br>
</p>
</div>
</blockquote>
<div>Not much of a coder these days unfortunately :) Sorry,
didn't want to stop your efforts or diminish them, I'll be a
bit clearer next time I raise concerns.</div>
<div><br>
</div>
<div>Andreas</div>
</div>
<br>
</blockquote>
We will need to sort out how to efficiently report these problems
(this is something that is noted and that will be addressed, as part
of the new Quality Team effort). Until then, I'll forward to the
relevant mailing lists the problems that are reported, hoping the
relevant people will address them. We face an unusual number of
problems this time due to the lack of manpower to manage the
releases and we'll try to address all that for the next time.<br>
<br>
Best regards,<br>
<br>
Anne-Marie<br>
<br>
</body>
</html>
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic