Releases of jedmodes

[G. Milde]

On  4.06.06, Jörg Sommer wrote:
> Hallo G.,
> 
> G. Milde schrieb am Tue 30. May, 11:43 (+0200):
> > On 29.05.06, Jörg Sommer wrote:
> > > 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
 
> I don't see any problem, why this could not be CVS. But if someone
> is in doubt, I would ask on debian-devel.

>From the Debian policy:

   get-orig-source (optional)
   
   This target fetches the most recent version of the original source
   package from a canonical archive site (via FTP or WWW, for example),
   does any necessary rearrangement to turn it into the original source
   tar file format described below, and leaves it in the current
   directory. 
   
   This target may be invoked in any directory, and should take care to
   clean up any temporary files it may have left. 
   
   This target is optional, but providing it if possible is a good idea. 

So you are right, as FTP and WWW are stated as example, CVS is
principially possible, if it is a "cononical archive site" for the
original source.

However, for historical reasons, the Sourcforge CVS is no "canonical
archive site" for the Jedmodes repository:

 * some modes are not put under CVS but present in the working copy at
   jedmodes.sf.net/cvs/modes/
 * the update script for this working copy does some fixes that are hard
   to doe in the CVS itself:
     # fix apsconf permissions 
     # (executable in the Jedmodes CVS repository due to upload from Windoof)
     chmod a-x apsmode/apsmode.sl apsmode/apsconf/aps* apsmode/apsconf/*.ssh

     # and a2ps README name
     mv a2ps/README a2ps/a2ps-README
     
 * there are plans to move the CVS repository to SVN (so the URL/download
   command will change)
 * at least in the past, Sourcforge's CVS was not really stable
 * the File Release System (FRS) is robust and guarantees a stable URL for a
   long time.
   
This is why I propose the following:

 * During the early development cycle of a new jed-extra package,
   bugfixes are done upstream whenever possible and "pre-releases"
   created at jedmodes.sf.net/cvs/ with a 3-parts version number.
   
   Currently this is jedmodes-2.1.3.tgz. The next pre-release will be
   jedmodes-2.1.4.tgz. The past practice of "silent upgrading" a
   pre-release without changing its name will not be repeated any more:
   the content of a pre-release will not change after it appears as
   download target in the jed-extra changelog in the SVN. 
   
 * For the jed-extra release, the tested upstream pre-release is
   published at the FRS. The next FRS release will be jedmodes-2.2.tgz.

 
> I would say, we should use
>   cvs -z3 -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/jedmodes export -r HEAD mode
> as the new source of upstream files. 

This will fail as Sourcforge changed the CVS URL. Maybe you have luck with

>   cvs -z3 -d:pserver:anonymous at jedmodes.cvs.sourceforge.net:/cvsroot/jedmodes export -r HEAD mode

> This way we could checkout older version if some contains errors.

I did not catch that. IMO, HEAD means the most current version -- what
did I miss?

OTOH, we can also replace some files in the pre-relase with separately
downloaded older versions from the CVS if needed.

Günter