Hi all,
We managed to push 0.11.1 out of the door 5 months ago. A friend of
mine pointed out that the 'vanilla' opensc (meaning the opensc that
comes with linux distros and does not have a binary build like for
Windows or Mac OS X, specially built for Estonian eID card from my
private tree) has a regression in the whole 0.11.x line (related to
changeset 2836). I would really like to get it fixed ASAP.
So I gave a look at trac - at milestones and open tickets and I made
the following conclusions:
* We don't really have nor support different branches and bugfix
releases. We have a trunk we build binary releases against (SCB, SCA
my builds for Estonians that come from a spearate branch anyway). And
we have releases we release in order and don't really look back.
Distro maintainers sometimes fix strange issues with those releases
while we seem to concentrate on the trunk again.
* This is actually not bad once we admit it. Why not to take an
approach like ubuntu? Lets just release _something_ every X months,
where X is an agreed constant (6 moths?)
* I looked through current, already passed milestones and assigned
all valid tickets to a realistic milestone we still have to complete
- that is, 0.11.2
* We still have a lot of tickets that we really don't know what to do
with - they have no real milestone and they have no real verified bug
or issue that still would be valid or we could somehow react upon.
* The collection process had no real point unless we process the
stuff. There are currently 3 milestones - 0.11.2, 0.12 and someday.
There are no other realistic milestones for issues to become fixed.
* What should we do?
- fix the small but many issues for trunk/next 0.11.x version.
There are many small tickets that relate to documentation for
example. Lets try to get the documentation into shape and keep it
like that.
- review the tickets with no milestones and no activity for months.
If the ticket looks total garbage - DELETE it. If it is a real issue
- it shall be reported again. If we can't shape the ticket into
something we could act upon - it would anyway be a waste of bits and
attention.
- Maybe we should agree on some kind of release schedule and
policy. We currently don't know if we want to release something, when
we want to release something, or why we would want to release
something. The tickets nor the milestones in trac have no real
meaning and thus everything seems to be hanging in the void.
I'm personally interested in getting a new 0.11.x version out and I
also have the needed time to make it happen.
So, I'm asking aboutt:
* your plans and ideas about next release(s)
* your input in trac to sort all the unclassified (meaning no
milestone) tickets into either actionable items or help to classify
the possible problem source. Give your input about the real
priorities of clear issues so that we could decide a release
milestone for them.
* Once we get trac into a clear and understandable shape it shall
become actually trivial to fix all those trivial issues and thus
bring the project closer to a next release.
I myself have the following goals I would like to see fixed in the
future (next 12 months or so :) ):
* re-work my pin entry and pinpad related code, so that all utilities
have uniform understanding on how to enter the pin and what to do if
we have a pinpad (for 0.12 or 0.11.x)
* bring the pin cache code closer to libopensc, so that it would not
be duplicated in tokend, pkcs11 (and future basecsp plugin on
windows) (possibly 0.12)
* Make sure that #29 is possible (future)
* Look into multi-app and threaded access (future)
* Build some test cases upon the python pkcs#11 wrapper for Estonian
eID card (and I suggest to make similar stuff for other emulated
cards, so that problems I fixed in changeset 3010 would not happen
again.) (future)
I suggest we try to follow some bits from http://www.divmod.org/trac/
wiki/UltimateQualityDevelopmentSystem and I would like to make at
least two branches for such bigger improvements on opensc-projec.org
svn.
Corrections, comments, opinions, improvements?
m.
--
Martin Paljak / [EMAIL PROTECTED]
martin.paljak.pri.ee / ideelabor.ee
+372 515 64 95
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
