> > Every time someone asks about version 2.4.2, we keep hearing "it'll be out
> > in a week I'm just finishing up the docs
>
> That's the main pending issue for 2.4.2 to be released. The code is
> stable. It's been in production on many sites for a while. Just make
> sure you test it before you actually need it, just like you should do
> with any backup software, be it a final release or not.
Just because a lot of sites are running beta software doesn't mean
anything. For a developer to move a source code base from "beta" to "gamma"
means that the developer has decided that this meet some baseline of
stability/security/etc that they feel makes it gamma quality.
We are running 2.4.2 right now. But the fact that it hasn't moved into
gamma after 6 months of few if any updates to the source implies that there
is some major issue which remains unsolved. Thus, I am questioning why it
is being held back so that I can understand the known issues.
Keep in mind that
A. This is backup software that all of us depend upon.
B. You don't provide an updated known bugs list.
So I'm left to ask -- what is holding up release? What are the open issues?
If there are known issues with 2.4.2, what are they? Nobody's listed them,
yet it hasn't been released nor have there been many updates to the 2.4.2
tree.
> > What exactly is holding up the 2.4.2 release? Are there unresolved bugs?
> > How can we help?
>
> So what you're saying is that you're volunteering to dedicate full
> time to review and update Amanda's documentation until 2.4.2 is out?
> Or maybe I misunderstand you? :-)
There are people here, myself included, who would be willing to devote some
effort to speeding this along if we understood how we can help. Devoting
"dedicated full time" is probably beyond most of us, but this wasn't
indicated in any form in my initial question. Where did that come from?
--
Joe Rhett Chief Technology Officer
[EMAIL PROTECTED] ISite Services, Inc.
PGP keys and contact information: http://www.noc.isite.net/Staff/
