From: Pascal B. <pa...@dy...> - 2000-11-07 19:05:03
|
I definetly like this activity on the DynAPI.. (we actually made the top-something a few times at sourceforge homepage :-) There's just one thing: releases.. I know we all agree on the fact of having only one release version, but maybe there should be 2 versions. One fully-tested "bug-free" version, and one latest version that should be in some sort of Beta fase, containing new code modifications that still need some heavy testing. This way people with "real-life" projects can use the stable version, and all others can download the latest beta update there projects and see if everything still works (this would mostly be developers playing around with dhtml projects) This would give use time to give all the new code a little time to be tested fully before the final release has it all.. Luckily we can have multiple downloads at Sourceforge.. so maybe we'll only need to add some extra notes to releases, or use Beta in the filenames.. just some ideas ofcourse. There have been some major changes to some of the important code (like the events and dynlayer objects), and I'm not sure everything works ok, so to make this the "latest" release might not be the correct name for it Other note, On what platforms are we testing these things? Most of use are using either one of these: IE4,IE5+ WinXX/win2000/winNT NS4.x WinXX/win2000/winNT Mozilla (although Milestone18 sucks big time) but how about Linux IE,NS ? Mac IE? Is there somebody out there that has access to these platforms and is capable of testing the DynAPI? cya, Pascal Bestebroer pa...@dy... http://www.dynamic-core.net |
From: Dougal C. <do...@gu...> - 2000-11-07 19:16:25
|
On Tue, 7 Nov 2000, Pascal Bestebroer wrote: > I definetly like this activity on the DynAPI.. (we actually made the > top-something a few times at sourceforge homepage :-) > > There's just one thing: releases.. I know we all agree on the fact of having > only one release version, but maybe there should be 2 versions. One > fully-tested "bug-free" version, and one latest version that should be in > some sort of Beta fase, containing new code modifications that still need > some heavy testing. Personally, I was disappointed when you turned off CVS. Of course, if the developers aren't using it to commit changes, I guess it doesn't do much good. But for other projects I track/contribute, it's really convenient to just do a "cvs update" and have it fetch all the recently modified files for me. On the Thatware project (http://thatware.org/ or http://sourceforge.net/projects/thatware/), we do the usual: we use CVS to perform updates for bleeding edge code. Every once in a while, the project leader calls a feature freeze, and we can only commit bug fixes. Then once things seem calm, he makes a new release from the CVS and we open the floodgates for new (buggy :) code again. -- Dougal Campbell <do...@gu...> <URL:http://www.gunters.org/!dougal/> Professional Jack of All Trades |
From: Pascal B. <pa...@dy...> - 2000-11-07 19:26:12
|
big problem here is that most of us can't get CVS working correctly. (yeah, yeah.. windows users :) I know there's a win32 client for CVS somewhere, but haven't tried it (and haven't actually found it, which is ofcourse contributing to the fact of me not trying it) I think Robert is doing a GREAT job keeping up with all patch submissions here.. cheers! Any comments/ideas on CVS or other version controlling? Pascal Bestebroer pa...@dy... http://www.dynamic-core.net -----Oorspronkelijk bericht----- Van: dyn...@li... [mailto:dyn...@li...]Namens Dougal Campbell Verzonden: dinsdag 7 november 2000 20:16 Aan: Dev Onderwerp: Re: [Dynapi-Dev] Version controll or something On Tue, 7 Nov 2000, Pascal Bestebroer wrote: > I definetly like this activity on the DynAPI.. (we actually made the > top-something a few times at sourceforge homepage :-) > > There's just one thing: releases.. I know we all agree on the fact of having > only one release version, but maybe there should be 2 versions. One > fully-tested "bug-free" version, and one latest version that should be in > some sort of Beta fase, containing new code modifications that still need > some heavy testing. Personally, I was disappointed when you turned off CVS. Of course, if the developers aren't using it to commit changes, I guess it doesn't do much good. But for other projects I track/contribute, it's really convenient to just do a "cvs update" and have it fetch all the recently modified files for me. On the Thatware project (http://thatware.org/ or http://sourceforge.net/projects/thatware/), we do the usual: we use CVS to perform updates for bleeding edge code. Every once in a while, the project leader calls a feature freeze, and we can only commit bug fixes. Then once things seem calm, he makes a new release from the CVS and we open the floodgates for new (buggy :) code again. -- Dougal Campbell <do...@gu...> <URL:http://www.gunters.org/!dougal/> Professional Jack of All Trades _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
From: Scott A. L. <sc...@sc...> - 2000-11-07 19:40:58
|
I use WinCvs here at work...it works great but be prepared for a steep, non-intutitive learning curve: http://www.wincvs.org Pascal Bestebroer wrote: > > big problem here is that most of us can't get CVS working > correctly. (yeah, yeah.. windows users :) I know there's a > win32 client for CVS somewhere, but haven't tried it (and haven't > actually found it, which is ofcourse contributing to the fact of > me not trying it) > > I think Robert is doing a GREAT job keeping up with all > patch submissions here.. cheers! > > Any comments/ideas on CVS or other version controlling? > > Pascal Bestebroer > pa...@dy... > http://www.dynamic-core.net > > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Dougal Campbell > Verzonden: dinsdag 7 november 2000 20:16 > Aan: Dev > Onderwerp: Re: [Dynapi-Dev] Version controll or something > > On Tue, 7 Nov 2000, Pascal Bestebroer wrote: > > > I definetly like this activity on the DynAPI.. (we actually made the > > top-something a few times at sourceforge homepage :-) > > > > There's just one thing: releases.. I know we all agree on the fact of > having > > only one release version, but maybe there should be 2 versions. One > > fully-tested "bug-free" version, and one latest version that should be in > > some sort of Beta fase, containing new code modifications that still need > > some heavy testing. > > Personally, I was disappointed when you turned off CVS. Of course, if > the developers aren't using it to commit changes, I guess it doesn't do > much good. But for other projects I track/contribute, it's really > convenient to just do a "cvs update" and have it fetch all the recently > modified files for me. > > On the Thatware project (http://thatware.org/ or > http://sourceforge.net/projects/thatware/), we do the usual: we use CVS > to perform updates for bleeding edge code. Every once in a while, the > project leader calls a feature freeze, and we can only commit bug fixes. > Then once things seem calm, he makes a new release from the CVS and we > open the floodgates for new (buggy :) code again. > > -- > Dougal Campbell <do...@gu...> <URL:http://www.gunters.org/!dougal/> > Professional Jack of All Trades > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
From: Robert R. <rra...@ya...> - 2000-11-07 19:47:11
|
I wish we were using CVS, but I have a feeling that no one would be using it. When we had it before, no one used it. One good thing is that we would not need to have beta releases (see other topic). We would have automatic nightly builds, since sourceforge does that for us. CVS is not easy to setup in Windows, but it can be done by just following the instructions at sourceforge. It also requires you to instll ssh. I think we should either use CVS or have beta releases. \\Robert -- rra...@ya... |
From: Jordi 'I. M. <jmi...@or...> - 2000-11-08 17:28:46
|
Snifff...., I haven't been able to cope with the latest flood of patches and versions. I wish I had the time, but I'm still here. I have updated mi site so the download zone brings people to dynapi.sourceforge.net, and explains that from now on that is DynAPI's home page. Mine, Pascal's an any other are just DynAPI related and contain DynAPI stuff, but I think we should make clear that there's, finally, only one version. Is it just me, or now things that used to work don't work anymore ? It is not a bad thing, though, if this is due to some changes in the APi's core that came to be necessary due to the new issues that have appeared when people tried to do more complicated things. Which is a sympthom of usage, after all. I'm happy. |