Visualização combinada Visão plana Exibição em árvore
Tópicos [ Anterior | Próximo ]
Mostrando 1 - 20 de 48 resultados.
de 3
James Falkner
Liferay 6.2 Milestone 4: Community Verifier
21 de Fevereiro de 2013 14:03
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

Hi Team,

This team did an outstanding job last year in finding and verifying almost 400 bugs soon after the 6.1 release, cutting the unverified list almost in half! We need your help once more. I'd like to re-energize the team and make it easier to participate, by making a couple of changes and really concentrating on verifying 100% of those outstanding bugs. Here are the changes for 2013:

  • Recruiting new members. We have 6 new members joining! Welcome to Amit Doshi, Aniceto Perez, Tejas Kanani, Gaurav Jain, Jignesh Vachhani, and Prakash Khanchandani!
  • The team will now verify against the latest Milestone release (currently Milestone 4). This means no fooling with EE licenses, and you get a sneak peek of what's coming in Liferay!
  • Updated the Participation Guide to clearly spell out the goals and specific instructions for verifying bugs.
  • Right now, the number of bugs needing verification stands at 480. We will be celebrating our victory at various stages:
    • 25% (when 360 remain) - Participants will receive a community-designed tee-shirt and awesome community laptop stickers!
    • 50% (when 240 remain) - Participants will receive an official award depicting their accomplishment that can be proudly displayed at work and on their social profiles around the web, and recognition on the IRC Topic for the official #liferay chat room for 30 days.
    • 75% (when 120 remain) - Participants will receive free passes to an upcoming Liferay event of their choosing, or free training (subject to availability).
    • 100% (when none remain) - To be determined, but I can guarantee you it will be monumental. I'll need galactic presidential authorization before revealing what will happen.
  • Successfully verified tickets will be recorded in the annals of Liferay, using the Verified-By field in JIRA. We'll have a leaderboard set up to track this on the Community Verifier Homepage. You'll be able to see your verified issues actually make it into the next release, and see that your efforts benefited the entire open source community.

So, please take a few minutes to read over the participation guide, and see if you can help out! Having a cleared issue board is a HUGE step toward improving the quality and predictability of Liferay releases, which helps everyone interested in using Liferay. We need the community's help to clear this, because it takes time to look at and verify each issue. Liferay does not believe in mass-closing old bugs simply because they're old, they each need attention!

If you would like to join this team, let me know via email or this thread and I will add you to the JIRA group.
Mika Koivisto
RE: Liferay 6.2 Milestone 4: Community Verifier
21 de Fevereiro de 2013 15:52
Resposta

Mika Koivisto

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1501

Data de entrada: 7 de Agosto de 2006

Mensagens recentes

Sorry the current issue count is now down to 471. I cleared a few very old issues.
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
21 de Fevereiro de 2013 16:36
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

Mika Koivisto:
Sorry the current issue count is now down to 471. I cleared a few very old issues.


Nice! We're off to a good start then emoticon
Alan Lim
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 00:51
Resposta

Alan Lim

Ranking: New Member

Mensagens: 1

Data de entrada: 14 de Fevereiro de 2012

Mensagens recentes

Hi James,

Could you upgrade my JIRA access so I could update the JIRA ticket label? Thank you.

Regards,
Alan
Szymon Gołębiewski
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 01:15
Resposta

Szymon Gołębiewski

Ranking: Regular Member

Mensagens: 247

Data de entrada: 8 de Junho de 2009

Mensagens recentes

James Falkner:
Liferay does not believe in mass-closing old bugs simply because they're old, they each need attention!


Hallelujah! emoticon
Aniceto P Madrid
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 04:51
Resposta

Aniceto P Madrid

Ranking: Regular Member

Mensagens: 135

Data de entrada: 24 de Maio de 2008

Mensagens recentes

James

I cannot change the affected versions field

Thaks
Aniceto P Madrid
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 05:14
Resposta

Aniceto P Madrid

Ranking: Regular Member

Mensagens: 135

Data de entrada: 24 de Maio de 2008

Mensagens recentes

James

I can see in github tags up to milestone 3. Where is m4? is te current trunk?

Thanks
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 06:44
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

Alan Lim:
Hi James,

Could you upgrade my JIRA access so I could update the JIRA ticket label? Thank you.

Regards,
Alan


Welcome to the team Alan. Nice to see more Aussies on the roster.
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 06:45
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

