Port project_usage to D7 [#1551356]

Comment #1

dww

we/he/they

commented 27 April 2012 at 22:30

Status:

Active

» Postponed

We should do #428680: Change usage stats to not use google charts first.

Log in or register to post comments

Comment #2

hunmonk commented 4 May 2012 at 22:09

Assigned:	Unassigned	» hunmonk
Status:	Postponed	» Active

A good portion of the port won't be related to the changes in project_release module, so we can start this now.

Log in or register to post comments

Comment #3

senpai commented 5 May 2012 at 21:44

Issue tags:

+sprint 1

Log in or register to post comments

Comment #4

dww

we/he/they

commented 5 May 2012 at 23:03

@hunmonk: This probably goes without saying, but be sure to merge the recent fixes to project_usage from 6.x-1.x into 7.x-2.x before porting. In particular:

#428680: Change usage stats to not use google charts
#703720: The varnish merge

Not sure if we should just cherry pick, or try a full 6.x-1.x -> 7.x-2.x merge.

Log in or register to post comments

Comment #5

hunmonk commented 14 May 2012 at 00:41

Status:	Active	» Needs review
Issue tags:	-sprint 1

this port is now mostly done. couple of remaining things:

{project_projects}.uri is used in the module, but i'm not sure where to get that from these days?
{project_release_nodes} and {project_projects} are both referenced in the drush plugin, clearly that will need to be updated, but i figure we should wait until project and project_release have shaken out their data structure for 7.x
the unit tests *should* pass, but project_usage depends on project_release currently, and that module still isn't ported -- seems best to deal with functional/unit testing once we have all deps working as well
#1576640: kill project-usage-process.php and raw/daily db tables would be a nice cleanup i think, and would save porting project-usage-process.php

Log in or register to post comments

Comment #6

dww

we/he/they

commented 15 May 2012 at 20:53

1. {project_projects}.uri is the machine_name field on project nodes.

2. Not sure how {project_projects} is referenced in the drush plugin. I'd need more info to be able to answer that. {project_release_nodes} is almost certainly going away. Again, more data about how it's being used would be helpful.

3. Do the tests actually depend on releases, or just that usage wants to depend on releases?

4. I'll answer there. ;) Short version: -1.

Thanks!
-Derek

Log in or register to post comments

Comment #7

senpai commented 18 May 2012 at 19:25

Issue tags:

+sprint 1, +sprint 2

Tagging for Sprint 2.

Log in or register to post comments

Comment #8

senpai commented 29 May 2012 at 17:18

Issue tags:

+sprint 3

Tagging for sprint 3.

Log in or register to post comments

Comment #9

hunmonk commented 2 June 2012 at 04:05

Status:

Needs review

» Postponed

progress today, got the missing machine name stuff worked out, and hammered on the summary page of all projects, it's now working perfectly.

the other usage pages really need a working project_release module to finish/test, and the tests are very simple to verify once the module has been fully ported, so postponing the rest of the work until project/project_release are more fully formed.