This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. « Voltar para Contributing
100 PaperCuts
Note: Please see the main landing page for the latest updates.. <<TableOfContents>>
Introduction #
This project's aim is to identify and fix high-visibility, easy to correct bugs in Liferay Portal. It is driven by the wider Liferay community, with volunteers working to identify, prioritize, assign, and resolve known issues.
The Process #
- Identify issues. The community has always been encouraged to vote for issues that they would like to see fixed sooner rather than later. This has allowed Liferay program managers to properly prioritize bugs based on community feedback. With the 100 Paper Cuts program, voting has become even more important. We use the same voting system to identify high visibility, easy-to-fix bugs. The 100 Paper Cuts process begins with a period of time in which additional voting is encouraged. If you wish to vote for issues, please read the voting process. You can also browse this filter for potential PaperCuts bugs. This fiter shows all open bugs that haven't been already selected for inclusion into the existing Liferay development pipeline, sorted by votes.
- Assign and Fix. During a 2-week period, approximately 10 issues are selected and fixed based on their impact and effort required to fix. We aim for selecting bugs that take no more than 1 developer-day to fix. This period is called a "Community Sprint" and represents a fixed time amount in which to fix the identified issues. Once the sprint period is over, the process is repeated.
- Track progress. During and after the sprint, issues are tracked for progress, until the issue is merged with one or more Liferay releases.
Current Sprint Status #
| Resolved | In Progress | Blocked on submitter | Warning! | Unfixable/Not a papercut | |
|---|---|---|---|---|---|
 |  |  |  |  |
Sprint 5: May 11, 2011 - May 25, 2011 #
| Issue | Summary | Assigned To | Status | Indicator | |
|---|---|---|---|---|---|
| LPS-17329 | VelocityUtil.evaluate() creates velocity.log in tomcat bin directory | Rafal | Community Resolved | | |
| LPS-15409 | Document library folder permissions not exporting/importing | Juan | Resolved | | |
| LPS-16863 | PortletURL incorrectly created for secure resource | Corne | Contributed Solution | | |
| LPS-15491 | Automatic "html linkification" of text http links in message board posts | Boubker | Contributed Solution | |
Previous Sprint Status #
See the [100 PaperCuts - Previous Sprints] page for detail on past sprints and their status.
Páginas descendentes
57808 Visualizações
