Release Management

[posbis]

Ultra VNC and its associated sub-projects such as SC-II is really great value for the community. But I must say that the release management is really kind of not so effective.

- There is a release Tabbed-Viewer here and a release of Repeater there.
- WinVNC (server) hasn't been updated since a long time (officially still 1.01)

Wouldn't it make sense to release bundles in regular time frames ? Such as other OpenSource products do ?

I mean Ultra VNC 1.5 or 2.0 , SC-3 with corresponding Repeater(s) for Windows and Linux and a matching WinVNC (server).

- Why is Repeater development handled outside of SourceForge ?
I mean on http://koti.mbnet.fi/jtko/uvncrepeater/ there are new versions v0.11/v0.12 but on SF there is still the old v0.07.

I really love the product but I think development life cycle should be streamlined a little bit.

I see a lot of people spending hours (forums) in configuring SC-2/3 configurations and helping each other assembling the right versions to get a running configuration. This process should be simplified by releasing matching component bundles and maybe an easier configuration wizard (I know there exists creator; btw. why is it not part of the SF download page ?) which automatically does all the work for not so experienced users.

Don't take this as a bad criticism of the project or involved persons but it just should show you how the life cycle of the project and the www.uvnc.com site is seen from outside people.

Kind regards and thank you for this project
Oliver