public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire-3.x Images
Date: Mon, 18 Feb 2019 12:14:45 +0000	[thread overview]
Message-ID: <E58B8FB2-F3FB-4CB8-B53D-4A50EB7A4D12@ipfire.org> (raw)
In-Reply-To: <6415AB88-61B5-4C12-A537-B5D0B2B6F04B@rymes.com>

[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]

Hi,

I do not really want to bring down the excitement, but IPFire 3 is no where near ready for production.

This image is rather the status from last autumn when we had our last developer summit. Since then, literally nothing has happened in regard of IPFire 3. There is just no time to work on that.

As Jonatan has said, all of our time is very limited and we are putting every minute into IPFire 2 to at least keep that running well. Unfortunately that has become more time in the past since I have the feeling that we are getting less and less feedback from testers and so on.

The time that we do spend on IPFire 3 is rather on regrouping and finding the spot where we stopped working because too much time passes between those two points in time. So far we have failed to continue working on it a little bit every single day…

But, there is also good news… I always tend to talk about the downsides of all of this, but actually there is more positive things to say about IPFire 3:

* We have an amazing build system - which is not bug-free but doing a much better job than what we have in IPFire 2

* Networking is working really well. It is powerful, has loads of features. We just need to round it off a little bit.

* The OS is modern, small and faster than IPFire 2.

If you want to toy around with the networking, here is the documentation: https://man-pages.ipfire.org/network/

Please report any bugs, please talk about IPFire 3. I am happy to help out and answer questions :)

-Michael

> On 17 Feb 2019, at 20:05, Tom Rymes <trymes(a)rymes.com> wrote:
> 
> 
>> 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


  reply	other threads:[~2019-02-18 12:14 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
2019-02-18 12:14     ` Michael Tremer [this message]
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=E58B8FB2-F3FB-4CB8-B53D-4A50EB7A4D12@ipfire.org \
    --to=michael.tremer@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