Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

BugDay/201107

From TYPO3Wiki
Jump to: navigation, search
This page belongs to the TYPO3 Bug Day project (category Project)

General

Actually this time we have a whole Bug Weekend for the time of July 29th-31st 2011.

Topic

Since TYPO3 4.6-beta1 will be released next week and the first beta version always defines the feature freeze, the Bug Weekend in July 2011 is dedicated to get pending features reviewed and overworked if required. However, priority should be given to patches already pending in Gerrit.

How does it work

  • look at the bug reports and pick an issue that sounds interesting to you
  • Important: post the bug ID in IRC before you start working on it, so that nobody does double work (the lists below show who is currently working on a specific issue)
  • check if the bug/feature report still applies to current TYPO3 versions (version matrix)
  • now the reviewing and testing process starts - so, search for the bug/feature ID in Gerrit

Note: Since March 2011 reviewing patches is done using Gerrit, which you find at https://review.typo3.org/. Basically it works the same way as the Core List did:

  • apply the provided patch file to your local TYPO3 installation and test if the patch solves the issue
  • additionally you can also review the code and make sure if it's clean and understandable or if it has programming flaws
  • finally post your votes in the issue in Gerrit:
    • vote Verified after a formal check: Did the patch apply? Is it free of PHP errors? Does it follow the CGL? If so, mark it as "verified".
    • vote Code Review +1, if the patch solves the issue ("everything was fine") or Code Review -1 if something was wrong.
    • If you voted "-1" somewhere, please add a reason in the field "Cover message" below the votes and if you can add an improved version of the patch.


Resources

Gerrit Reviewing System

Issues to work on

Big Blue Button Communication (preferred, we have voice there)

IRC Communication Channel (fallback if voice on BigBlueButton does not work)

For new bug hunters

Read Getting ready for a Bug Day.

Participants

Individual participants

Enter your name here so as not to be forgotten:

  • Oliver Hader
  • Steffen Gebert
  • Lorenz Ulrich
  • Patrick Broens
  • Susanne Moog
  • Christian Kuhn
  • Kay Strobach
  • Jo Hasenau
  • Stefan Geith
  • Philipp Gampe
  • Stefan Neufeind
  • Xavier Perseguers

(SteffenG: added everybody, who came to my mind..)

Meeting places

If you want to offer a meeting place for this Bug Day, please list it here. Give enough details to enable people to find the place, but if you need to give a lot of details please just put a link to some other page.

For participants: please enter yourself in the place where you plan to attend.

City, Country

Describe the meeting place here.

Bugs

Committed during Bug Weekend

These are the patches that were effectively committed.

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Ready to commit

These patches have all the votes needed. They just need to be committed by a Core Team member.

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Needs a core +1

These patches need a +1 from a Core Team member.

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Needs anyone's +1

These patches have already been reviewed by a Core Team member and need one more vote from anyone.

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Needs reviews

These patches have no reviews yet. After you reviewed a patch, please post your observations to the thread in Gerrit.
If the patch did not cause any side-effects and worked as expected, vote "+1 Verified" and "+1 Looks good to me, but someone else must approve" in Gerrit.

Bug Name
28536: TYPO3 Core - JSwindow-typolink URLs are encoded twice with htmlspecialchars() [Closed; assigned to Helmut Hummel]
Oliver Hader

Needs work

These patches are not working anymore and should be reworked.

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Development

Working on these bugs (development)

Bug Name

Triage

Bugs that can be closed

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Closed bugs

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name


Duplicate bugs

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Old bugs that can't be reproduced

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name

Usability issues that are still valid

Bug Name
Use the issue tag in this way: <issue>12345</issue>

your name