On Apr 24, 2012, at 10:18 AM, Tom Browder wrote: > Can I do that officially somehow? We don't have means for a 7.20.4.N > release do we?
The mechanism for source distributions is to post a patch file and update the release notes README file. There can be multiple patch files for a release as it's expected they're all independent; and users will download and apply all patches available sequentially (they should be numbered). For binary releases, we haven't strictly needed to backport since it's easy enough to just post the next release iteration a couple weeks later. It's only because of big development surges (like the Coverity fixing effort) that monthly iterations tend to get skipped since it takes longer to restabilize trunk for sync to STABLE. If we had to, we could post 7.20.4.N binary releases, pull specific changes to STABLE (like was done for 7.20.6), or create and stabilize a release or maintenance branch. Cheers! Sean ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
