On Wed, 2010-12-15 at 11:07 +0100, david blanchard wrote: > I'm a bit lost regarding the 'make' process when we merge or push - > I'd like to confirm if every step should be followed or if some > commands should be avoided for now : > * after merge -> make upgrade
When you merge from trunk, yes - I'll try to make sure that the version on trunk doesn't contain obvious issues with upgrades, and refrain from merging branches that create those issues. > * before push -> make check and make release You only need to make a release if you have altered the database schema or need to modify a file specific to each installation (such as the config.php files or .htaccess). make check should be run before every commit yes - once the current issues with tests are solved, it will allow to confirm that the code is clean, properly covered and to catch a portion of the bugs that the modifications may have introduce. Right now it's a bit difficult to use given the number of errors that it shows (same thing about make debug). > * others (need to do it ? and when ?) : make backupdb and make restore > db The others are just helpers - they are meant to automate some common operations, but if you don't need them, you don't have to run them : ) Xavier. _______________________________________________ Farsides mailing list - [email protected] Wiki: http://farsides.com/ List: http://farsides.com/ml/ Forum: http://farsides.com/forum/ Ideas: http://farsides.com/ideas/ Chat: http://farsides.com/chat/
