Re: [orbitcpp-list] Time for a release?
Status: Beta
Brought to you by:
philipd
|
From: Phil d. <ph...@us...> - 2000-03-20 08:23:09
|
Andreas Kloeckner wrote: > > > This will keep interest up, give people something to build and play > > with, and hopefully allow us to spot some build/test problems on other > > platforms. I hope it will also encourage more developers to help out. > > Release early, release often. I'm very much in favor of releasing now > that there is something people can usefully toy around with. Yet, I > believe we should not raise too much dust about it, such as by > announcing it on freshmeat, since what we have is still clearly > pre-alpha. But there's certainly nothing bad about having a small > internal release for people who care about the project. > Agreed. > > Of course the next issue is version number: I'm not keen on 0.30 since > > this version doesn't represent any significant increase in CORBA > > functionality. orbitcpp-0.26? > > It depends. Do you intend to do any new releases on the old python > stuff? In this case, I'd say we should choose something really > different, such as orbitcpp-devel-0.20, orbitcpp-hacker-0.20 or > orbitcpp2-0.20. If not, 0.26 is not such a bad choice, since it suggests > there wasn't much user-visible improvement, which is clearly true. On > the other hand, the people who are obeying our project will certainly > have noticed that 0.26 _is_ something radically different, so the clumsy > naming won't matter to them. Yep. I don't intend on doing any more work on the old ORBit-C++ release (except perhaps bug fixed). 0.26 it is! > > Any plan about the release date? > Err.. Today if I get the chance. Phil. |