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

List:       kde-release-team
Subject:    Re: Frameworks 6 alpha
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2023-11-01 8:47:32
Message-ID: CA+XidOHA42ot_T+16yT0DDAzTdPcNrAgrButmSJg3387hit8+Q () mail ! gmail ! com
[Download RAW message or body]

On Wed, Nov 1, 2023 at 8:42 AM Jonathan Riddell <jr@jriddell.org> wrote:

> We chatted about the alpha release due next Wednesday in the Frameworks
> meeting today.
>
> From my notes:
>
> - Frameworks would like do be part of this release
>
> - Nico F, Alex S, David E are release spods
>
> - There's not been any work on doing the tooling.  There's a desire to
> move to releaseme for tooling.  Jonathan uses this plus a load of
> supporting scripts for Plasma and will look at adapting that for Frameworks
> and come up with a proposal
>
> - Plasma would like to take over release of plasma-framework, kwayland and
> kactivities and that presumably means also kactivities-stats.  There was
> discussion on the problem of moving the gitlab entries for this while 5
> releases are still ongoing so it's probably best to just leave that for now.
>

Having the repositories being subject to two different sets of rules is
going to be quite painful - as quite a few systems assume that something in
frameworks/* is a Framework.
This is the case for CI (in the branch-rules, the seed jobs, etc), API
Documentation and a few other places.

It is much easier to make something non-Frameworks look like a Framework,
than it is to make something that is classified as Frameworks (but isn't
actually one) not be seen as one.
(ie. the rules we have are inclusionary not exclusionary)

I'd be in favour of saying they need to be moved from frameworks/ to
plasma/ in preparation for this.


>
> - oxygen-icons5 tar should be renamed oxygen-icons (again probably leave
> gitlab repo renaming until later)
>
- We didn't discuss it but kirigami2 tar should also be renamed to kirigami
>

Not sure why we need to delay renaming the repository?


>
> Does that seem right?
>
> Anything else?
>
> Jonathan
>

Thanks,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Wed, Nov 1, 2023 at 8:42 AM Jonathan Riddell \
&lt;<a href="mailto:jr@jriddell.org">jr@jriddell.org</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>We \
chatted about the alpha release due next Wednesday in the Frameworks meeting \
today.</div><div><br></div><div>From my notes:<br></div><div><br></div><div>- \
Frameworks would like do be part of this release</div><div><br></div><div>- Nico F, \
Alex S, David E are release spods</div><div><br></div><div>- There&#39;s not been any \
work on doing the tooling.   There&#39;s a desire to move to releaseme for tooling.   \
Jonathan uses this plus a load of supporting scripts for Plasma and will look at \
adapting that for Frameworks and come up with a proposal</div><div><br></div><div>- \
Plasma would like to take over release of  plasma-framework, kwayland and kactivities \
and that presumably means also kactivities-stats.   There was discussion on the \
problem of moving the gitlab entries for this while 5 releases are still ongoing so \
it&#39;s probably best to just leave that for \
now.</div></div></blockquote><div><br></div><div>Having the repositories being \
subject to two different sets of rules is going to be quite painful - as quite a few \
systems assume that something in frameworks/* is a Framework.</div><div>This is the \
case for CI (in the branch-rules, the seed jobs, etc),  API Documentation and a few \
other places.</div><div><br></div><div>It is much easier to make something \
non-Frameworks look like a Framework, than it is to make something that is classified \
as Frameworks (but isn&#39;t actually one)  not be seen as one.</div><div>(ie. the \
rules we have are inclusionary not exclusionary)</div><div><br></div><div>I&#39;d be \
in favour of saying they need to be moved from frameworks/ to plasma/ in preparation \
for this.</div><div>  </div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><br></div><div>- oxygen-icons5 tar should be renamed oxygen-icons \
(again probably leave gitlab repo renaming until later)  \
</div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>- \
We didn&#39;t discuss it but kirigami2 tar should also be renamed to \
kirigami</div></div></blockquote><div><br></div><div>Not sure why we need to delay \
renaming the repository?</div><div>  </div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Does that seem \
right?</div><div><br></div><div>Anything \
else?</div><div><br></div><div>Jonathan</div></div></blockquote><div><br></div><div>Thanks,</div><div>Ben \
</div></div></div>



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