<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Oct 15, 2006, at 5:29 PM, Trae McCombs wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Kieran, Sorry if this is OT, but I think it sorta makes sense to say this on this thread. <BR><BR>I think the #1 problem Drupal faces is this:<BR><BR>Difficulty to upgrade.<BR></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Yes, it is off-topic. Yes, you are right. Upgrading was listed as the hardest task in the Drupal administration survey, as of right now. Survey results are subject to change.</DIV><BR><BLOCKQUOTE type="cite"><BR>I'm sure I'll get flamed for this, but... I think there should be a button, or something in the admin section that says goes something like the following: <BR><BR>Upgrade - Configure when your Drupal software is upgraded<BR><BR>1. Status<BR>Upgrade is pending - Somewhere something should say: Upgrade pending!<BR>No Upgrades present - Same place it should say: No Upgrades Needed. <BR>(wording is off, but you get the idea)<BR>other?</BLOCKQUOTE><BLOCKQUOTE type="cite"><BR>2. When are your upgrades to be run?<BR>[Nightly]<BR>[Monthy]<BR>[Only when security releases are available - does this poll <A href="http://drupal.org">drupal.org </A>? heh]<BR>[Never]<BR><BR>3. Level of upgrades [Email UID 1 (or whoever is specified) when something is done or available ]<BR>Simple Notification<BR>Download update but don't install<BR>Install upgrade but perform only when UID1 logs in and approves <BR>Automagic upgade with no user intervention needed. <BR><BR>Heh, Ok, I know I'm probably smoking crack here, and none of this is possible, BUT, from a "newbie" Drupal Administrator, this would be a MAJOR plus on helping keep things maintained. I'd personally select the Automagic upgrades. That way I wouldn't have to worry about things. <BR><BR>There is a LOT more thinking that has to go into something like this, and I know it's probably a 6.0 feature, but... it would really make managing a Drupal site a complete and utter breeze. <BR></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Most of the basics to solve this are being done by Derek right now. The basic assumption is that we need a release mechanism for contributed modules in order to do official releases that need to be pushed out to sites.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>However, I do think there are even harder parts of upgrading that we should explore like API changes, and teaching effective upgrading procedures to administrators.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Cheers,</DIV><DIV>Kieran</DIV><BR><BLOCKQUOTE type="cite"><BR>Trae<BR><BR><DIV> <SPAN class="gmail_quote">On 10/14/06, <B class="gmail_sendername">Kieran Lal</B> <<A href="mailto:kieran@civicspacelabs.org">kieran@civicspacelabs.org</A>> wrote:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hello, there are hundreds, possibly thousands of available patches in<BR>the queue for head.<BR><BR>If there are patches available that address managing large lists of<BR>items (users, nodes, comments, groups, blocks, menus) then please <BR>help identify them.<BR>Also, if there are patches that help in the discovery of Drupal<BR>settings for administrators please help to identify those patches as<BR>well.<BR><BR>These are not requests for new features to be added to Drupal 5.0.<BR>It is a request to help identify proposed solutions to user<BR>experience problems that have been identified in the Drupal<BR>administration survey. We would like to include these proposed<BR>solutions as part of the user experience survey report. <BR><BR>Cheers,<BR>Kieran<BR><BR><BR></BLOCKQUOTE></DIV><BR><BR clear="all"><BR>-- <BR> Trae McCombs || <A href="http://occy.net/">http://occy.net/</A><BR> Founder - <A href="http://Themes.org">Themes.org</A> // <A href="http://Linux.com"> Linux.com</A></BLOCKQUOTE></DIV><BR></BODY></HTML>