Nils asked me about 0.11 release plans and I think it is best to answer here.
0.) things to do before a first beta release: does anyone have a major issue we should wait for? please let us know as soon as possible. 1.) how to do a first release: edit configure.ac, run make "dist", lots of testing, put the tar.gz file online, maybe write an announcement. 2.) when to create a branch. we need to branch as soon as someone wants to commit changes, but doesn't want to have these changes in the next release. we need to branch at least once we call something a release candidate - in my point of view these are always created from the releases/opensc-new.ver.sion branch. note: a release/ branch does not necessarily imply a branch/ branch. those are only created when we want to split further development and maintenance of the latest stable version. as far as I'm concerned: I have no further big plans. so we could create a beta1 from trunk, then test a lot. check all bugs, fix as much as possible, and once it looks good go for a release candidate. Regards, Andreas _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