Aniceto P Madrid:
James

I can see in github tags up to milestone 3. Where is m4? is te current trunk?

Thanks


It shall be added shortly. It's not currently part of the release process, but should be soon.
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 06:56
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

All, a couple of questions have come up:

Q: How do we know who’s working on what or whos done what if we aren’t assigning the tickets to ourselves?
A: When you select a ticket, the first thing you should do is add the community-verifier label (see the participation guide for details on how to do this). If the analysis will require more than a couple of hours, also add a comment that you are looking into it (again, see participation guide).

Q: I know there was mention of a leaderboard but I can’t find it or see how it would work if the tickets aren’t attached to us in any way.
A: Working on it today, should be available soon!

Q: Next issue I’ve run into. LPS-33075 talks about the knowledge base but the knowledge base does not appear to be available with Milestone 4.
A: Good point. Unfortunately since plugins are now de-coupled, we don't build each and every plugin for the Milestone builds. If you're willing and able, it's relatively easy to compile and deploy a plugin. I will add instructions to the wiki page to show a quick&dirty way to do this.

Q: Another question. Many of these tickets talk about large numbers of pages. I don’t really have time to create 50+ test web content articles for each test to enable pagination in search results.
A: Another excellent point, but unfortunately one for which I don't have a good answer. There is a way to create one article, then copy it using the "Actions -> Copy" functionality from Control Panel. Or, you could create and execute some code in the "Script Executor" in Control Panel which creates a bunch of content (blog, wiki, etc) by converting some of the example java code snippets I published earlier into Velocity, but this isn't trivial cut'n'paste. I'll do this for blog entries and add it to the wiki page.

In the meantime, or if you aren't comfortable doing these kinds of things, just ignore those and concentrate on the bugs that affect the core of Liferay, while we collectively gain experience in working with bugs in plugins and reproducing the harder-to-reproduce issues.
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 07:14
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

James Falkner:

Q: I know there was mention of a leaderboard but I can’t find it or see how it would work if the tickets aren’t attached to us in any way.
A: Working on it today, should be available soon!


BTW, one comment on the leaderboard. When you verify a bug and recommend a course of action via your actions, you don't get "credit" for it (and it won't show up on the leaderboard) until Liferay QA staff actually takes the recommended course of action (and adds your name to the "Verified-By" field). This helps reduce the chance someone just mass-marks bugs as "should be closed" without any oversight.
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 08:46
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

Ok I added some instructions on how to build plugins to the wiki page for M4, and also, I present my quick and dirty script to generate tons of blog entries (so that you can force the search portlet to paginate):

 1
 2import com.liferay.portal.kernel.workflow.WorkflowConstants
 3import com.liferay.portal.model.GroupConstants
 4import com.liferay.portal.service.GroupLocalServiceUtil
 5import com.liferay.portal.service.ServiceContext
 6import com.liferay.portlet.blogs.model.BlogsEntry
 7import com.liferay.portlet.blogs.service.BlogsEntryLocalServiceUtil;
 8
 9long companyId = userInfo.get("liferay.company.id").toLong();
10long userId = userInfo.get("liferay.user.id").toLong();
11
12guestGroup = GroupLocalServiceUtil.getGroup(companyId, GroupConstants.GUEST);
13
14context = new ServiceContext();
15context.setWorkflowAction(WorkflowConstants.ACTION_PUBLISH);
16context.setAddGroupPermissions(true);
17context.setAddGuestPermissions(true);
18context.setCompanyId(companyId);
19context.setScopeGroupId(guestGroup.getGroupId());
20
21for (int i = 0; i < 100; i++) {
22    rCal = Calendar.getInstance();
23    BlogsEntry newEntry = BlogsEntryLocalServiceUtil.addEntry(
24        userId,
25        "Blog " + i + " Title", "",
26        "The awesome content of blog #" + i,
27        rCal.get(Calendar.MONTH), rCal.get(Calendar.DAY_OF_MONTH),
28        rCal.get(Calendar.YEAR),
29        rCal.get(Calendar.HOUR_OF_DAY), rCal.get(Calendar.MINUTE), false,
30        false, null, false, null,
31        null, null, context);
32    println("Created blog " + newEntry.getTitle());
33}
[Also posted as a Gist]

