Release RC18 as 1.0?

Guest · Post by **Guest** » 2005-02-04 23:43

Guys,
my suggestion is simple:
- give a little order to the numbering system and stop a second to release something officially!

There are so may 'intermediate' versions out there that is difficult to predict future directions anymore. In some companies you will not be able to use RCx until it is declared 'stable' and some poeple have been waiting long the mythical date (which should have been 'after summer 2004' then 'end 2004'', now 'totally unknown')

Given RC18 has been around for such a long time and seems to be good, why don't you officially release RC18 as Ultravnc v1.0 (with internal number 1.0.0.18).
You simply need to change the name and recompile it (without any other fixes)!!

Work will of course then continue towards a 1.1 version when the rc19 testing is finished, adding the extra 1.1 SC as an extra gift. But at least a version is out there 'stable'.

This would give also a more professional image out there to UVNC (besides the great technical work!).

Guest · Post by **Guest** » 2005-02-22 20:52

I am confused on Ultravnc. Looking around for new version, I understand there are now 3 flavours of UVNC:

- Classic
- NAt2NAT
- Single Click

The Classic version is the one that should have been released as stable last year (2004), but still there are new functions put in all the time (which make it potentially 'more unstable' than in the past). Why don't you release RC18 as stable and continue development on future versions?
I think it would be a smart move, as it might well take 3-6 more months to debug the current RC19 (assuming no more functions are put in), letting people in unstable conditions.

The other two versions (nat2nat and SC) are experimental forks with some specific functionalities. But are these intended for v1.0? Will they be released together with the full one?

Post by **Rudi De Vos** » 2005-02-22 21:29

Only one...

+SC was a tryout that is waiting on RC19 (stable) to cont.
It use the same code as RC19, but certain functions are just disabled and added to make it more secure and easy to connect

+NAT2NAT use the loopback interfaces to connect. It is flavor independed, works also with Real/Tight (seperated connection exe) Does not require any code changes in vnc.

List that need to be fixed before Rel1.00
http://forum.ultravnc.net/viewforum.php?f=18

I don't think it will take that long.

Guest · Post by **Guest** » 2005-04-21 14:11

Anonymous wrote: 2005-02-22:
I think it would be a smart move, as it might well take 3-6 more months to debug the current RC19 (assuming no more functions are put in), letting people in unstable conditions.

Rudi De Vos wrote: I don't think it will take that long.

Will we see a v. 1.0 appearing? Two months and running... debugging is not finished, more versions are apprearing (SC II) and the great new web site has been left at half....

californiajeff · Post by **californiajeff** » 2005-05-06 20:28

I think they are doing the right thing and calling it version 1.0 when it is completely ready. No point in releasing something halfass like Microsoft would if you get my drift.

Guest · Post by **Guest** » 2005-06-10 10:52

well,
time runs away. 4 months have passed from that statement from Rudi: "I don't think it will take that long."

Why has 1.00 not been released? Please put something out for use!

Some of us cannot install betas for serious projects, and uvnc has been in beta for years now!

Post by **Rudi De Vos** » 2005-06-10 11:35

We are considering releasing
the latest version
as rel1

We still need to solve some driver issue (upgrade), new dll is not installed
(installer)

http://doc.uvnc.com/UltraVNC-1.0.20.7-Setup.exe
http://doc.uvnc.com/UltraVNC-1.0.20.7.zip

We need some feedback so we can upgrade the number to Rel1.0..
It would be a shame that after more then 2 years we would rel a version with stupid bugs

Please test....