From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: IPFire-3.x Images
Date: Sun, 17 Feb 2019 15:05:55 -0500 [thread overview]
Message-ID: <6415AB88-61B5-4C12-A537-B5D0B2B6F04B@rymes.com> (raw)
In-Reply-To: <32b82f91ff010bc2e28c6e253eb013d3fe7a5efa.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
> On Feb 17, 2019, at 12:28 PM, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> On Sa, 2019-02-16 at 10:39 +0100, Jonatan Schlag wrote:
>>
>> As stated time is limited and 4 persons are not enough to build
>> IPFire-
>> 3.x. To push the development of IPFire-3.x it would be cool If
>> everybody would thinking about working on this next major version
>> too.
> It might be helpful to know a little more about the insides which kind
> of work needs to be currently done and who is working on what.
I’d also like to have a better feel for what are the items that need attention before 3.x can be released. It has long been that “IPFire 3 is coming soon", but it’s unclear what work is needed where to get to the next step.
Tom
next prev parent reply other threads:[~2019-02-17 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 9:39 Jonatan Schlag
2019-02-17 17:28 ` ummeegge
2019-02-17 20:05 ` Tom Rymes [this message]
2019-02-18 12:14 ` Michael Tremer
2019-03-17 17:17 ` Jonatan Schlag
2019-03-21 4:12 ` DJ Lucas
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=6415AB88-61B5-4C12-A537-B5D0B2B6F04B@rymes.com \
--to=trymes@rymes.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