On Fri, Sep 18, 2009 at 6:52 PM, Kent Sølvsten <[email protected]> wrote:
> The only time I have seen a weird versioning scheme like George's was a > situation where 1.0.1 was "our product customized for customer 1" and 1.1 > was "our product customized for customer 2", but I believe it is ok, if > support for that is left out of Qi4J. What Georg is talking about; Jan - Release 1.0 March - Release 1.1 April - VIP customer of 1.0 wants bug 123 fixed (but don't want upgrade). Released as 1.0.1 June - 1.2 is released with bug123 fixed as well. Assuming for a second that the bug fix requires a domain model change (could be very small). I don't see this as unrealistic. Question is if we wan to aim for this straight away, or put it in later... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
