Branching Code

[MisterX]

This is true in the example of filter "" without in x

I release mostly stacks and have to be wary of this...

But that is the price to get faster functions you dont have
to write for yourself (past a certain version naturallly).

I know I complain a lot about quality issues but remember that
versions + platforms is very hard to do for RR.

Much harder than our 3 dozen functions we write into one app.
Granted they are supposed to work (given flawless code) and 
I got my share of crashing stacks without flawed code but 
Im sure RR listens...

If we (rr users) keep promoting RR as the ultimate toaster
we are bound to get some benefits.

It's always two way street...
How many of you have told the slashdot or Dr Dobbs community
that RR is a great toaster lately?

cheers
Xavier

> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com
> [mailto:use-revolution-bounces at lists.runrev.com]On Behalf Of Brian
> Yennie
> Sent: Sunday, June 27, 2004 18:21
> To: How to use Revolution
> Subject: Branching Code
> 
> 
> All,
> 
> As I approach a product release myself, something is in the works which 
> strikes me as related to Revolution. Code branching.
> 
> For me, I have version 2.1 of a product coming out. This means we'll be 
> creating an older 2.0 branch of our code. Purpose? So that we can 
> provide bug fixes for existing 2.0 customers without forcing them to 
> upgrade to 2.1 which a) costs extra money b) possibly has it's own 
> (new) bugs.
> 
> Sound familiar?
> 
> Any chance Revolution will start keeping at least two branches of code? 
> It seems like there hasn't been one _solid_ release yet as far as 
> bugginess. Don't get me wrong, lots of it works. But whenever someone 
> is stuck they have to wait for the new version... pay extra (if their 
> license expired)... and then find new bugs. And the old version never, 
> ever gets fixed because it's old.
> 
> Thoughts?
> 
> - Brian
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution