RE: Patch submission and release policy

"Oded Arbel" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
> -----Original Message-----
> From: Harrie Hazewinkel [mailto:[email protected]]
> 
> Changelog is generated from the cvs commit messages or is it 
> neccessary
> to do it by hand?? Just wondering, since I thought ChangeLog can be
> generated from CVS itself. (I could be wrong)

The ChangeLog is written by hand. theoreticly it's possible to generate it from the CVS commit messages, but I would still recomend not to do it : writing the ChangeLog by hand forces the developer to submit clearly described patches.

> > Semantics. I don't mind what you call it, as long as we 
> have a stable
> > branch and a development branch.
> 
> Fine, but I would think that you would at least want a different
> branch for for instance the 1.2.x and the 1.3.y 
> product/stable release.

Why would I want to have two "stable" branches ?

> What people should put on their production systems is something tested
> and released as stable. I don't think that people should just take a
> CVS checkout for the production system. Those poeple take a risk where
> a released version should have been tested before release.
> IMHO, that has not much to do with branching.

You're thinking "commercial". sorry - open source doesn't work that way. Testing is done by the users, so if the users will hold for a tested release, one will never appear. we need to get things going now, by declaring the CVS as it is now "stable", package and "release" it.

> Besdies that I intended to say here that we first need to discuss
> how the architecture will be and some of those other things. After
> that we need to decide on the implementation and how to use branches.
> Maybe some things are having very little impact and thus do not need
> a special (own) branch.

I don't see why would we need more then two branches - a stable branch and development HEAD. too much branching will only slow development down. always remember that Kannel is a low visibility project with little commercial support: all development is done as needed by the users of the software. if you make it hard for the developers to develop, you won't have any development done.

--
Oded Arbel
m-Wise Inc.
[email protected]
(972)-67-340014
(972)-9-9581711 (ext: 116)

::..
Katharine : "A woman should never learn to sew, and if she does know how she shouldn't admit to it."
	-- from "The English Patient"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.