Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Unless I'm grossly mistaken, the .# versions are built on an as needed basis due to new security issues popping up (zero day hacks and the like) and/or a major issue or issues are found with the 2.7 series. Once a milestone release goes gold it shifts from trunk to branch and minor security/bug fix updates are made from that particular branch. There's no continuous development once 2.7-final is released and goes to branch that I know of. On 12/8/2008 4:38 AM, Xavier Borderie wrote: Okay, but what about when 2.7 is installed and before 2.7.1 becomes available, what will normal (not testers) users see? Well then you wouldn't be on trunk anymore, so I'm guessing there is no development version for 2.7.x once 2.7 goes gold. Unless, if course, a 2.7-dev code exists :) ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
[wp-testers] Verifying core update works for the real 2.7 to 2.7.1
I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? -- Xavier Borderie ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Ah, something I want to know as well. Since a few of my clients had requested to be updated to 2.7 RC1+ it would be nice to know if I'll be doing the update to 2.7-final automatically or manually (auto-updating to the final should be fine as I can't imagine there's any major changes from the current trunk to the final version). On 12/7/2008 1:40 PM, Xavier Borderie wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
On Sun, 7 Dec 2008 19:40:47 +0100, Xavier Borderie [EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? I suppose it works like warning about new version works now, if you use a nightly build on the admin footer it show a message inviting you to kepp updated, if you use a release version it show a message on the top of the admin screens when and only when a new version is available. As actual version know if there is an update or not i suppose the automatic update use same method (plus the selection of the correct locale if available) for allow update or not. -- Stefano Aglietti - StallonIt on IRCnet - ICQ#: 2078431 Email: [EMAIL PROTECTED] [EMAIL PROTECTED] Sites: http://www.40annibuttati.it (personal blog) http://www.wordpress-it.it (WordPress Italia) ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Michael E. Hancock wrote: I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
I was more worried that Matt and the guys would implement a Authorized Beta only system, where if you didn't have some sort of a code you wouldn't be able to Beta test Wordpress... Thereby getting rid of ppl like me. :( -Paleo Pat http://www.politicalbyline.com On Sun, Dec 7, 2008 at 2:34 PM, Jeff Chandler [EMAIL PROTECTED] wrote: Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Michael E. Hancock wrote: I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
In message [EMAIL PROTECTED], Jeff Chandler [EMAIL PROTECTED] writes Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Only admins have the ability to launch the update. -- mrmist ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
To be honest, I was thinking of getting rid of you. Kidding aside, I don't believe there are any wrong inquiries when it comes to testing. It is better to have someone stand up and be heard about a problem than have that problem go unnoticed and be broken for multiple versions. That is in my humble opinion. The more testers the better. That answer is a tricky one. If you update right when 2.7 comes out, if you are using RC1, then you should be fine. When WordPress goes back to being bleeding-edge then you will back on the nightlies. So I mean, the only ones affected will be the ones that update too late and update to bleeding-edge. However, you won't receive a notice to upgrade until 2.8 comes out. It will just be up to you on whether you want to or not. You know that is interesting. In the past, if you have one version say 2.5.1, it will tell you that 2.6.0 came out. Then if you want to upgrade to 2.5.2, it would still say 2.6. I wonder if they are going to fix that on the server side. Jacob Santos Paleo Pat wrote: I was more worried that Matt and the guys would implement a Authorized Beta only system, where if you didn't have some sort of a code you wouldn't be able to Beta test Wordpress... Thereby getting rid of ppl like me. :( -Paleo Pat http://www.politicalbyline.com On Sun, Dec 7, 2008 at 2:34 PM, Jeff Chandler [EMAIL PROTECTED] wrote: Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Michael E. Hancock wrote: I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
On Sun, Dec 7, 2008 at 10:40 AM, Xavier Borderie [EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Thanks Ryan. Just the information that was needed. On 12/7/2008 3:27 PM, Ryan Boren wrote: On Sun, Dec 7, 2008 at 10:40 AM, Xavier Borderie[EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. Excellent thing, thanks for your answer Ryan. -- Xavier Borderie ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Ryan Boren wrote: On Sun, Dec 7, 2008 at 10:40 AM, Xavier Borderie [EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. For the more adventurous of you that want to stay always on the nightly builds I intend on sorting out a plugin based solution although this may not be available before 2.7 goes gold. westi -- Peter Westwood http://blog.ftwr.co.uk | http://westi.wordpress.com C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5 ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
From: Ryan Boren [EMAIL PROTECTED] snip If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. /snip Okay, but what about when 2.7 is installed and before 2.7.1 becomes available, what will normal (not testers) users see? Right now it always says There is a new version of WordPress available for upgrade so will normal admin users see that message even though they have 2.7 installed? MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
