Our first focus was around improving the discussion and support around plugins.

You’ll now notice that threads about a plugin are pulled directly into a “support” tab on the plugin page — each plugin has its own forum. We’ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you’re using. And finally to show how active and well-supported a plugin is, you can see  ”16 of 75 support threads in the last two weeks have been resolved.” Finally, if you’re logged in you get access to the new “favorites” feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!

If you’re a plugin author, we’ve started with a short threshold (2 weeks) for the resolved stats so it’s easy to catch up and stay on top of it. (It’ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.

We’ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:

• “Plugin headers” or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.
• You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn’t yours. There is no better way to follow the development of your favorite plugins. There’s nothing like the smell of fresh changesets in the morning.
• Behind the scenes, we’ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.

All of this will continue to evolve as we get feedback and see usage, but we’re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ — it imparts magical coding powers.)

Fuente: WordPress News
Entrada original: http://wordpress.org/news/2012/05/plugins-refreshed/

Fuente: The Latest Tiki News
Entrada original: http://info.tiki.org/article193-The-Tiki-Admin-Team-Welcomes-New-Members

During a release team meeting we decided on the dates for the alpha and beta releases and of course for the final release.

As you see on the timeline, the date of the feature freeze which will be the 14th of August together with the release of the first beta version. From then on we will have a fair amount of time to stabilize the new features and fix remainig bugs.
If you want to contribute a feature for TYPO3 6.0, make sure to be ready with coding in the beginning of August, so that there is enough time for reviewing it until the first beta.

We also decided to start early with alpha releases, to enable you to test your extensions, applications and websites with them.
The first alpha version will be released on tuesday next week. A lot of code cleanups and refactoring happend already in order to have an easier and better testable codebase. This means that quite some previously deprecated API has been removed. Therefore we recommend to already test your extensions with it.
Of course also new features made it into that alpha version, most notably the long awaited File Abstraction Layer (FAL). We think FAL works great already, but there might be some minor issues here and there.

We would love to get your feedback especailly on this but also on other features and changes, be it from a user’s or a programmer’s perspective.

Fuente: TYPO3 news: Development
Entrada original: http://typo3.org//news/article/typo3-60-release-schedule/

FLOW3 1.1 contains various new features and – we knew you would like that – big speed improvements. We also took the opportunity to adjust some important APIs, such as the Model View Controller mechanism. Thus the upcoming FLOW3 version is not 100% backwards compatible and this is what we anticipated. But we found a nice way to ease everyone’s upgrade pain: a brand new code migration tool automatically adjusts your code to fit the most important API changes. And for the few parts it can’t refactor you just follow the detailed upgrade instructions.

Beta and Stable Releases

We plan to release two beta versions in total, followed by the stable release of FLOW3 1.1. If necessary, we’d also release additional betas or adjust the timeline in order to meet our quality standards. Both beta releases have a specific goal:
FLOW3 1.1 beta 1 contains all improvements we want to see in the final version. The goal for this release is to get feedback on the compatibility and stability: does your project still work fine after following our upgrade instructions? What did we miss? Although the first beta contains most of the code of the new major features (HTTP, I18N, content security, more speed …), those features are not fully documented yet. Which brings us to the goal for the second beta release:
FLOW3 1.1 beta 2 will contain all features, including the big new ones. The objective for this release is to also get feedback on the HTTP foundation, the localization and translation framework and all the other gems we put into 1.1. We will provide documentation for all of the new features so you know how to test and use them in your own projects. Once we are confident that 1.1 works equally fine for you like it does for us, we are ready for a stable 1.1 release.

Share Your Insights

At this point we’d like to invite you to upgrade existing projects or start new ones based on 1.1. Don’t use it in production yet, but please do share your insights and possible problems you might face. Please refer to the upgrading instructions and add your own findings to the related discussion page.
The prospective release date for FLOW3 1.1 beta 2 is May 29th. We hope you enjoy it.
Fuente: TYPO3 news: Development
Entrada original: http://typo3.org//news/article/flow3-11-beta-1-released/

Core code isn’t the only way to contribute to the WordPress project. We have an active theme review team, support forum volunteers, people writing documentation, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we’ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.

In addition to bringing together the active contributor team reps to work together, I think it’s important to include community members who don’t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!

Taking a cue from events with limited availability like AdaCamp (attendance) and the jQuery conference (speaker roster), I want you to nominate people and/or WordPress-based businesses to participate in the summit. Yes, you can nominate yourself.* You can nominate up to 10 additional people — be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there’s a theme or hosting company (for example) that you think should be there, you don’t need to go looking for employee names. This nomination process will hopefully ensure that we don’t overlook someone who is making a difference in our community when it comes time to issue invitations.

Nominations will be open for a week, after which the survey will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at WordPress.tv. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you’re thinking to yourself that maybe now’s the perfect time to start contributing time to the WordPress project, good thinking! In the meantime, if you want to weigh in, fill in the community summit nomination form. Thanks, and wish us luck!

* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.

** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.

Fuente: WordPress News
Entrada original: http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/

FLOW3 1.1 contains various new features and – we knew you would like that – big speed improvements. We also took the opportunity to adjust some important APIs, such as the Model View Controller mechanism. Thus the upcoming FLOW3 version is not 100% backwards compatible and this is what we anticipated. But we found a nice way to ease everyone’s upgrade pain: a brand new code migration tool automatically adjusts your code to fit the most important API changes. And for the few parts it can’t refactor you just follow the detailed upgrade instructions.

Beta and Stable Releases

We plan to release two beta versions in total, followed by the stable release of FLOW3 1.1. If necessary, we’d also release additional betas or adjust the timeline in order to meet our quality standards. Both beta releases have a specific goal:
FLOW3 1.1 beta 1 contains all improvements we want to see in the final version. The goal for this release is to get feedback on the compatibility and stability: does your project still work fine after following our upgrade instructions? What did we miss? Although the first beta contains most of the code of the new major features (HTTP, I18N, content security, more speed …), those features are not fully documented yet. Which brings us to the goal for the second beta release:
FLOW3 1.1 beta 2 will contain all features, including the big new ones. The objective for this release is to also get feedback on the HTTP foundation, the localization and translation framework and all the other gems we put into 1.1. We will provide documentation for all of the new features so you know how to test and use them in your own projects. Once we are confident that 1.1 works equally fine for you like it does for us, we are ready for a stable 1.1 release.

Share Your Insights

At this point we’d like to invite you to upgrade existing projects or start new ones based on 1.1. Don’t use it in production yet, but please do share your insights and possible problems you might face. Please refer to the upgrading instructions and add your own findings to the related discussion page.
The prospective release date for FLOW3 1.1 beta 2 is May 29th. We hope you enjoy it.
Fuente: TYPO3 news: Development
Entrada original: http://typo3.org//news/article/-397dfd6490/