My process: 0) Code and test on my laptop 1) Look at install.xml to figure out what the next version will be 2) Edit strings.txt with a note about the changes 3) Check in my source code (local RCS revisions) 4) Run my "publish" script to make a new version in my "test" repo, including updating version and uuid in install.xml 5) Run an rsync command to publish zip & repo files to the web 6) Install and test on my main home system 7) Run my "promote" script to copy the test zip to the live repo and update the live repo xml 8) Another rsync command to publish
The "publish" script uses my Perl "mkrepo" script to update my repo xml files and some html that are used in my main web page; I've put that script online, with a link on the SD wiki. My "publish" and "promote" are still private. I don't use PluginBuilder at all b/c I dislike how the internal .par it builds makes it more difficult for others to read my source. -- peterw http://www.tux.org/~peterw/ free plugins: http://www.tux.org/~peterw/#slim AllQuiet BlankSaver ContextMenu FuzzyTime KidsPlay KitchenTimer PlayLog PowerCenter/BottleRocket SaverSwitcher SettingsManager SleepFade StatusFirst SyncOptions VolumeLock ------------------------------------------------------------------------ peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107 View this thread: http://forums.slimdevices.com/showthread.php?t=63623 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
