My application has an icon file which is stored in version control.  Now tomorrow I might  decide to change the icon.  I'm debating between two possible naming conventions for the icon file:Keep the filename fixed, e.g., application.icoHave the filename reflect the nature of the image, e.g., happyface.icoOption 1 doesn't say what the file is.  It could give the illusion that two wildly different images are somehow different versions of the same thing.  With option 2, I'd not only have to add a new file and delete the old one, I'd have to modify the resource file to reflect the new icon filename.On a related but different angle:A website with a header image.  Is the filename header.jpg or sunrise-family-smiling.jpg?Should image file names reflect their function in the application or their content? What would be a best practice for this?
File naming convention for images stored in version control?
version control;naming;binary
Option 1 doesn't say what the file is. It could give the illusion that  two wildly different images are somehow different versions of the  same thingWell, it is, isn't it? I know that it might have changed from a smiley face to a corporate logo, but it's still different versions of a specific icon in your application.I think you're missing the point by focussing on subversion. The key deciding factor should be the application itself. When I'm adding the icon that appears in the title bar, I'm not thinking I must describe the content of the image. I'm thinking what is this image to the application, or to anyone else who needs to change it later?And therein lies a bigger point. When I come to change it later, do I really want to change the name of the image in the application? It's still doing the same thing, so why does the app need to know I've changed it?