From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire-3.x Images
Date: Sun, 17 Feb 2019 18:28:02 +0100 [thread overview]
Message-ID: <32b82f91ff010bc2e28c6e253eb013d3fe7a5efa.camel@ipfire.org> (raw)
In-Reply-To: <1550309980.20640.4.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
Hi Jonatan,
On Sa, 2019-02-16 at 10:39 +0100, Jonatan Schlag wrote:
> Hi list,
>
> I want to inform you all that new images for IPFire-3.x are
> available.
Great thanks for your work.
>
> See this wiki page for more information:
> https://wiki.ipfire.org/devel/get_image/start
>
> I also want to use this E-Mail as a reminder that we not only have
> IPFire-2.x. I have worked with IPFire-3.x a lot and compared to
> IPFire-
> 2.x this version makes a lot of things better than IPFire-2.x
>
>
> A lot of things are very limited in IPFire-2.x. For example, the
> network in IPFire-2.x does not support IPv6.
> It is not productive to implement IPv6 in IPFire-2.x. and that's why
> we
> build IPFire-3.x from scratch.
> That means unfortunately that the effort for IPFire-2.x cannot or
> only
> partly reused iPFire-3.x.
>
> IPFire-3.x is build to support IPv6 and if we want to support this we
> need IPFire-3.x.
>
> Currently, the development work is done by Michael Tremer, Arne
> Fitzenreiten, Peter Müller, Stefan Schantl and me. My time is very
> limited at this moment and the other 4 have to work also on IPFire-
> 2.x.
>
>
> 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.
>
> A good starting point is the IPFire-3.x step by step guide here
>
>
> So thank you all for your efforts and maybe we can increase the speed
> of IPFire-3.x development a little bit. :-)
Thank you all to for your great work on IPFire-3.x.
>
> Greetings
> Jonatan
next prev parent reply other threads:[~2019-02-17 17:28 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 [this message]
2019-02-17 20:05 ` Tom Rymes
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=32b82f91ff010bc2e28c6e253eb013d3fe7a5efa.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--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