Title: 3.3 – Page 2 – Make WordPress Core

---

#  Tag Archives: 3.3

 [  ](https://profiles.wordpress.org/nacin/) [Andrew Nacin](https://profiles.wordpress.org/nacin/)
9:38 am _on_ December 3, 2011     
Tags: 3.3   

# 󠀁[Shortcodes were added to text widgets early in…](https://make.wordpress.org/core/2011/12/03/shortcodes-were-added-to-text-widgets-early-in/)󠁿

Shortcodes were added to text widgets early in the cycle, but this has been **reverted**
for 3.3 due to a number of problems discovered. See [r19547](https://core.trac.wordpress.org/changeset/19547),
[#10457](https://core.trac.wordpress.org/ticket/10457), and [#19411](https://core.trac.wordpress.org/ticket/19411).

Since I imagine a number of people probably knew about this enhancementenhancement
Enhancements are simple improvements to WordPress, such as the addition of a hook,
a new feature, or an improvement to an existing feature. already and would assume
it is in 3.3 final, I am posting here.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/nacin/) [Andrew Nacin](https://profiles.wordpress.org/nacin/)
1:50 am _on_ December 3, 2011     
Tags: 3.3   

# 󠀁[I just added 3.3 to the support forum…](https://make.wordpress.org/core/2011/12/03/i-just-added-3-3-to-the-support-forum/)󠁿

I just added 3.3 to the support forumSupport Forum WordPress Support Forums is a
place to go for help and conversations around using WordPress. Also the place to
go to report issues that are caused by errors with the WordPress code and implementations.
versions as well as the compatibility dropdowns in the plugins directory. Emailing
wp-hackers, wp-testers, and wp-forums about that now.

Strings were frozen [earlier today](http://wppolyglots.wordpress.com/2011/12/02/were-in-string-freeze-heads-up-on-timing/).

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/nacin/) [Andrew Nacin](https://profiles.wordpress.org/nacin/)
5:26 am _on_ December 2, 2011     
Tags: 3.3   

# 󠀁[Post-RC1 status update](https://make.wordpress.org/core/2011/12/02/post-rc1-status-update/)󠁿

Now that we’ve hit RCrelease candidate One of the final stages in the version release
cycle, this version signals the potential to be a final release to the public. Also
see [alpha (beta)](https://make.wordpress.org/core/tag/3-3/page/2/?output_format=md#alpha-beta).,
we’re only dealing with regressions or 3.3-specific bugs. The window for guest committers
is closed, and we’re all working with patches now — all commits first require secondary
approval.

#### Confirmed 3.3 bugs

**Five remaining bugs for 3.3. (See [reports 5](https://core.trac.wordpress.org/report/5)
or [6](https://core.trac.wordpress.org/report/6).)**

 * [#19411](https://core.trac.wordpress.org/ticket/19411), an issue with shortcodes
   in text widgets. **Needs developer feedback.**
 * [#19371](https://core.trac.wordpress.org/ticket/19371), some limitations with
   the Admin_Bar APIAPI An API or Application Programming Interface is a software
   intermediary that allows programs to interact with each other and share data 
   in limited, clearly defined ways. changes in 3.3. **Needs developer feedback.**
   Ideally, we solve this as simply as possible. That might be making get_nodes()
   public.
 * [#19408](https://core.trac.wordpress.org/ticket/19408), need to finalize logic
   surrounding some strings on the welcome panel. Patchpatch A special text file
   that describes changes to code, by identifying the files and lines which are 
   added, removed, and altered. It may also be referred to as a **diff**. A patch
   can be _applied_ to a codebase for testing. (from ryan) is about ready.
 * [#19410](https://core.trac.wordpress.org/ticket/19410), “New” in + New icon on
   Adminadmin (and super admin) Bar is black on focus. Patch from koopersmith ready
   to go.
 * [#19346](https://core.trac.wordpress.org/ticket/19346), final styling and strings
   for maintenance releases. Patches from me and chexee ready to go.

#### Watching for more bugs

Need to watch two things. One, defects reported against trunktrunk A directory in
Subversion containing the latest development code in preparation for the next major
release cycle. If you are running "trunk", then you are on the latest revision.,
normally the first section of [report 40](https://core.trac.wordpress.org/report/40).
I just cleaned it out, so it’s empty.

Two, the [Alpha/Beta support forums](https://wordpress.org/support/forum/alphabeta).
I’ve been skimming these threads and they look impressively handled by ipstenu, 
duck_, and a number of others. If anything comes up, now is the time to sound the
alarms.

#### String freeze

Per [Jane’s post earlier this week](http://wpdevel.wordpress.com/2011/11/29/3-3-status-update/),
the goal is to release 3.3 in under two weeks. String freeze will likely occur on
Friday, before the weekend. Need to handle [#19346](https://core.trac.wordpress.org/ticket/19346)
and [#19408](https://core.trac.wordpress.org/ticket/19408), but that’s it — plenty
of strings to be worked on.

#### Twenty Ten and Twenty Eleven

I think both need version bumps.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
8:09 pm _on_ November 29, 2011     
Tags: 3.3   

# 󠀁[3.3 Status Update](https://make.wordpress.org/core/2011/11/29/3-3-status-update/)󠁿

Nothing too major has come up since beta 4 last week. Looking at pushing RC1 tomorrow
by dev chat time. There are a few bugs and such; check https://core.trac.wordpress.
org/report/6 to keep up and help test incoming patches. A bunch of Help tab patches
came in, so I’ll be reviewing all the committed text today and doing a patch with
any edits for tomorrow’s RC/string freeze push.

Note to translators: Since we want to get 3.3 launched before the coreCore Core 
is the set of software required to run WordPress. The Core Development Team builds
WordPress. team meetupMeetup All local/regional gatherings that are officially a
part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/).
A meetup is typically a chance for local WordPress users to get together and share
new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com
will help you find options in your area. if possible (starts Dec 13), that means
a little less than two weeks of string freeze. The help tabs may still change before
RCrelease candidate One of the final stages in the version release cycle, this version
signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/tag/3-3/page/2/?output_format=md#alpha-beta).
tomorrow, but there are two large chunks of text that are new in 3.3 — about.php
and index.php (Welcome section) — but have finalized text if you want to get a head
start.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
3:06 pm _on_ November 23, 2011     
Tags: 3.3   

# 󠀁[15 10 6 tickets between us and launch…](https://make.wordpress.org/core/2011/11/23/15-tickets-between-us-and-launch-still-need-2/)󠁿

15 10 6 tickets between us and launch. Still need a betaBeta A pre-release of software
that is given out to a large group of users to trial under real conditions. Beta
versions have gone through alpha testing in-house and are generally fairly close
in look, feel and function to the final product; however, design changes often occur
as part of the process. 4 and an RCrelease candidate One of the final stages in 
the version release cycle, this version signals the potential to be a final release
to the public. Also see [alpha (beta)](https://make.wordpress.org/core/tag/3-3/page/2/?output_format=md#alpha-beta)..
The tickets:

#### Needs Dev / Bug Wrangler Feedback

 *  [#19338](https://core.trac.wordpress.org/ticket/19338) Welcome Panel and no 
   JSJS JavaScript, a web scripting language typically executed in the browser. 
   Often used for advanced user interfaces and behaviors. don’t mix well — Not sure
   how we missed putting in a no-js version, but we did. Need one. @dkoopersmith
   was owner of feature, [@azaozz](https://profiles.wordpress.org/azaozz/) has done
   lots of the no-js stuff in wp, and @joncave made the ticketticket Created for
   both bug reports and feature development on the bug tracker. and wrote a patchpatch
   A special text file that describes changes to code, by identifying the files 
   and lines which are added, removed, and altered. It may also be referred to as
   a **diff**. A patch can be _applied_ to a codebase for testing.. Huddle and work
   it out. ([@jane](https://profiles.wordpress.org/jane/))
 *  [#17975](https://core.trac.wordpress.org/ticket/17975) _default_wp_die_handler
   css referencing logic is fragile and doesn’t always work ([@jane](https://profiles.wordpress.org/jane/))

#### Has Patch / Needs Testing

 *  [#19020](https://core.trac.wordpress.org/ticket/19020) Content Updates for Help
   Tabs — Tedious. Will finish before before string freeze at RC. Mostly same strings,
   just moved around a bit. @chexee, [@jane](https://profiles.wordpress.org/jane/)
   and whoever wants to help with some copy paste drudgery patching.
 *  [#19191](https://core.trac.wordpress.org/ticket/19191) Improve adminadmin (and
   super admin) menu tab navigation — Gotta be keyboard accessible! @dkoopersmith
   or [@azaozz](https://profiles.wordpress.org/azaozz/) need to check out patch 
   by John Kleinschmidt on ticket. ([@jane](https://profiles.wordpress.org/jane/))
 *  [#19127](https://core.trac.wordpress.org/ticket/19127) Welcome Panel should 
   be displayed for the first administrator — Panel itself is done, but needs code
   underneath. [@nacin](https://profiles.wordpress.org/nacin/) is on this today.(
   [@jane](https://profiles.wordpress.org/jane/))
 *  [#19326](https://core.trac.wordpress.org/ticket/19326) jQuery 1.7.1 — They _just_
   released this update. There were some issues with 1.7. ([@jane](https://profiles.wordpress.org/jane/))
 *  [#19292](https://core.trac.wordpress.org/ticket/19292) Not found errors due 
   to sanitization in sanitize_title_with_dashes — Mark’s patch being reviewed.
 *  [#19125](https://core.trac.wordpress.org/ticket/19125) CPT as a submenu item
   does not get the correct classes when adding new ([@jane](https://profiles.wordpress.org/jane/))
 *  [#18693](https://core.trac.wordpress.org/ticket/18693) New feature pointers —
   These are in, but in some browsers aren’t positioning correctly (fixed, [[19416]](https://core.trac.wordpress.org/changeset/19416)).
   Also need a little RTL love, see [#19335](https://core.trac.wordpress.org/ticket/19335).(
   [@jane](https://profiles.wordpress.org/jane/))

#### Patch Needs Refresh

 *  [#18880](https://core.trac.wordpress.org/ticket/18880) Back compatback compat
   Backward compatibility - a desire to ensure that plugins and themes do not break
   under new releases - is a driving philosophy of WordPress. While it is a commonly
   accepted software development practice to break compatibility in major releases,
   WordPress strives to avoid this at all costs. Any backward incompatible change
   is carefully considered by the entire core development team and announced, with
   affected plugins often contacted. It should be noted that external libraries,
   such as jQuery, do have backward incompatible changes between major releases,
   which is often going to be a greater concern for developers. for the admin_user_info_links
   filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
   They provide a way for functions to modify data of other functions. They are 
   the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
   manner, and should never have side effects such as affecting global variables
   and output. ([@jane](https://profiles.wordpress.org/jane/))

#### Needs Patch

 *  [#19088](https://core.trac.wordpress.org/ticket/19088) AccessibilityAccessibility
   Accessibility (commonly shortened to a11y) refers to the design of products, 
   devices, services, or environments for people with disabilities. The concept 
   of accessible design ensures both “direct access” (i.e. unassisted) and “indirect
   access” meaning compatibility with a person’s assistive technology (for example,
   computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) for the
   admin bar — Screen readers, tabbing, etc. ([@jane](https://profiles.wordpress.org/jane/))
 *  [#18742 ](https://core.trac.wordpress.org/ticket/18742)New post-update screen—
   screen itself is done (translators, might want to get a head start, lots of new
   strings), but needs code to tell when to show it/to whom. Maybe some RTL love
   also. [@nacin](https://profiles.wordpress.org/nacin/) doing the when-to-show 
   code. ([@jane](https://profiles.wordpress.org/jane/))
 *  [#19320](https://core.trac.wordpress.org/ticket/19320) wp_tiny_mce() cannot 
   call wp_editor(), and other issues — [@nacin](https://profiles.wordpress.org/nacin/)
   and [@azaozz](https://profiles.wordpress.org/azaozz/) duking it out on the ticket.(
   [@jane](https://profiles.wordpress.org/jane/))
 *  [#19335](https://core.trac.wordpress.org/ticket/19335) Make feature pointers
   nice for our RTL users ([@jane](https://profiles.wordpress.org/jane/))
 *  [#18467](https://core.trac.wordpress.org/ticket/18467) Standardize Language 
   on CoreCore Core is the set of software required to run WordPress. The Core Development
   Team builds WordPress. Update — [@nacin](https://profiles.wordpress.org/nacin/)
   working on it.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
1:03 am _on_ November 23, 2011     
Tags: 3.3   

# 󠀁[14 tickets](https://make.wordpress.org/core/2011/11/23/14-tickets/)󠁿

14 tickets.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
4:13 pm _on_ November 22, 2011     
Tags: 3.3   

# 󠀁[It’s that time again in the release cycle…](https://make.wordpress.org/core/2011/11/22/its-that-time-again-in-the-release-cycle/)󠁿

It’s that time again in the release cycle where we have to be bad guys to be good
guys. We’re past deadline, we’re hitting the holidays, and if we don’t start cutting
the cord, 3.3 will hang on until next year. Say it with me: Not again!

For the people working on the release, most of whom run trunktrunk A directory in
Subversion containing the latest development code in preparation for the next major
release cycle. If you are running "trunk", then you are on the latest revision. 
on their own sites for at least a month or two (if not longer) before each launch,
it’s easy to forget that features we had done months ago — flyout menus, drag and
drop uploading — are still being hoarded by us (and more recently by the lucky recipients
of a merge onto wordpress.comWordPress.com An online implementation of WordPress
code that lets you immediately access a new WordPress environment to publish your
content. WordPress.com is a private company owned by Automattic that hosts the largest
multisite in the world. This is arguably the best place to start blogging if you
have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/))
and are not available on the sites of regular users. While we try to take the time
to examine every bugbug A bug is an error or unexpected result. Performance improvements,
code optimization, and are considered enhancements, not defects. After feature freeze,
only bugs are dealt with, with regressions (adverse changes from the previous version)
being the highest priority., every fix, and every report of one of those not working,
all the stuff that is done and working fine is just sitting there, waiting on the
sidelines to be asked to dance by a happy WordPress user who’s still not even at
the party.

It’s time for everyone to join the 3.3 party.

From the [WordPress.org Philosophy](https://wordpress.org/about/philosophy/) page:

> Deadlines are not arbitrary, they’re a promise we make to ourselves and our users
> that helps us rein in the endless possibilities of things that could be a part
> of every release. We aspire to release three major versions a year because through
> trial and error we’ve found that to be a good balance between getting cool stuff
> in each release and but not too much that we end up breaking more than we add.
> Good deadlines almost always make you trim something from a release. This is not
> a bad thing, it’s what they’re supposed to do.
> The route of delaying a release for that one-more-feature is, literally, a rabbit
> hole. We did that for over a year once, and it wasn’t pleasant for anybody.
> The more frequent and regular releases are, the less important it is for any particular
> feature to be in this release. If it doesn’t make it for this one, it’ll just 
> be a few months before the next one. When releases become unpredictable or few
> and far between, there’s more pressure to try and squeeze in that one more thing
> because it’s going to be so long before the next one. Delay begets delay.

So, here’s where we stand: We’ve had some unexpected big bugs (widgets, etc). We’ve
had some people get sick. We’ve had some people traveling. Or moving. Or having 
kids, a job, a family, a life. It happens. We are one week away from our target 
launch date, and we still need to do betaBeta A pre-release of software that is 
given out to a large group of users to trial under real conditions. Beta versions
have gone through alpha testing in-house and are generally fairly close in look,
feel and function to the final product; however, design changes often occur as part
of the process. 4 and an RCrelease candidate One of the final stages in the version
release cycle, this version signals the potential to be a final release to the public.
Also see [alpha (beta)](https://make.wordpress.org/core/tag/3-3/page/2/?output_format=md#alpha-beta).
cycle. Clearly we will be launching late.

As of today, we are a steamroller paving the way to 3.3 launch. There are 36 tickets
right now. Of those, a few are still time-consuming blockers. Yes, those have to
get fixed. If someone can’t write content, that’s a big problem. Pretty much everything
else that still needs work will be moved to 3.4-early. Note that “has-patchpatch
A special text file that describes changes to code, by identifying the files and
lines which are added, removed, and altered. It may also be referred to as a **diff**.
A patch can be _applied_ to a codebase for testing.” is not the same as “has-patch
and has been agreed upon as a patch we should include in coreCore Core is the set
of software required to run WordPress. The Core Development Team builds WordPress..”
Patches needing more work… need more work.

So instead of yelling, “How dare you puntpunt Contributors sometimes use the verb"
punt" when talking about a ticket. This means it is being pushed out to a future
release. This typically occurs for lower priority tickets near the end of the release
cycle that don't "make the cut." In this is colloquial usage of the word, it means
to delay or equivocate. (It also describes a play in American football where a team
essentially passes up on an opportunity, hoping to put themselves in a better position
later to try again.) my bug!” please instead focus on how important it is for us
to get this release out, and the sooner we do, the sooner we can get back to all
the things that got punted or postponed as we start the 3.4 cycle. Hey, we punted
our pet projects that weren’t done in time too — language packs, some of the responsive
adminadmin (and super admin) stuff, pointers on the new-install tour, etc. No one
was spared. (And believe me, I really wanted those pointers.)

So, countdown to 3.3 should start now. I’d offer a betting pool, but since we could
totally rig it, that would be lame. If we can do beta 4 today, RC1 after the US 
Thanksgiving holiday, we could still release before the core team meetupMeetup All
local/regional gatherings that are officially a part of the WordPress world but 
are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/).
A meetup is typically a chance for local WordPress users to get together and share
new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com
will help you find options in your area. in mid-Dec. We postponed a release until
after the meetup last year, and I wish we hadn’t. So let’s just get this sucker 
out the door, yeah?

Shipping is a feature. 🙂

And remember, since you run trunk, you’ll get all that 3.4 goodness before you know
it!

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
12:45 pm _on_ November 21, 2011     
Tags: 3.3   

# 󠀁[45 tickets](https://make.wordpress.org/core/2011/11/21/45-tickets/)󠁿

45 tickets.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
4:06 pm _on_ November 20, 2011     
Tags: 3.3   

# 󠀁[Also daily ticket counts time 55 tickets](https://make.wordpress.org/core/2011/11/20/also-daily-ticket-counts-time-55-tickets/)󠁿

Also, daily ticketticket Created for both bug reports and feature development on
the bug tracker. counts time. 55 tickets.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
3:24 pm _on_ November 20, 2011     
Tags: 3.3   

# 󠀁[Still shooting for Beta 4 widgets bug last…](https://make.wordpress.org/core/2011/11/20/still-shooting-for-beta-4-widgets-bug-last/)󠁿

Still shooting for BetaBeta A pre-release of software that is given out to a large
group of users to trial under real conditions. Beta versions have gone through alpha
testing in-house and are generally fairly close in look, feel and function to the
final product; however, design changes often occur as part of the process. 4; widgets
bugbug A bug is an error or unexpected result. Performance improvements, code optimization,
and are considered enhancements, not defects. After feature freeze, only bugs are
dealt with, with regressions (adverse changes from the previous version) being the
highest priority. last week threw us for a loopLoop The Loop is PHP code used by
WordPress to display posts. Using The Loop, WordPress processes each post to be 
displayed on the current page, and formats it according to how it matches specified
criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed
on each post. [https://codex.wordpress.org/The_Loop](https://codex.wordpress.org/The_Loop).
Sounds like it’s about fixed, so hopefully we can shoot for beta 4 on Monday. If
no unexpected blockers crop up, could potentially RCrelease candidate One of the
final stages in the version release cycle, this version signals the potential to
be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/tag/3-3/page/2/?output_format=md#alpha-beta).
a couple of days later? It seems not very likely that we’ll release by the original
target of November 29, but we have a little wiggle room. CoreCore Core is the set
of software required to run WordPress. The Core Development Team builds WordPress.
team meetupMeetup All local/regional gatherings that are officially a part of the
WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/).
A meetup is typically a chance for local WordPress users to get together and share
new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com
will help you find options in your area. will be the week of December 12, so if 
we can get it out by then we’ll be okay.

[#3-3](https://make.wordpress.org/core/tag/3-3/)

# Post navigation

[← Older posts](https://make.wordpress.org/core/tag/3-3/page/3/?output_format=md)

[Newer posts →](https://make.wordpress.org/core/tag/3-3/?output_format=md)