2.7.1, the first 2.7 maintenance release, is almost ready. So far, 66 tickets are fixed in 2.7.1. There are another 50 tickets open against the 2.7.1 milestone, but most of those will be moved to 2.7.2 or 2.8. If there are tickets in that list you would really like to see fixed in 2.7.1, drop a comment.
To automatically upgrade from 2.7 to 2.7.1 Beta 1, change the version in your wp-includes/version.php file from 2.7 to 2.7.1-beta and then visit Tools->Upgrade. Otherwise, download the beta package and install manually.
Great to hear. I always feel reassured by x.x.1 releases.
I would love to see http://trac.wordpress.org/ticket/8750 resolved, it’s something that’s been irking me for a while.
Regarding all of the closed tickets: Great work!
Most (all?) of the high priority tickets would be appreciated. Also, personally, I would really like 8543 fixed (but the ticket its possibly a duplicate of is sceduled for 2.8).
no já bych klidně moderoval je mi 17 ale moderoval bych až od 21:00 – 23 chodim na dramaťák a sestřenka pracuje v rádiu a já od ní už něco okoukal
[...] hoy por fin Ryan Boren ha dicho esta boca es mía y ha hecho unos breves comentarios sobre la beta y el inminente lanzamiento de la versión final de [...]
I’ll be pleased enough if all marked with ‘high’ priority are fixed in the final release
Wew… i don’t now if wordpress release 2.7.1 beta. I just upgraded to 2.7 few days ago. And now new version will be release
My wish. I’d like http://trac.wordpress.org/ticket/8863 to be resolved! This bug breaks my comment related stats.
[...] için Boren‘a teşekkürler. Şubat 3rd, 2009 in WordPress | tags: WordPress 2.7.1 Beta [...]
i hope the drop down menu issue is already embedded. it’s hard to look for a good drop down menu plugin.
[...] Boren, nos informa de la aparición de la primera actualización de WordPress 2.7, concretamente esta 2.7.1 (aún en estado beta) solventa unos 60 problemas menores detectados y ha ayudado a detectar problemas y caréncias que [...]
#7520, especially, bugs the hell out of me. I’d be THRILLED if I could set default options for images explicitly, I use the same settings 95% of the time and they aren’t the defaults WP uses.
wow! used a lot of open source before but nothing like wp. i am using it as a cms and i am fully satisfied. will wait for the stable release. great!
[...] a versão 2.7.1 Beta 1 do WordPress, essa release vem com várias correções, na verdade 66 tickets foram corrigidos, o pessoal ainda [...]
It’s about time, many people have been asking when 2.7.1 will come out.
I will first see what has changed from the previous version.
Thanks for sharing
Welcome WP 2.7.1 Beta !
again the same question, why should there be beta releases so frequently? Is it that necessary?
waiting
Finally! I’ve been waiting for this forever
[...] Ryan Boren Etiquetas: actualizar, beta, herramienta, oficial, web, webs, [...]
waiting, toooooooooooooooo
Apik ora yo..?
Good news! Thx!
I`ve been using the beta for a new days.
There`s only 1 rather important bug. which i`ve reported on the wordpress forum.
Hello
This forced me to update? When we get a version 2.8 update should be fine right?
[...] está disponible para descarga la beta 1 de WordPress 2.7.1, en la que se han solucionado 66 tickets. Si quieres actualizar a esta versión (no recomendable [...]
GJ!
Updates are very fast thou. I just updated from 2.6.0… I think I will stick with 2.7.2 until 2.9 or 2.10 releases, a few plugins always get bugged after update
The 2.7.1 is coming very slowly, I have been expecting it earlier. However, I am very pleased with 2.7, it works great and I love the automatic upgrade.
I’m starting to love WordPress more and more!
I dont know…isn’t too risky install a beta version on top of a stable version? I would not risk!
[...] primer actualización de mantenimiento de WordPress 2.7.1 está por ser lanzado, tal y como anuncia Ryan Boren, para este beta 66 tiquetes (pulgas o pequeñas actualizaciones) han sido resueltos con otros 50 [...]
I dont have privileges to submit new tickets so hopefully this will get out some how. When clicking the Dashboard link in the admin console it returns a blank page: {url}/wp-admin/admin.php?page=index.php. When clearing the extended link and leave as {url}/wp-admin it loads page correctly. This has been noted from original production 2.7 release in a Local test environment and production hosted environment. Problem still persists and I dont see a currently logged ticket for this issue.
thanks
Please fix the white screen of death!
Waiting…
Is that because you always assume x.x releases to be broken by default?
I agree with this. Having the time displayed as different time zones for different things gets annoying (and confusing).
Yes, please fix the timezone tickets Ryan!
Thanks again for all you do.
could you please give more info?
(turn debugging on, show us the errors)