Well, I can't answer for the project devs but I know I'd love this. I've often wished I could add a warning to update status to remind me not to blindly update certain modules. While I avoid hacking modules whenever possible, there are some times that changes in a module's directory is unavoidable and my usual practice of deleting the whole directory before untarring the new one gets me in trouble.<br>
<br>Michelle<br><br><div class="gmail_quote">On Sat, May 3, 2008 at 1:51 PM, Daniel F. Kudwien <<a href="mailto:news@unleashedmind.com">news@unleashedmind.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi friends,<br>
<br>
Journal module will be enhanced to allow developers to manage a list of hacks and patches that have been applied to a Drupal site. I'm posting this announcement to devel list, because I guess that many devs are concurrently working on multiple projects, and have created and/or applied various patches to these sites.<br>
<br>
The goal is to track all customizations, so there is finally an answer to the question whether Drupal core and contributed modules can be updated easily when a new version is released.<br>
<br>
d.o. issue: <a href="http://drupal.org/node/254303" target="_blank">http://drupal.org/node/254303</a><br>
<br>
<br>
To make this feature rock, I could imagine a project_issue and update(_status) module integration:<br>
<br>
1) project_issue: Periodically query d.o with a list of issue numbers and update their status in Journal's patch list.<br>
<br>
2) update(_status): Add a warning to a module's entry, if there's a patch recorded in Journal that is not of status 'fixed'.<br>
<br>
Thus, I'd like to specifically ask the maintainers of project_issue and update(_status), whether these features would be supported by them.<br>
<font color="#888888"><br>
Daniel<br>
<br>
</font></blockquote></div><br>