The later updates will be smaller and more focused, including such features as Apache 2.0.x and 2.2.x support.
Currently it's only on EDGE. Once the QA team is comfortable that it meets our quality standards, only then will it begin to gradually move into the production-worthy builds (CURRENT, RELEASE and eventually STABLE)As your CPanel is upcp'd, you will have more options to install through WHM. I am on CURRENT. I don't know what tree or version you are on.
In WHM, you can choose Update Apache and Apache2 will be there (depending again on your CPanel Version. I think you would need to be on edge to have it at the moment. Wait a few days and it will be available with Current).
Currently it's only on EDGE. Once the QA team is comfortable that it meets our quality standards, only then will it begin to gradually move into the production-worthy builds (CURRENT, RELEASE and eventually STABLE)
I just updated my test server to CURRENT, no EasyApache 3 yet so I assume there may be some issues that still need working on by the Dev and QA folks. After all, as much as we *all* want Apache 2 support at this time, we'd much rather not break servers in the process.There is a current build posted today. Is this based on Stage 2?
Also where can I find Apache2
-a
I've upgraded on of our VPS Servers to EDGE. It seems as stable as the current build. We're stress testing it now and are "thinking" of turning off auto update if we find it stable enough. Once that has passed, we may "chance" using it on a few other places (with caution). From there we'll wait until the CURRENT build fits are needs once more.Now I'm running EDGE, so my server already has the easyapache script that support it, but... I dont really understand the complaints here,
would you rather have it take a bit more time so that the team can make sure your apache server doesnt break, or do you rather have a buggy version released? :-X
Sure I can understand the frustration,
but a broken apache server gives even more frustration in my humble opinion.