Jump to content

Current status of PW2.1


Adam Kiss
 Share

Recommended Posts

Hi all (and Ryan mostly:) ),

what's the current status of PW 2.1, and it's readiness for production? I remember announcement of 2.1, that went with 'not recommended for production'.

However, that was around a month ago, so I'm curious what's current status?

Note: I have to go live in about a week, will have to build a site on PW in next three days, so I'm curious which version to build on.

Link to comment
Share on other sites

Alastair, Antti (really? Top posters' names (except Ryan) start with A? We should call ourselves PW AAA): I know it works, but was more looking for recommendation for Ryan ;)

I mean, I believe both of you, but, after all, there are people who call WP a perfect any site CMS, it only needs 30 plugins (and you have plugins for everything!) [/irony]

And since it was Ryan who did not recommended 2.1 for production, I was curios whether he thinks it's ready now :)

edit: Also, no disrespect to you two :)

Link to comment
Share on other sites

This is not an easy yes/no question. :) I think that officially it's not good for me to say to use a development version for production use. But the reality is that we're all using it for production and it has some benefits over 2.0 that are worthwhile relative to the risks... but you have to determine that. The primary difference between the dev version and the stable version is that the dev version (2.1) has some newer code in it that hasn't yet been used on hundreds of sites. So when you use a dev version, you may be using some code that has only been tested by myself. It implies a higher chance that you may run into bugs, and that you are not just using it, but sort of testing it as well.

I don't ever knowingly push buggy or partially finished code to GitHub. So this may be different from the way other projects keep their development version. I only push updates after I've got them to a point where I think they are usable and I've tested to confirm it works. So in that sense, there is more stability in the dev version than people may assume at first.

Lastly, with the dev version, it may take a little more work on your part because you have to pay more attention to the updates. And it's a good idea to keep your source up-to-date, at least until there is a formal 2.1 release version. But  that's just a recommendation...

One other recommendation when using a dev version is to stage and test updates before you push them to production. And of course, back up stuff before you replace it. Though I think this recommendation applies for any update, and for any CMS, whether on a stable version or not...

Adam's "tldr" version: Given your involvement here and the fact that we communicate here a few times a week, 2.1 is probably the way for you to go in most cases. But if you just want to quickly setup a site and never got back to it, then 2.0 may be better in that case.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...