Martin Paljak wrote:
...
The subversion branch is called trunk. if someone uses it and want to
report a bug in this branch I imagine he knows what he is doing and
the name trunk should be reused for the version field.
Now this is a somewhat technical issue. If we had branches with ongoing
work that would address some bigger enhancements in the codebase, then
in perfect theory this would happen in the 'development branch' of a new
feature but not necessarily in 'trunk'. So 'trunk' and 'devel' could
if we have a new dev branch with major code changes and we want
users to test it (and report bugs) we could just add another tag.
mean the same (ongoing deveopment) but just 'trunk' is associated with
subversion terminology of 'trunk' while 'devel' has a broader meaning...
No matter what, we still should have only one version tag unless proven
otherwise.
well, having two tags for the same thing isn't really useful
Current score:
devel: 1
trunk: 1
votes welcome :)
well, IMHO 'trunk' is more precise.
Cheers,
Nils
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
