Howdy, > That would be ideal, if we had a release manager. But releasing only a > stable > release would minimize the work.
The problem with that, I think is that as someone else rightly pointed out, it's quite difficult to stop commits of new features! A "stable branch" (as has been done historically) may be the best idea, and we can say that only bugfixes go on the branch. > > I think that someon from the 3GLab said that they could do the > > development release. I'd vote for a one. > > Nick, is this still true ? The problem is that I haven't had a lot of time to follow development (or even run Kannel!) for some months now. I think that Stipe might be better to handle the job, because he "keeps his finger on the pulse" of what's going on. He's also got the necessary access rights to do anything that needs doing. Stipe? See ya, Nick -- Nick Clarey, System Architect | "Sometimes when you fill a vacuum, 3G LAB | it still sucks." - Rob Pike p +44-1223-478900 fx +44-1223-478901 |
