On Mon, Jul 11, 2016 at 11:39:54AM -0400, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: > > A way to accomplish this would be to branch, run boostrap.sh, commit > the artifacts it creates, then tag the commit that includes the > artifacts and push the tag to github: > > (1) git branch release_x_prep, checkout release_x_prep > > (2) edit gitignore files so that artifacts created by boostrap.sh won't > be ignored. > > (3) sh boostrap.sh > > (4) git add/commit > > (5) git tag release_x release_x_prep, git push --tags > > Development could continue on a master branch that doesn't have the > generated artifacts committed.
Yes, doing releases on a release branch would be a very good way to handle this. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir-dev mailing list [email protected] http://xastir.org/mailman/listinfo/xastir-dev
