Confirmed users
884
edits
Drumbeat/website/proposal: Difference between revisions
m
→3) Install profile
Paulbooker (talk | contribs) |
Paulbooker (talk | contribs) |
||
| Line 66: | Line 66: | ||
* packaging the latest version - changes to content types and other parts of the admin interface are going to make any install profile obsolete quickly. It may be useful to write a packaging script specifically around views, content types, and blocks. | * packaging the latest version - changes to content types and other parts of the admin interface are going to make any install profile obsolete quickly. It may be useful to write a packaging script specifically around views, content types, and blocks. | ||
** Would you say that packaging a release will be best suited for when we have a configuration of our modules / themes that were looking to to hold fixed for a time ? We will probably need to look at how we will do versioning / branching but i imagine we will want some thing along the lines of a production branch which is only accepting bug fixes and and a development branch where we will be introducing new modules, .. a snapshot | ** Would you say that packaging a release will be best suited for when we have a configuration of our modules / themes that were looking to to hold fixed for a time ? We will probably need to look at how we will do versioning / branching but i imagine we will want some thing along the lines of a production branch which is only accepting bug fixes and and a development branch where we will be introducing new modules, .. a snapshot of which will later become the next production branch [booker] | ||
of which will later become the next production branch [booker] | |||