RE: RFC: Change of WinCvs release advertisment strategy

> I think it's quite possible with the increased expose system. 
> We managed to
> get quite a few milestones in the beta cycle that way.

Problem was nobody could tell without trying.


> Unless of course cygwin will create another break-thru 
> release in the mean
> time ;)

Are there any news on that front? We've now got at least seven threads 
about this running on the CVSGUI list by now (plus an eighth still 
unconfirmed).

 
> things and it should be enought to make a clear distinctions 
> between stable,
> beta and latest releases. Anybody with common sense will 
> understand the
> meaning.

You wish... ;)


> People are not going to read long explanations anyway...

Yes, but at least we would be able to say "toldyaso" if they still get 
it wrong... ;]


> Let's just map the things to SF releases, e.g.:
<.snip.>

I have now made a bold move and checked in a revised download.html (and 
corresponding index.html) to CVS for your review. I haven't updated the 
htdocs yet. You probably won't like it because of the "long texts" but I 
honestly did try to keep it to a minimum. ;)
(I did try to clean up some of the HTML along the way - still a lot to 
do but that was all I had time for at the moment.)

BTW: What exactly was the reason for not declaring WinCvs 1.3.14 
"recommended" so far? I wasn't really aware of any serious issues...

Cheers,

Oliver
----	------------------
JID:	[email protected]
ICQ:	18777742	(http://wwp.icq.com/18777742)



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/