Stipe Tolj wrote:
>>Maybe its time to do a 1.1.6 release soon.
> +1 from me.
Uh... Don't forget that 1.1.5 was a 1.2 candidate. In this situation my
opinion is that releasing the current CVS as 1.1.6 would mean that
releasing kannel 1.2 will take huge leap to undetermined future since so
much new features has been added to CVS after releasing 1.1.5 and they
would still need some stress testing under sifferent circumstances that
releasing them in a development release would give.
Dark had already in start of June a plan to make 1.1.6 as a bug fix
release on 1.1.5 and then roll it out as 1.2. I think that the reason
for 1.1.6 and 1.2 not rolling out was some bugs in the smsc_at-driver.
So I propose that 1.1.5 is nominated as Kannel 1.2 and the current CVS
is then released as Kannel 1.3. To make 1.2 a real stable release with
smsc_at somebody should then go through the bug fixes for the module and
add them onto 1.2 and the outcome would be 1.2.1. The benefits for this
procedure (IMHO, again):
- some historical load would be dropped off our shoulders; even those
most conservative people who use only the stable releases would have
reason to upgrade and there would be no more need to support 1.0.x
series
- the gap in the source code between the stable and development releases
wouldn't be that huge. And cleaning the table after Wapit's
destruction would do good for the project
> How do be tag and roll new releases anyway? -- Are we still stuck in
> the proclamation of the Kannel Foundation?
No, we are still living the time BKF (before Kannel Foundation) so the
idea is that there is a head architect and a release manager who decide
by themselves when and what to release. There just ain't those people
right now; thank to 3G Lab people there is at least somebody who would
be ready to take the responcibility for the latter. =)
--
Tuomas Luttinen
Application Developer -- Reach U
**************
