I'm wondering if we should switch to 1.2.0 for the upcoming release?
This may indicate a rough cut to the divergence of the latest
development branch 1.1.5 and the current cvs tree.
Any suggestions or constraints?
Stipe
[EMAIL PROTECTED]
Jacob Vennervald Madsen wrote:
Will that be a new development version or stable?
AFAIK, we thought of taking down the two way approach of having one
development tree and one stable tree at the same time living parallel.
It very tricky to have those two coexist, especially when there is a
lot
-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED]]
Sent: 26. marts 2002 11:10
To: Jacob Vennervald Madsen
Cc: [EMAIL PROTECTED]
Subject: Re: [RFC] new release version number?!
Jacob Vennervald Madsen wrote:
Will that be a new development version or stable?
AFAIK, we
Jacob Vennervald Madsen wrote:
Instead we should tag the current cvs to 1.1.6 and warp it to 1.2.0 as
soon as we feal stable on that?!
Good idea.
Will the documentation be updated as well?
There are a lot of new features that should be documented
and some of the old features are
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
Nick Clarey wrote:
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
habit of releasing a development version that is a
stable release candidate. That way we get the CVS version into heavier
use so some bugs may still be found.
That would be ideal, if we had a release manager. But releasing only a
stable
release would minimize the work.
Making a new release
release? Who is coordinating the
development? As I understand the initial team as been discontinued...
Making a new release is a question of changing version number and
updating the CVS I guess.
--
Andreas Fink
Fink-Consulting
for example).
Is there a project for a near release? Who is coordinating the
development? As I understand the initial team as been discontinued...
Making a new release is a question of changing version number and
updating the CVS I guess.
--
Andreas Fink
Fink-Consulting
I wuldn't say it's too stable yet. I've tried the DLR implementation on a
few boxes and a few SMSC's. Thanks to Andreas latest fix for the SMPP it
doesn't crash when getting the DLR from the SMSC, but it doesn't work.
Well on my SMSC it works in a productive environment since a few months.
I
that is a
stable release candidate. That way we get the CVS version into heavier
use so some bugs may still be found.
Making a new release is a question of changing version number and
updating the CVS I guess.
+ giving out a release notice with list of changed things. I guess
...
PMD
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Stefan Cars
Sent: quinta-feira, 10 de Janeiro de 2002 11:50
To: [EMAIL PROTECTED]
Subject: Re: New release
I wuldn't say it's too stable yet. I've tried the DLR implementation on
a few boxes and a few
is coordinating the
development? As I understand the initial team as been discontinued...
Making a new release is a question of changing version number and
updating the CVS I guess.
--
Andreas Fink
Fink-Consulting
--
Tel: +41-61
13 matches
Mail list logo
