Support » Alpha/Beta/RC » I now have 4.2 alpha 1 !!!!

  • Resolved DavePorter

    (@daveporter)


    Is that right ?
    I saw the tweet that RC1 was released.
    So updated a test site (trivial site, not important)
    And I ended up with 4.2 alpha 1
    (using wp beta test 0.99)

    cheers, Dave

Viewing 15 replies - 1 through 15 (of 38 total)
  • Moderator Marius L. J.

    (@clorith)

    Hi,

    That’s most likely because the nightly builds had already been ran for the day before RC1 was released, so I’d give it a try again a bit later (alternatively grab the file manually from https://wordpress.org/wordpress-4.1-RC1.zip)

    I’ll leave this as unresolved until it’s confirmed to be the reason just in case 🙂

    Andre

    (@andrejcarter)

    I had the same experience with the same version of the beta tester plugin. Will going from 4.2-alpha to 4.1-RC1 cause any problems?

    Moderator Marius L. J.

    (@clorith)

    Shouldn’t cause any problems, 4.2-alpha and 4.1-RC1 are pretty much in sync at this time.

    Moderator Matthew

    (@kidsguide)

    Volunteer Moderator

    I had the same problem also.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    It’s not a ‘problem’ so much as it’s expected (especially if you set Beta Tester to Aortic, hullo 😉 )

    Manually grab 4.1-RC1 and install that.

    Andre

    (@andrejcarter)

    If the expected behavior when the beta tester plugin is installed is for 4.2 alpha to be installed why does the announcement post for 4.1 RC1 suggest using the beta tester plugin to get RC1?

    Is it due to a setting on my installation? It’s never jumped like this before and would like to understand why it did this time.

    quote> That’s most likely because the nightly builds had already been ran for the day before RC1 was released, so I’d give it a try again a bit later (alternatively grab the file manually…..)

    I’ve tried a few times now, but I still get 4.2 alpha
    if I download the RC1 zip, do I manually replace all the files ?
    This does not seem like very friendly behaviour – what is the point of the beta tester plugin if it is not updating the correct version ?

    Cheers, Dave

    Hi Dave,
    After clicking the update button, I had exactly the same experience and reaction. I was disappointed not to get the RC1 and wanted it to check my test site before WP 4.1 is issued. I did not expect it would simply backtrack and will have to install manually. Perhaps the Beta Tester algorithms need a tweak.

    quote -> Perhaps the Beta Tester algorithms need a tweak.

    Could not agree more!

    Same problem here, what should we do?
    Must manually download and install RC 1 now that the alpha 2 is installed?

    Moderator Marius L. J.

    (@clorith)

    That’s right, they moved all of trunk over to 4.2-alpha so the only way to get RC1 right now is to download it manually as described above (I was mistaken in my previous post that it might be timing related with when the build was made, unfortunately).

    I do the update manually to RC 1 yesterday. This morning, I do the daily update (nightly build) from the dashboard and I get once more version 4.2 alpha!
    What is the problem?

    I just manually reinstall RC1. Then, I manually downloaded wordpress-latest and I installed it manually. I get new 4.2-alpha!
    There’s a big problem!

    Moderator Jan Dembowski

    (@jdembowski)

    Brute Squad and Volunteer Moderator

    Nope, not a problem at all. Because the beta tester plugin is doing what it’s supposed to which is pull down the latest nightly. 😉

    Deactivate the beta tester plugin, install 4.1 RC1 again. With the plugin deactivated you will not go to 4.2-alpha.

    (Also thank you for testing the pending release, that’s really appreciated.)

    There is indeed a problem since I’ve never installed the beta tester plugin and WordPress 4.2-alpha is installed nevertheless.

Viewing 15 replies - 1 through 15 (of 38 total)
  • The topic ‘I now have 4.2 alpha 1 !!!!’ is closed to new replies.