Linux NILFS development
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Cc: admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org
Subject: Re: Ready for production ?
Date: Fri, 17 Oct 2008 04:15:30 -0700	[thread overview]
Message-ID: <200810170415.30644.phillips@phunq.net> (raw)
In-Reply-To: <20081017.150912.86504903.ryusuke-sG5X7nlA6pw@public.gmane.org>

On Thursday 16 October 2008 23:09, Ryusuke Konishi wrote:
> Hi,
> 
> On Wed, 15 Oct 2008 22:44:38 +0200, David Arendt wrote:
> > Hi,
> > 
> > One thread with exactly this subject was started 12 months ago. So it
> > would be interested to make the point once again.
> > 
> > I am actually using nilfs2 on a volume where data integrity isn't
> > important and didn't have any problems until now.
> > 
> > So what would the developers say ? Is it ready for production ?
> 
> It's up to you. ;)
> 
> We aim to apply nilfs to commercial products, and we use it daily for
> laptops, desktop machines and a shared storage server (samba server).
> 
> However, we think still it needs further testing, debugging efforts,
> performance improvement, enhancement of administrative tools, and so
> forth.  At least for the stability, it was dramatically improved in
> the past year.

I don't think you should hold back from merging with mainline just
because of stability problems.  If you are mostly working except for
some small, hard to find problems, then get it merged, tell everybody
about the problems, and let people go hunt for them.  That is what
the open source process is about.

From what I can see, you are ready to go start the merging process
now.

Regards,

Daniel

  parent reply	other threads:[~2008-10-17 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 20:44 Ready for production ? David Arendt
     [not found] ` <48F65636.5050405-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2008-10-17  6:09   ` Ryusuke Konishi
     [not found]     ` <20081017.150912.86504903.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-10-17 11:15       ` Daniel Phillips [this message]
     [not found]         ` <200810170415.30644.phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org>
2008-10-18  2:28           ` Ryusuke Konishi

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=200810170415.30644.phillips@phunq.net \
    --to=phillips-sjnr1biwhqjeowh0uzbu5w@public.gmane.org \
    --cc=admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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