Releases of jedmodes

[Jörg Sommer]

Hello G.,

G. Milde schrieb am Mon 29. May, 11:36 (+0200):
> On 26.05.06, Jörg Sommer wrote:
> > Hi all,
> > 
> > after some experiences with the pre-release of the jedmodes archive I
> > would prefer to have static archive which we can use to setup the
> > package. The forward and backward of patches and other problems eats up
> > time. One day you find a bug and create a dpatch, the next day the bug is
> > fixed in the upstream release.
> > 
> > If we would collect more modes from different sources in the near future
> > we will end up in a big game fixing upstream sources and wait for the
> > next release.
> > 
> > Therefore I would prefer if jedmode make every two or three month a
> > release which we use to setup a package, with all bugs they have
> > released. And I would also prefer we release in this cycle a new package,
> > maybe with 2 or 3 weeks delay.
> > 
> > What is your opinion? Would this be OK for you, Günter, Paul?
> 
> By "release", do you mean "real" releases via the Sourceforge file release
> system or inofficial "micro" releases as currently done?

I mean releases via the Sourceforge file release system.

> In any way, Jedmodes does not really have "releases" but CVS snapshots.

Right, but they mark a point where you decided "all modes are in stable
state." Or are everytime the modes in a sane state? Then we don't need
these releases we can take the CVS.

I thought you use the CVS as a development tool where not all commits are
usable. I'm wrong?

Or can you add tags to the mode which we can use to checkout a sane
version?

Jörg.
-- 
"UNIX was not designed to stop people from doing stupid things, because
 that would also stop them from doing clever things."
         -- Doug Gwyn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-jed-devel/attachments/20060529/8e20fe23/attachment-0001.pgp