From: "Kienker, Fred" <fkienker@at4b.com>
To: development@lists.ipfire.org
Subject: RE: IPFire 2.23 - Core Update 135 is ready for testing
Date: Thu, 22 Aug 2019 11:22:16 -0400 [thread overview]
Message-ID: <H000006e0051b6ef.1566487336.mail.at4b.net@MHS> (raw)
In-Reply-To: <70B22414-B889-45CD-81BA-22B87277BCFB@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]
Thanks again for doing this Michael!
In addition to using the ISO to test installation, we use the change log
as a checklist of items to test for proper operation. Makes testing more
effective and less time consuming.
Best regards,
Fred
-----Original Message-----
From: Michael Tremer <michael.tremer(a)ipfire.org>
Sent: 22 August, 2019 10:39
To: Mentalic <mentalic(a)cox.net>; development
<development(a)lists.ipfire.org>
Subject: Re: IPFire 2.23 - Core Update 135 is ready for testing
Great! I was just going to check :)
> On 22 Aug 2019, at 15:00, Mentalic <mentalic(a)cox.net> wrote:
>
> Found it!
>
> Regards
> Wayne
>
> -----Original Message-----
> From: Michael Tremer [mailto:michael.tremer(a)ipfire.org]
> Sent: Wednesday, August 21, 2019 9:37 AM
> To: Mentalic
> Subject: Re: IPFire 2.23 - Core Update 135 is ready for testing
>
> Hi,
>
> I just checked. The builders are running on both compiling next (which
always has priority).
>
> The will get to master as soon as next is done :)
>
> -Michael
>
>> On 21 Aug 2019, at 15:31, Mentalic <mentalic(a)cox.net> wrote:
>>
>> Michael
>>
>> Saw the posts and looking for 135 now. Only thing I can find is the
"next".
>>
>> Regards
>> Wayne
>>
>>
>> -----Original Message-----
>> From: Michael Tremer [mailto:michael.tremer(a)ipfire.org]
>> Sent: Tuesday, August 20, 2019 2:04 PM
>> To: Mentalic
>> Subject: Re: IPFire 2.23 - Core Update 135 is ready for testing
>>
>> Hi,
>>
>> I hope you have seen my email on the list that the nightly builds for
the master branch are coming back:
>>
>>
https://lists.ipfire.org/pipermail/development/2019-August/006194.html
>>
>> -Michael
>>
>>> On 19 Aug 2019, at 18:34, Mentalic <mentalic(a)cox.net> wrote:
>>>
>>> Just cannot find a link nor the location to download an iso of 135.
>>>
>>> Regards
>>> Wayne
>>>
>>> -----Original Message-----
>>> From: Michael Tremer [mailto:michael.tremer(a)ipfire.org]
>>> Sent: Monday, August 19, 2019 12:24 PM
>>> To: Mentalic
>>> Cc: Arne Fitzenreiter
>>> Subject: Re: IPFire 2.23 - Core Update 135 is ready for testing
>>>
>>> Hi,
>>>
>>> What do you mean?
>>>
>>> The master branch? We are currently not building that.
>>>
>>> Do you want/need it?
>>>
>>> -Michael
>>>
>>>> On 19 Aug 2019, at 16:08, Mentalic <mentalic(a)cox.net> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> Looked for the new 135 update but dont see it in the nightly
tree.
>>>>
>>>> Regards
>>>> Wayne
>>>
>>
>
prev parent reply other threads:[~2019-08-22 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001301d558f2$0356d590$0a0480b0$@net>
2019-08-22 14:39 ` Michael Tremer
2019-08-22 15:22 ` Kienker, Fred [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=H000006e0051b6ef.1566487336.mail.at4b.net@MHS \
--to=fkienker@at4b.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox