Releases of jedmodes

G. Milde g.milde at web.de
Tue May 30 09:43:35 UTC 2006


On 29.05.06, Jörg Sommer wrote:
> Hello G.,
> 
> G. Milde schrieb am Mon 29. May, 11:36 (+0200):
> > On 26.05.06, Jörg Sommer wrote:

> > > 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.
 
> > 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.

These will happen very infrequently. The intended use of Jedmodes is not by
a "release" but by browsing the Site and downloading individual modes.

Sourceforge FRS releases were only started because Sourceforge required it.
(The site was closed due to perceived inactivity.)
 
> > 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." 

No, I do not have the time nor a regime to decide this. (And prevent further
updates.) There is no freeze, no testing, nothing that normally would
preclude a release. Jedmodes is a collection.

> Or are everytime the modes in a sane state?

No, there is no time we can guarantee that every mode is in a sane state.

> Then we don't need these releases we can take the CVS.

Principially, Yes. 

However, the Policy says, that get-orig-source should download the
upstream from a URL (the tgz from the working copy is here to
provide a download URL for the get-orig-source target).

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

No, yes. We use CVS

  * to keep record of older versions,
  * to allow co-authoring of modes,
  * because Sourceforge wants it this way.
    (The site was closed due to perceived inactivity while the
    development was done in the Web space.)

Normally, all commits are for publication and the mode pages provide a
download link to the latest CVS version. The usability of the version is
left to the discretion of the author, usually this is a "works-for-me".

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

If I find out how to do this, I can add tags with every "release".

I can also use a new version number for every packing of a sub-release
on http://jedmodes.sf.net/cvs/jedmodes-$(VER).tgz;
However, during the first phase of testing and debugging, I preferred to
use the same version number so that fixes are immediately included in the
new test version of jed-extra*.deb. Once this first phase is over, there
should be a "freeze" of these sub-releases.


If you decide that Jedmodes management doesnot look very professional, I
agree with you. I too over the administration only because there were no
other volunteers and I do not have a webspace for the publication of my
modes.

Günter



-- 
Milde ife.et.tu-dresden.de



More information about the Pkg-jed-devel mailing list