On Jan 11, 2011, at 6:21 PM, Mr Dash Four wrote: > >>> Something like that might actually warrant a new point release of opensc >>> to make sure Linux distros pick up the fix. >>> >> >> Having a point release for every single bug fix would be overkill. So >> the question is, what's the best approach to quickly distribute >> important fixes? What would fit the workflow of the package maintainers? >> Any suggestions? >> > May be distribute a patch with the fix directly with the various > distributors and make a 'dash' release (i.e. 12.0-2) - at least that is > how it works, I think, with FC. The first thing would be an easy way to track real regressions, it would be nice if they could be gathered to Trac, so that actual changesets required to fix regressions (or other small things) could be tracked.
-- @MartinPaljak.net +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
