I had to make several tweaks to get projects up and running far enough to test security releases. It hasn't been excercised much lately and has coderotted a bit.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1358602-fix-release-issues-in-profile.patch | 2.32 KB | bdragon |
I had to make several tweaks to get projects up and running far enough to test security releases. It hasn't been excercised much lately and has coderotted a bit.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1358602-fix-release-issues-in-profile.patch | 2.32 KB | bdragon |
Comments
Comment #1
dwwTrue, but can you be more specific? ;) It's hard to fix "random lossage".
Thanks,
-Derek
Comment #2
bdragon commentedPatch attached.
In addition to this, some of the project stuff now requires solr, so I have the following running locally but would like advice as to whether or not we want everyone to be installing solr (I happened to have a solr server running already so it "just worked" for me...)
Since going to /project downright crashes without enabling the solr stuff, it is probabaly a good idea to force them to be enabled....
Comment #3
bdragon commenteddww: I was allocating an issue nid for use in my commit message, sorry I was not more clear about that ;)
Comment #4
dwwAhh, basically you're just working around the limitations in project_release until #642106: Add native support in project_release for a "Release type" vocabulary and #642110: Add native support in project_release for a "Security update" term are done. I wouldn't mind code comments to that effect before commit, but otherwise, looks fine to me. I haven't tested, but assuming it works (and I trust you), please go for it.
Re solr: let's move that debate to a totally separate issue please. I have strong concerns about that, but I'd rather not debate them here. ;)
Thanks!
-Derek
Comment #5
bdragon commentedAgreed on all counts.
Added references to the issues you mentioned. Committed.
http://drupalcode.org/project/drupalorg_testing.git/commit/efba4bb970346...
Comment #6
bdragon commentedsolr concerns split off to #1358648: Enabling solr is necessary to avoid crashes in some places.
Comment #7
dwwYay, thanks!