On Wed, May 2, 2012 at 4:31 PM, Douglas E. Engert <deeng...@anl.gov> wrote:
> On 5/2/2012 8:22 AM, Jean-Michel Pouré - GOOZE wrote: > > Le mardi 01 mai 2012 à 21:00 +0300, Kalev Lember a écrit : > >> > >> What I am looking for is an official release, something that Linux > >> distributions could pick up. A snapshot of another development branch > >> wouldn't really help me here, but I appreciate the suggestion. > > > > At some point, the SM branch will deprecate other branches: > > * This is where most development is done. > > * We have a complete approach of a quality circle, starting with > > frequent updates and ending with package releases and automatic testing. > > > > OpenSC hackers are encouraged to switch to SM branch. > > That still does not answer the questions: What will be in the next > "Official" release and when? > > Will SM be in it? > > The SM branch has pulled in many other changes (including > my C_Derive changes) that I would like to see in the next release. > If the SM branch is not going to be the bases for the next release, > then we need to look at what change in the SM branch can be pulled in > to the release. > > Martin, I would like to hear your comments. > Also do I. I still propose to merge the SM branch into the github:OpenSC-staging and prepare it as candidate for release . It should not be difficult, recently both branches has been synchronized. One more argument is that the alternative CI server should soon be ready for the automatic packaging and later for the automatic testing. It could be useful when preparing new release. > Kind regards, > Kind wishes, Viktor.
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