To use this, go to Control Panel -> Server Administration -> Script (tab), choose the Groovy language in the dropdown, then cut and paste the above code and click Execute. Then, for example, add the Search portlet to a page and search for "Blog". This could be modified, for example, to create web content articles instead of blogs. Be careful though! You might blow up your system if you code poorly in this scripting executor.
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
22 de Fevereiro de 2013 14:30
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

All,

I have added a leaderboard for this particular effort on the Community Verifier site. You can click on the avatars and names to be taken to the person's profile, or click on their numbers to see exactly which tickets they have verified. This only shows non-Liferay staff!

You can also see the total remaining at the bottom, and if you click on it, you are taken to the list of open issues to be verified. Good luck!

PS: If you see your name on the leaderboard, but you have a 'generic' avatar, be sure to update your profile on JIRA with your picture, if you wish it to show up on the leaderboard! Just log into issues.liferay.com and click on your name at the upper-right, then click the pencil icon next to your avatar and upload a custom pic.
Tejas Kanani
RE: Liferay 6.2 Milestone 4: Community Verifier
25 de Fevereiro de 2013 00:50
Resposta

Tejas Kanani

Ranking: Liferay Master

Mensagens: 653

Data de entrada: 6 de Janeiro de 2009

Mensagens recentes

James,
I've visited Community Verifier site. Looks like I am missing in "The Team" dashboard. emoticon
I've appropriate rights in JIRA but not seeing myself here.

Thanks,
Tejas
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
25 de Fevereiro de 2013 06:51
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

Tejas Kanani:
James,
I've visited Community Verifier site. Looks like I am missing in "The Team" dashboard. emoticon
I've appropriate rights in JIRA but not seeing myself here.

Thanks,
Tejas


Fixed! emoticon I had a bad email address for you in there. I really need to update it to use screen names.
Tejas Kanani
RE: Liferay 6.2 Milestone 4: Community Verifier
25 de Fevereiro de 2013 22:34
Resposta

Tejas Kanani

Ranking: Liferay Master

Mensagens: 653

Data de entrada: 6 de Janeiro de 2009

Mensagens recentes

Thanks James. emoticon
Amit Doshi
RE: Liferay 6.2 Milestone 4: Community Verifier
26 de Fevereiro de 2013 04:21
Resposta

Amit Doshi

Ranking: Liferay Master

Mensagens: 544

Data de entrada: 29 de Dezembro de 2010

Mensagens recentes

James,

I am not able to find myself in "liferay-community-verifier" Group.

Can you please add me on the same?

Thanks & Regards,
Amit Doshi
Aniceto P Madrid
RE: Liferay 6.2 Milestone 4: Community Verifier
27 de Fevereiro de 2013 04:57
Resposta

Aniceto P Madrid

Ranking: Regular Member

Mensagens: 135

Data de entrada: 24 de Maio de 2008

Mensagens recentes

James

Somebody is fooling us because we started on Feb 21st and there are new issues after that date.

We´ll have to renegociate our work conditions: salary, vacations, health insurance, working hours, etc.

Regards
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
27 de Fevereiro de 2013 05:52
Resposta

James Falkner

LIFERAY STAFF

Ranking: Liferay Legend

Mensagens: 1222

Data de entrada: 17 de Setembro de 2010

Mensagens recentes

Aniceto P Madrid:
James

Somebody is fooling us because we started on Feb 21st and there are new issues after that date.

We´ll have to renegociate our work conditions: salary, vacations, health insurance, working hours, etc.

Regards


Yeah, I've been wondering what to do about that - it's not really fair to chase a moving target, but then again we never set an 'end date' for the contest at least.

How about, I'll change the dashboard to only consider those issues filed on or before Feb 21, and then the close of the contest (but not the CV program) is when 6.2 ships?

Also, vacations are hereby cancelled, and everyone will have to take a 20% cut in pay, but work 50% more hours per week. Seems fair to me.
Szymon Gołębiewski
RE: Liferay 6.2 Milestone 4: Community Verifier
27 de Fevereiro de 2013 06:36
Resposta

Szymon Gołębiewski

Ranking: Regular Member

Mensagens: 247

Data de entrada: 8 de Junho de 2009

Mensagens recentes

James Falkner:
Also, vacations are hereby cancelled, and everyone will have to take a 20% cut in pay, but work 50% more hours per week. Seems fair to me.


I just flagged your post as "Infringes my Rights" ;)
Mostrando 1 - 20 de 48 resultados.
de 3