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.
Be kell jelentkezni ahhoz, hogy ez helytelenként legyen megjelölve.
