The KDE Patchset Collection has been rebased on top of Qt 5.15.6
Cheers,
Albert
I'm sorry, I neither wanted to upset nor insult.
frameworks has 83 projects, plasma has 65 projects, release service
has 297 = 445 projects to which your blanket statement does not apply.
Their releases run on rails, that's why Nate suggests a way to
introduce additional stops, as it were.
On Thu
On Thu, Sep 8, 2022 at 8:30 AM Sven Brauch wrote:
>
> Hi,
>
> On 9/7/22 17:28, Harald Sitter wrote:
> > On Wed, Sep 7, 2022 at 5:20 PM wrote:
> >> In most projects the maintainers who'd make a release decision are the
> >> same people who triage bugs
> >
> > You quite clearly have no idea how thi
Hi,
I think all 3 of us envision very similar things, we just have different
things we think/talk about, and different understandings of Nate's
suggestion. I for example understood that Nate suggests to make bugs
matching the named criteria the *trigger* for making (or discussing) a
new relea
Hi,
I don't think Nate or anyone wants to propose a strict policy that when
X then Y has to happen. That's just not how we operate in KDE. I do
think it is valuable though to discuss and create some guidelines/shared
understanding/soft policy that maintainers can use as a reference when
making de
On 8/9/22 13:51, Nicolas Fella wrote:
Hi,
I don't think Nate or anyone wants to propose a strict policy that when
X then Y has to happen. That's just not how we operate in KDE. I do
think it is valuable though to discuss and create some guidelines/shared
understanding/soft policy that maintainer
On 9/8/22 05:51, Nicolas Fella wrote:
Hi,
I don't think Nate or anyone wants to propose a strict policy that when
X then Y has to happen. That's just not how we operate in KDE. I do
think it is valuable though to discuss and create some guidelines/shared
understanding/soft policy that maintainer
On Thursday, 8 September 2022 13:59:43 CEST, Ahmad Samir wrote:
From the git-archive manual page:
«git archive behaves differently when given a tree ID versus
when given a commit ID or tag ID. In the first case the current
time is used as the modification time of each file in the
archive. In
Bug fixes don't change the entire package, only the executable, so
why can't apps just be programmed to update themselves? There
could be precompiled binaries stored on the git repos of each project
for a few CPU architectures, or maybe the app could even recompile
itself inside /tmp since most sys
Am 08.09.22 um 20:50 schrieb samuel ammonius:
Bug fixes don't change the entire package, only the executable, so
why can't apps just be programmed to update themselves?
because outside the windows world central package management is the norm
and based on "least privileges" applications mus
> because outside the windows world central package management is the norm
> and based on "least privileges" applications must not have the
> permissions to change itself
I didn't mean a background update. I meant the user could get a dialog or
notification asking them to update, and if they press
Am 08.09.22 um 22:24 schrieb samuel ammonius:
> because outside the windows world central package management is the norm
> and based on "least privileges" applications must not have the
> permissions to change itself
I didn't mean a background update. I meant the user could get a dialog or
> and you marry upstream binaries with the distribution update-manager how?
You don't need to. The app can just check the latest bugfix for that
version on git
and install it if it isn't installed. I don't understand why you stress the
need for the
package manager to have anything to do with the u
Am 08.09.22 um 23:53 schrieb samuel ammonius:
> and you marry upstream binaries with the distribution update-manager how?
You don't need to. The app can just check the latest bugfix for that
version on git
and install it if it isn't installed. I don't understand why you stress
the need for
14 matches
Mail list logo
