[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Re: adding a QA responsibility to the release team??
From: Giorgos Tsiapaliwkas <terietor () gmail ! com>
Date: 2011-09-19 11:51:24
Message-ID: CAODYyLaNiXsBjQHJD0J_bwP7rM8pBvQjKjyEWhFeDJ0q0ov1Uw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 18 September 2011 21:21, Rex Dieter <rdieter@fedoraproject.org> wrote:
>
> There's already a week between initial tarball creation (for packagers) and
> official release. Are you proposing making this longer?
In this week,the tarballs are being created?If so,we don't have a
week,because when the tarballs are out the packagers will get the non-fixed
code.
In general,i was thinking that the timeline of 2 weeks(before the tarball
creation,could solve the issue).
> or... some other workflow?
Actually,this is a big discussion and i don't know how wise that would
be.But in KDE 5.0.Should we have to consider the release of the frameworks?
(Not the for the entire KDE,just for the frameworks part).
2 additional comments:
> * I think it may be unwise to conflate release engineering with QA, they
> really are 2 distinct items (though obviously interelated).
>
Yes you have right,but the time that i wrote the mail,i couldn't think a
better word.And i don't think that a QA team could be established inside
KDE,
since KDE doesn't exist as a monolithic community but from subcommunities.
Also a QA team some time in her lifetime would affect the release cycle and
the change of the release cycle have been discussed a lot of times in the
past and it has been decided not to change.Moreover a QA team would have
some policy which will be against the "habit" of the subcommunities,and
our authority system is based in the relationship between us and not in our
access stuff,since we all have the same access.
> * I'm also of a mind there's no special need for additional bugzilla
> components... in the past, when/if regressions or blockers identified in our
> "week", they were dealt-with appropriately.
>
I propose the bugzilla compoments only as a solution for taking down the
issues.But its really not a big matter.
On 18 September 2011 21:34, Ian Monroe <ian@monroe.nu> wrote:
> Seems like the basic issue is that the (official) release + a week or
> two is usually more stable then the release. But that's because the
> release spurred people to find bugs and fix them.
this means that we have to reconsider our release timelines,and find a
better way?
I stand for yes on that one.
--
Tsiapaliwkas Giorgos (terietor)
KDE Developer
terietor.gr
[Attachment #5 (text/html)]
<br><br><div class="gmail_quote">On 18 September 2011 21:21, Rex Dieter <span \
dir="ltr"><<a href="mailto:rdieter@fedoraproject.org">rdieter@fedoraproject.org</a>></span> \
wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;">
There's already a week between initial tarball creation (for packagers) and \
official release. Are you proposing making this \
longer?</blockquote><div><br></div><div><div>In this week,the tarballs are being \
created?If so,we don't have a week,because when the tarballs are out the \
packagers will get the non-fixed code.</div> <div>In general,i was thinking that the \
timeline of 2 weeks(before the tarball creation,could solve the \
issue).</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;"> or... some other \
workflow?</blockquote><div><br></div><div>Actually,this is a big discussion and i \
don't know how wise that would be.But in KDE 5.0.Should we have to consider the \
release of the frameworks?</div><div> (Not the for the entire KDE,just for the \
frameworks part).</div><div><br></div><blockquote class="gmail_quote" style="margin:0 \
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> </blockquote><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;">
2 additional comments:<br>
* I think it may be unwise to conflate release engineering with QA, they really are 2 \
distinct items (though obviously \
interelated).<br></blockquote><div><br></div><div>Yes you have right,but the time \
that i wrote the mail,i couldn't think a better word.And i don't think that a \
QA team could be established inside KDE,</div> <div>since KDE doesn't exist as a \
monolithic community but from subcommunities.<br>Also a QA team some time in her \
lifetime would affect the release cycle and the change of the release cycle have been \
discussed a lot of times in the</div> <div>past and it has been decided not to \
change.Moreover a QA team would have some policy which will be against the \
"habit" of the subcommunities,and</div><div>our authority system is based \
in the relationship between us and not in our access stuff,since we all have the same \
access.</div> <div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
* I'm also of a mind there's no special need for additional bugzilla \
components... in the past, when/if regressions or blockers identified in our \
"week", they were dealt-with appropriately.<br></blockquote> \
<div><br></div><div> I propose the bugzilla compoments only as a solution for taking \
down the issues.But its really not a big matter.</div></div><div><br></div>On 18 \
September 2011 21:34, Ian Monroe <span dir="ltr"><<a \
href="mailto:ian@monroe.nu">ian@monroe.nu</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; \
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); \
border-left-style: solid; padding-left: 1ex; "> <div class="im">Seems like the basic \
issue is that the (official) release + a week or</div>two is usually more stable then \
the release. But that's because the<br>release spurred people to find bugs and \
fix them.</blockquote> <div><br></div><div>this means that we have to reconsider our \
release timelines,and find a better way?</div><div>I stand for yes on that one. \
</div><div><br></div>-- <br>Tsiapaliwkas Giorgos (terietor)<br>KDE Developer<br> \
<br><a href="http://terietor.gr" target="_blank">terietor.gr</a><br>
_______________________________________________
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