Re: [Ming-dev] Future Stable vs Development branches?

[Justin C. <ju...@sa...>]

(re-post after accidentally replying only to Klaus - Sorry Klaus)

Klaus Rechert wrote:
 > Hi Justin,
 >
 > I see your point but I still have some concerns:
<snip>
 > If you develop for some time only in CVS the next release (say 0.5 or 
0.6) will be a bumpy ride for developers and also for users. The 
problems you experience right now are caused by exactly the same 
release/development process you propose.

Yep, but I think the main difference here is that from the 0.4.x 
*release version* (0.4.1?) onwards, there will be enough features in it 
that _most_ apps won't need to be on the "development stream" 0.5.0.

Sure, cutting edge ones will, and they're going to have no choice but to 
keep with more cutting edge code.

But that won't be the majority of things using Ming.


 > Ming 0.3 is old and (kind of) stable. Very few release were made in 
between. So it was difficult to propagate changes and give users time to 
adopt.

Agreed.  It's going to be a fairly large transition in this instance. :(

As an aside, earlier today I started looking at moving Salasaga to use 
Ming 0.3.0 instead.  Wow a lot of stuff has changed between 0.3.0 and 
even beta5. (sigh)


 > But currently *any* release style is better then the current one.

Heh.  Oh, we *have* a release style at the moment? ;->


 > Thanks for caring that much about MING!

No worries.

Its in my direct best interest -> need something to produce swf for 
Salasaga. :)

Regards and best wishes,

Justin Clift

 >    Klaus


-- 
Salasaga  -  Open Source eLearning IDE
               http://www.salasaga.org