> 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.
> 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.
Any plan about the release date?
> <SHOTINTHEDARK>
> The ORBit-C++ web page is in need of a bit of a facelift. Unfortunately
> time spent keeping it up to date detracts from my hacking time. If
> anybody else fancies maintaining the site, drop me an email.
> </SHOTINTHEDARK>
Though I hate html, I'll probably have time to do it by the end of next
week - if there aren't any volunteers, that is... 8-))))
cya
andy
|
