7.x 3.x classics

Hi Shea,

Will you please take a look at this. It's curious. There seem to be changes that I didn't make...
Also, I updated the changelog, but I didn't quite know what to put for the tag since I'm not creating a tag. How does that work?
CLASSICS-62

Caryl
Cool! I'll keep my paws off the changelog. 


Caryl 
--- 
Caryl J. Westerberg 
Web Producer, Stanford Web Services 
cjwest@stanford.edu 


----- Original Message -----

From: "Sherakama" <notifications@github.com> 
To: "SU-SWS/stanford_courses" <stanford_courses@noreply.github.com> 
Cc: "Caryl Westerberg" <cjwest@stanford.edu> 
Sent: Friday, August 15, 2014 2:39:54 PM 
Subject: Re: [stanford_courses] 7.x 3.x classics (#29) 



In modules/stanford_courses_person_reference_views/stanford_courses_person_reference_views.info: 
> @@ -10,4 +10,4 @@ features[ctools][] = views:views_default:3.0
>  features[features_api][] = api:2
>  features[views_view][] = courses_reference
>  features_exclude[dependencies][ctools] = ctools
> -project path = sites/default/modules/stanford/stanford_courses/modules
> +project path = sites/all/modules/stanford/stanford_courses/modules 


You can place whatever notes into the changelog.txt you wish. It will all help but I would focus more on creating good commit messages. When I release a new version I will scan back though the history of commits and take out the commit messages that have value to them. If a commit message doesn't make sense or doesn't tell me enough I will have to read what changed in the commit. From there I get a list of things that have changed. 

Don't worry about creating a version number in the changelog. That will be created when the next release happens. 

Thanks Caryl 

— 
Reply to this email directly or view it on GitHub .