[documentation] List of changed files

[Steven Peck]

Not a problem.  I over write everything per the instructions after
testing on one site so that's all.  I never see what modules been
updated.  As I said, make the page if you want it.  I believe you have
the rights to.
 
If I find a version of my site at 4.7.0 then I'd just go straight to
4.7.2.  The reason it's recommended to do each and every incremental is
that more people are doing it.  Historically some version releases prior
to 4.5 you had to occassionally add SQL tables manually  Since then
updates have just gotten better and better as the contributing devs see
improved 'safe' ways to do things.
 
If someone ever gets time, perhaps a good thing to test.


________________________________

	From: documentation-bounces at drupal.org
[mailto:documentation-bounces at drupal.org] On Behalf Of Anisa
	Sent: Thursday, August 03, 2006 7:59 PM
	To: A list for documentation writers
	Subject: Re: [documentation] List of changed files
	
	
	I am not sure I understand.  What's the difference, really, as
long as the list is accurate?
	
	My concern is there is always a bunch of problems that crop up
with each of these security releases, and I am still on 4.7.0.  So, the
provided patches don't work.  I don't know how to use the patch tools, I
am sure I could, but my program list takes up my whole screen...  and
it's extra wide.  It is recommended with each of these security updates
to upgrade to the version before it...  that would mean 3 mini upgrades
for me.  To skip all that, I only have two options, overwrite everything
with the new install, or see which files have been changed, and upload
only those.  
	
	It may not be sensible, from the programmer's standpoint, but I
don't feel very secure in simply overwriting everything.  I don't have
any control over it?, is close.  Plus, I can't find any disadvantages in
just uploading select files.
	
	Anisa.
	sleepy.
	ooo, washing machine is shaking...  not good...
	
	
	
	On 8/4/06, Steven Peck <speck at blkmtn.org> wrote: 

		There is a upgrades section if you wish to create an
appropriate page but I don't understand the logic.  
		
		http://drupal.org/upgrade/ 
		 
		There are tools patch/diff for determining file
differences (no, I don't use them often for my Drupal sites) 
		 
		With the need to run update.php for Drupal modules,
installs etc.  The new install/upgrade scripts in the next version I do
not understand why people need to ask for these lists and want to 'just
replace the changed files'
		 
		I think this is a bad idea for a variety of reasons and
in general it should not be encouraged for anyone less then a skilled
developer (or someone working towards becoming a skilled developer,
etc).  
		 
		I am certainly willing to be convinced but I just don;t
understand what it buys you and see far more of a downside to
encouraging this method of upgrading then an upside.
		 
		Curiously yours,
		-sp
		 
		 
		 
		 


________________________________

			From: documentation-bounces at drupal.org
[mailto:documentation-bounces at drupal.org] On Behalf Of Anisa
			Sent: Thursday, August 03, 2006 4:58 PM
			To: A list for documentation writers
			Subject: [documentation] List of changed files
			
			

		
	
http://www.contractwebdevelopment.com/web-development-blog/drupal/2006/7
/files-changed-by-drupal-upgrades 
		
		Can we put this page somewhere?
		
		Anisa.
		
		-- 
		*********************************
		www.AnimeCards.Org
		
		16,000 scans and counting!
		********************************* 

		--
		Pending work:
http://drupal.org/project/issues/documentation/
		List archives:
http://lists.drupal.org/pipermail/documentation/
		
		




	-- 
	*********************************
	www.AnimeCards.Org
	
	16,000 scans and counting!
	********************************* 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/documentation/attachments/20060804/cf510846/attachment.htm