Is there any chance a branch could be created from some past release so that maintenance can be continued on something more stable (and that doesn't require a new tcl/tk version)?
It would be nice if all development didn't just march forward on the trunk with patch version numbers 23, 24, 25... I mean, if the trunk represents the future of scid that's great, but surely this represents a 4.0 release with it's primary feature being a revamped UI, no? The release engineering practices for scid are pretty much nonexistant. There is no release planning, or at least none that is communicated publicly, and no tags, no branches, nothing in the repository to assist with anything resembling release engineering. In the mean time it would be nice if folks could get bug fixes and such for the version that is stable, no matter how old and unexciting it may be. This would also allow more aggressive development on the trunk as there would be a vehicle for getting a working version to users in the mean time. If people want to try out the new hotness, that's up to them. Just wondering, Garth ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
