Here are the current release steps as of June 7, 2006 rake test (make sure no failures or errors) rake rdoc (make sure builds ok) (I do have a custom require warning that I would eventually like to eliminate from the output but not sure how to accomplish that) test locally as plugin for a rails app --------------------------------------------------------- script/generate masterview Model Controller script/server (See if the app works as it should) (make change to an app/views/masterview template file) (Refresh browser and see change immediately picked up (if in development mode) http://localhost:3000/masterview/admin (should see list) (invalidate the xhtml of a masterview template add something like </breakxhtml>) refresh browser (should show that file is not parseable (without tidy turned on) rake mv:list rake mv:list_all (both of these commands should show the same listing as webapp and should show the statuses) (fix the xhtml again by taking out the </breakxhtml>) (invalidate the imported layout of one of the mv template, for example add something to title in masterview template for destroy.) visit masterview/admin page, rake mv:list, rake mv:list_all and you should see the fact that destroy template is out of sync. Use rebuild or rebuild all link from webapp, and/or rake mv:rebuild TEMPLATE=foo.html or rake mv:rebuild_all visit masterview/admin page, rake mv:list, rake mv:list_all and you should see the fact that everything is OK Visit app pages to see everything working as should. test locally as a gem installation on another fresh rails app ---------------------------------------------------------------------------------------------------------------------------- (install local gem, if we were pulling from repository then gem install masterview_gem_pack --include-dependencies, however since we want to test before uploading to rubyforge, we need to do this locally, I don''t recall the commands to install a local gem) script/generate masterview_plugin script/generate masterview Model Controller (same tests as above) Ideally we will eventually create some system tests that we can run from rake to do all this making it easy to test (just haven''t gotten to it yet) Once all that is done we are ready to release (note that we were going to use tag latest to represent latest build but because script/plugin install uses the last part of url for directory name, we need to name the latest tag simply masterview) with subversion create release tag MASTERVIEW_X_Y_Z, remove existing ''masterview'' tag and recreate masterview tag from current this is what people will be pulliing from for plugin install rake package rake release_files RUBYFORGE_USER= RUBYFORGE_PASSWORD= (or put those in your shell environment) (this should publish the current versioned package for all of the parts (masterview, masterview_generator, masterview_plugin_generator, masterview_gem_pack) as well as a tar and zip version of the plugin up to rubyforge. It builds the release notes from RELEASE_NOTES and CHANGELOG. (eventually we will post mail announcements too, but I haven''t gotten to that yet) (At this point the new verison of files should be on rubyforge files directory, every so often I go up and remove the really old versions. I haven''t created a rake command to do this all yet) It will take a while for the gem to become available usually within a half hour or so I then test pulling the gem gem install masterview_gem_pack --include-dependencies I check that the right version came down and then do a quick rails test again. gem uninstall masterview (test plugin install) script/plugin install svn://rubyforge.org/var/svn/masterview/tags/masterview (retest) That should do it. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20060607/17a7ac90/attachment.htm