"force" feature requests into CVS on Drupal project?

+1. i love it.

we don't yet have a project_issue_drupal_org.module, but we could sure use one. ;) that'd be much easier than trying to make this sort of behavior generic enough to be potentially useful (or at least, not harmful) to other sites. i'd still be in favor of putting project_issue_drupal_org.module (or whatever reasonable name we can come up with) directly in the project_issue directory (or a subdir) instead of a whole new project, since i think other users of project_issue might want to see the sorts of customizations that are going on at drupal.org. i often see issues where people are asserting (incorrectly) that "the version of project running on drupal.org *must* be different, since XXX", which isn't true.

of course, we'd probably also want a 1-time script that finds all existing issues that aren't right and resets the version with basically the same text...

webchick if you want to spear-head the effort, i'd be happy to review and commit this stuff to project_issue, maintain it, and make sure killes installs it on d.o. i just need to focus on the release system for now, so i'd rather not work out all the actual code.

thanks!
-derek

p.s. from the stand-point of moving the project-related code to being more clean and modular, i've been splitting functionality into separate modules (project vs. project_issue and now project_release). eventually, some of the hard-coded node types could be customizable (so you could apply project_issues to any kind of node, not just a project_project node). however, for the sake of over-all simplicity for this particular issue, maybe we just want a global project_drupal_org.module for all d.o-specific customizations across the whole family of project-related modules. technically, it's a little weird this way, but it's sort of a hack to begin with. ;) i suppose we could always start by putting everything in project_drupal_org.module and eventually re-organize the code later if it turns out to be a problem.

Don't we automatically move issues from fixed to closed after a certain amount of time? That seems like a site specific kind of thing to me. Where is that handled?

Wherever this stuff ends up they should probably be together.

Don't we automatically move issues from fixed to closed after a certain amount of time? That seems like a site specific kind of thing to me. Where is that handled?

yes. it's at the end of project_issue_cron() (hook_cron) in project_issue.module, starting around line 114. i don't think it's all that site-specific, but we should probably add a setting to control the time period (which could also be used to disable the behavior if you don't want it, e.g. if you enter a period of 0, that means not to do it or something)...

but, that's off topic for this discussion. ;) when/if this drupal.org-specific project customizations module exists, we can generate new issues for moving code into it for behavior that's currently in project.module and friends that a) can't be easily customizable and b) is entirely specific to our needs. any functionality that we want to debate moving should be in its own issue/patch, since we'll want to handle them all separately.

let's leave this issue for discussing the task at hand: a new feature to prevent feature requests against core that aren't for the "cvs" version, and a 1-time script to move all mis-classified issues to the right version...

thanks,
-derek

re #7: personally, i'd rather we did this like project_issue_cron() does for closing issues that have been fixed for N days, instead of a silent SQL query. it'd be nice to actually save a new comment that explicity moves the version with the appropriate text, so that the owners/submitters of these issues see the issue was bumped, and why...

others might disagree, however, so i won't spend any more time on it than this. ;)

thanks for all the effort on this, webchick!
-derek

There's no "cvs" version anymore but it would be nice if feature requests automatically got bumped to the next version of Drupal when it opens up.

Michelle

Is there any development with this feature, or should the report bee marked as won't fix? If I remember well, there is another request to automatically pass the unresolved feature requests to the latest Drupal version.

Closing old issues.