On Tue, Jan 15, 2019 at 01:12:13PM +0100, Lennart Poettering wrote:
> On Di, 15.01.19 09:51, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> > On Mon, Jan 14, 2019 at 04:36:49PM +0100, Lennart Poettering wrote:
> > > I'd love to see some more CI hookup with Arch and Debian for example
> > >
Unfortunately, it likely was. I updated the webhook to also log when a tag
is ignored for the future and also changed it to use the rc tag.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On Wed, Jan 30, 2019, 12:34 PM Lennart
On Di, 29.01.19 23:31, Ryan Gonzalez (rym...@gmail.com) wrote:
> It's donotreply-systemd-...@refi64.com though I had already subscribed it
> to the mailing list with a temporary route to my own email and then turned
> off receiving messages, ... I'm guessing the whitelist would be better
>
It's donotreply-systemd-...@refi64.com though I had already subscribed it
to the mailing list with a temporary route to my own email and then turned
off receiving messages, ... I'm guessing the whitelist would be better
though?
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki
On Mo, 28.01.19 11:11, Ryan Gonzalez (rym...@gmail.com) wrote:
> From here everything looks good!
From which email address will these mails come? I figure I should
whitelist those in the mailing list access list first...
Lennart
--
Lennart Poettering, Red Hat
>From here everything looks good!
On Mon, Jan 28, 2019 at 7:39 AM Lennart Poettering
wrote:
> On Mo, 28.01.19 14:32, Lennart Poettering (lenn...@poettering.net) wrote:
>
> > On Sa, 26.01.19 16:56, Ryan Gonzalez (rym...@gmail.com) wrote:
> >
> > > I'll send you the webhook target and webhook
On Mo, 28.01.19 14:32, Lennart Poettering (lenn...@poettering.net) wrote:
> On Sa, 26.01.19 16:56, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > I'll send you the webhook target and webhook secret in a PGP-encrypted
> > email off-list (maybe overkill, but better safe than sorry).
It's set up
On Sa, 26.01.19 16:56, Ryan Gonzalez (rym...@gmail.com) wrote:
> I'll send you the webhook target and webhook secret in a PGP-encrypted
> email off-list (maybe overkill, but better safe than sorry).
>
> As a side note, the bot currently watches tags. Would it be better to watch
> releases, or
I'll send you the webhook target and webhook secret in a PGP-encrypted
email off-list (maybe overkill, but better safe than sorry).
As a side note, the bot currently watches tags. Would it be better to watch
releases, or will tags be fine for now?
On Sat, Jan 26, 2019 at 6:49 AM Lennart
On Fr, 18.01.19 20:44, Ryan Gonzalez (rym...@gmail.com) wrote:
> Okay, I created this:
>
> https://github.com/kirbyfan64/systemd-webhook
>
> and attached an image of what the messages look like. It receives new tag
> events over the webhook and sends out a message, and it also parses the
> NEWS
Lennart Poettering on Wed, 2019/01/16 19:46:
> And in case the tag matches ^v[0-9]+-pre-.*$ may be this:
>
> A new systemd ☠️ pre-release☠️ has just been tagged. Please
> download the tarball here:
>
> https://github.com/systemd/systemd/archive/$TAG.tar.gz
>
> NOTE: This is ☠️
On 18/01/19 2:29 am, Lennart Poettering wrote:
On Do, 17.01.19 07:05, Amish (anon.am...@gmail.com) wrote:
On 16/01/19 11:52 pm, Lennart Poettering wrote:
On Mi, 16.01.19 09:46, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Jérémy ROSEN wrote on 16/01/2019 08:24:
yes... adding a "this is
On Do, 17.01.19 07:05, Amish (anon.am...@gmail.com) wrote:
> On 16/01/19 11:52 pm, Lennart Poettering wrote:
> > On Mi, 16.01.19 09:46, Colin Guthrie (gm...@colin.guthr.ie) wrote:
> >
> > > Jérémy ROSEN wrote on 16/01/2019 08:24:
> > > > yes... adding a "this is the start of the freeze" tag
On Wed, Jan 16, 2019 at 07:18:15PM +0100, Lennart Poettering wrote:
> On Mi, 16.01.19 01:06, Christian Hesse (l...@eworm.de) wrote:
>
> > Lennart Poettering on Tue, 2019/01/15 20:00:
> > > Note that we don't branch releases right now. Instead when we are
> > > getting closer to a release we
On 16/01/19 11:52 pm, Lennart Poettering wrote:
On Mi, 16.01.19 09:46, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Jérémy ROSEN wrote on 16/01/2019 08:24:
yes... adding a "this is the start of the freeze" tag sounds like a low
hanging fruit... it's almost no work for the core team to do, and
All that sounds great! I'll get to work ASAP.
On Wed, Jan 16, 2019 at 12:46 PM Lennart Poettering
wrote:
> On Mi, 16.01.19 12:30, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > I'd love to do this!
>
> That'd be excellent! Thank you!
>
> > To be clear, it'd basically automatically send out a
On Mi, 16.01.19 12:30, Ryan Gonzalez (rym...@gmail.com) wrote:
> I'd love to do this!
That'd be excellent! Thank you!
> To be clear, it'd basically automatically send out a message on new
> "freeze" tags and release?
I think it could be as simple as just sending out a mail to the
mailing list
I'd love to do this!
To be clear, it'd basically automatically send out a message on new
"freeze" tags and release?
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On Wed, Jan 16, 2019, 12:22 PM Lennart Poettering On Mi, 16.01.19
On Mi, 16.01.19 09:46, Colin Guthrie (gm...@colin.guthr.ie) wrote:
> Jérémy ROSEN wrote on 16/01/2019 08:24:
> > yes... adding a "this is the start of the freeze" tag sounds like a low
> > hanging fruit... it's almost no work for the core team to do, and it
> > would be a clear signal that the
On Mi, 16.01.19 01:06, Christian Hesse (l...@eworm.de) wrote:
> Lennart Poettering on Tue, 2019/01/15 20:00:
> > Note that we don't branch releases right now. Instead when we are
> > getting closer to a release we simply don't merge PRs we don't
> > consider appropriate for the release anymore
On 1/14/19 4:36 PM, Lennart Poettering wrote:
> On Mo, 14.01.19 10:59, Jan Synacek (jsyna...@redhat.com) wrote:
>
> I'd love to see some more CI hookup with Arch and Debian for example
> (right now there is zero) or even just a git preview package set or so
> that interested people can test.
Jérémy ROSEN wrote on 16/01/2019 08:24:
> yes... adding a "this is the start of the freeze" tag sounds like a low
> hanging fruit... it's almost no work for the core team to do, and it
> would be a clear signal that the freeze period is starting...
And automated mails to the list when this happens
yes... adding a "this is the start of the freeze" tag sounds like a low
hanging fruit... it's almost no work for the core team to do, and it would
be a clear signal that the freeze period is starting...
Le mer. 16 janv. 2019 à 01:14, Christian Hesse a écrit :
> Lennart Poettering on Tue,
Lennart Poettering on Tue, 2019/01/15 20:00:
> Note that we don't branch releases right now. Instead when we are
> getting closer to a release we simply don't merge PRs we don't
> consider appropriate for the release anymore until after the
> release. Or in other words: the master branch simply
On Di, 15.01.19 10:36, Filipe Brandenburger (filbran...@google.com) wrote:
> So I think all the bits already exist somewhere and perhaps a small
> change in naming would go a long way to make these pushes smoother.
>
> If when we cut v240 from the master branch, we had called it v240-rc1
>
So I think all the bits already exist somewhere and perhaps a small
change in naming would go a long way to make these pushes smoother.
If when we cut v240 from the master branch, we had called it v240-rc1
instead, perhaps it was clear that it could take some more testing
before it was made
On 1/14/19 3:48 PM, Lennart Poettering wrote:
On Mo, 14.01.19 08:43, Dave Reisner (d...@falconindy.com) wrote:
On Mon, Jan 14, 2019 at 10:59:06AM +0100, Jan Synacek wrote:
Hi,
since v240 didn't go too well, I would like to suggest that the next one
(preferably two) release(s) are bugfix
On Tue, Jan 15, 2019 at 01:09:16PM +0100, Lennart Poettering wrote:
> On Mo, 14.01.19 11:26, Dave Reisner (d...@falconindy.com) wrote:
> > >
> > > Well, that sounds as if you want to volunteer as release engineer? ;-)
> > >
> > > Thing is, we are understaffed. I too have a wishlist of things I'd
>
On Di, 15.01.19 09:51, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> On Mon, Jan 14, 2019 at 04:36:49PM +0100, Lennart Poettering wrote:
> > I'd love to see some more CI hookup with Arch and Debian for example
> > (right now there is zero) or even just a git preview package set or so
> >
On Mo, 14.01.19 11:26, Dave Reisner (d...@falconindy.com) wrote:
> >
> > Well, that sounds as if you want to volunteer as release engineer? ;-)
> >
> > Thing is, we are understaffed. I too have a wishlist of things I'd
> > like to see done, but with only two paid full-time upstream engineers
> >
On Mon, Jan 14, 2019 at 04:36:49PM +0100, Lennart Poettering wrote:
> I'd love to see some more CI hookup with Arch and Debian for example
> (right now there is zero) or even just a git preview package set or so
> that interested people can test. Without either it's very likely that
> things break
On Mon, Jan 14, 2019 at 04:48:22PM +0100, Lennart Poettering wrote:
> On Mo, 14.01.19 08:43, Dave Reisner (d...@falconindy.com) wrote:
>
> > On Mon, Jan 14, 2019 at 10:59:06AM +0100, Jan Synacek wrote:
> > > Hi,
> > >
> > > since v240 didn't go too well, I would like to suggest that the next one
On Mon, Jan 14, 2019 at 10:36 AM Lennart Poettering
wrote:
>
> On Mo, 14.01.19 10:59, Jan Synacek (jsyna...@redhat.com) wrote:
>
> > Hi,
> >
> > since v240 didn't go too well, I would like to suggest that the next one
> > (preferably two) release(s) are bugfix only. Please, consider it.
>
> Well,
Am 14.01.19 um 16:48 schrieb Lennart Poettering:
> On Mo, 14.01.19 08:43, Dave Reisner (d...@falconindy.com) wrote:
>> systemd needs better release hygiene, not just a smattering of bugfix
>> releases. As a rolling release distro, we regularly find release-day
>> blockers. That's bad for
On Mo, 14.01.19 08:43, Dave Reisner (d...@falconindy.com) wrote:
> On Mon, Jan 14, 2019 at 10:59:06AM +0100, Jan Synacek wrote:
> > Hi,
> >
> > since v240 didn't go too well, I would like to suggest that the next one
> > (preferably two) release(s) are bugfix only. Please, consider it.
>
>
On Mo, 14.01.19 10:59, Jan Synacek (jsyna...@redhat.com) wrote:
> Hi,
>
> since v240 didn't go too well, I would like to suggest that the next one
> (preferably two) release(s) are bugfix only. Please, consider it.
Well, one thing I'd really like to see happen is a bit more feedback
*before* the
On Mon, Jan 14, 2019 at 10:59:06AM +0100, Jan Synacek wrote:
> Hi,
>
> since v240 didn't go too well, I would like to suggest that the next one
> (preferably two) release(s) are bugfix only. Please, consider it.
systemd needs better release hygiene, not just a smattering of bugfix
releases. As a
Hi,
since v240 didn't go too well, I would like to suggest that the next one
(preferably two) release(s) are bugfix only. Please, consider it.
Thank you,
--
Jan Synacek
Software Engineer, Red Hat
___
systemd-devel mailing list
38 matches
Mail list logo
