[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-windows
Subject:    Re: Updating raptor; kde-windows workflow
From:       Laszlo Papp <lpapp () kde ! org>
Date:       2012-12-14 6:14:28
Message-ID: CAOMwXhM8i_OufX3fe0udU1Mv1WD_ji1riEjuR==QPuPZ726Msw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


>
> Well, the background of my question is this: I don't have a build tree of
> master, and I don't intend to get one, either. I'm just trying to do what's
> necessary to have my own project running on Windows, and to fix the bugs
> that
> affect it, or that I happen to stumble upon, along the way.
>
> I do not intend to dive head first into the KDE on Windows project. I
> already
> have my own pet project, thank you. Building several branches, and possibly
> even with several compilers per branch is a no-go to me.
>

Projects usually have CI for several tier testing. The KDE Windows project
also has several builds run automatically on a server:

http://www.winkde.org/pub/kde/ports/win32/dashboard/


> So that's why I'm asking about policy, here: If I cannot (be convinced to)
> test a patch in master, but I think it should go there, how should I
> proceed.
>

The problem is that you think, but you do not know. I understand your good
intention and I appreciate that, but unfortunately that is not alway enough
if it causes breakages for others.


> Reviewboard? This list?
>

You will need to find another contributor somehow who will know. The
generic rules applies here: irc, mailing list, review board, and so forth.

I do not personally have time to check your write up now, but thank you for
your contribution.

Laszlo

[Attachment #5 (text/html)]

<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Well, the background of my question \
is this: I don&#39;t have a build tree of<br> master, and I don&#39;t intend to get \
one, either. I&#39;m just trying to do what&#39;s<br> necessary to have my own \
project running on Windows, and to fix the bugs that<br> affect it, or that I happen \
to stumble upon, along the way.<br> <br>
I do not intend to dive head first into the KDE on Windows project. I already<br>
have my own pet project, thank you. Building several branches, and possibly<br>
even with several compilers per branch is a no-go to \
me.<br></blockquote><div><br>Projects usually have CI for several tier testing. The \
KDE Windows project also has several builds run automatically on a server:<br><br><a \
href="http://www.winkde.org/pub/kde/ports/win32/dashboard/">http://www.winkde.org/pub/kde/ports/win32/dashboard/</a><br>
  </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

So that&#39;s why I&#39;m asking about policy, here: If I cannot (be convinced \
to)<br> test a patch in master, but I think it should go there, how should I \
proceed.<br></blockquote><div><br>The problem is that you think, but you do not know. \
I understand your good intention and I appreciate that, but unfortunately that is not \
alway enough if it causes breakages for others.<br>  </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Reviewboard? This list?<br></blockquote><div><br>You will \
need to find another contributor somehow who will know. The generic rules applies \
here: irc, mailing list, review board, and so forth.<br><br>I do not personally have \
time to check your write up now, but thank you for your contribution.<br> \
<br>Laszlo<br></div></div>



_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows


[prev in list] [next in list] [prev in thread] [next in thread]