Dear Douglas, > What this means is that you are not going to get many votes because > in some cases only the author can test the code. A +1 from the author > may be the most you will get!
If we look at GIThub, there is a limited numbers of OpenSC forks, which
means a relatively small workforce. Now, from a pure math, asking the
workforce to compile and test other branches is quite a heavy job.
One of the beauty of Free Software is also iterative modifications and
evolutions. This only happens if the first version of a patch is
committed fast and spreads using the Internet.
So I would be more in favor of the proposal of Viktor (I guess?) to have
all important patches go to staging rapidly. Then we compile and spread
packages daily. Previously, we had only one unstable SVN version and it
proved to be a big hunting place for bugs.
To go further and have more people reviewing and testing, we may also
have fixed-time releases, for example every 2 months. When we met at
FOSDEM one year ago, Martin said he liked project with fixed-time
releases.
Kind regards,
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
