Re: Admin support for Octave Forge

Olaf Till <[email protected]> Thu, 1 Oct 2020 09:56:48 +0200

Newsgroups	gmane.comp.gnu.octave.maintainers
Message-ID	<20201001075648.GA3325@till>

On Thu, Oct 01, 2020 at 01:26:55PM +0900, Kai Torben Ohlhus wrote:
> On 10/1/20 3:28 AM, Olaf Till wrote:
> > On Wed, Sep 30, 2020 at 08:20:34PM +0200, Olaf Till wrote:
> >> On Sun, Sep 27, 2020 at 08:39:37PM +0900, Kai Torben Ohlhus wrote:
> >>> Dear Olaf,
> >>>
> >>> Reading the OF release tracker [1], I would like to offer support for
> >>> getting releases done.  Testing the tarballs, reviewing the code, etc.
> >>>
> >>> When I get the situation right, you are the only active "Octave Forge
> >>> admin" left, right?  Thank you for keeping the OF project running the
> >>> last years!
> >>>
> >>> If you appreciate my help, can you provide "siko1056" [2] with the
> >>> necessary admin/developer rights?
> >>>
> >>> Kai
> >>>
> >>> [1] https://sourceforge.net/p/octave/package-releases/423/
> >>> [2] https://sourceforge.net/u/siko1056/
> >>
> >> Yes, gladly. 
> >>
> >> I'll do it this evening after some urgent things.
> >>
> >> Olaf
> > 
> > Done, you have now admin- (and so also developer-) rights. If you need
> > some instructions, tell me and I send them off-list.
> > 
> > Olaf
> > 
> 
> Thank you Olaf 🙂  If there is confidential information available, I
> would be happy to receive them off-list.

It's not confidential, I just wanted to limit list traffic to topics
of general interest. But there still may be something in this thread
which is of general interest, so I'll keep the list in. The attached
package-publishing-instructions are more or less the same I sent to
Mike some time ago.

> I started to make some book keeping and created a list in the wiki [1]
> how to publish an OF release.  If your time permits, feel free to
> add/correct items there.

Well, I never quite understood why such information is duplicated at
the wiki. Maybe because it's easier to edit at the wiki. There is
already such information at the OF webpage. If the wiki is preferred,
I'd suggest that the OF webpage just links to the wiki instead of
holding this information.

Similar with package documentation. Here, there were also efforts to
provide duplicated information at the wiki, and this was sometimes not
in sync with information from the package maintainer.

What regards my time, I can't pretend to be able to do much more in OF
administration now than an occasional package release.

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

publish-instructions-2020.txt (text/plain, 1.5 KB)

Put the new package tarball to:
<username>@frs.sourceforge.net:/home/frs/project/octave/Octave\ Forge\ Packages/Individual\ Package\ Releases/

It will take some minutes until the tarball is automatically copied
from there to be available online.

unpack the package html and do something corresponding to:

rsync -av --delete <package-name>-html/<package-name>/ <username>,[email protected]:htdocs/packages/<package-name>/

update <username>,[email protected]:htdocs/news.html

remember to notify the package maintainer at the release forum, the
maintainer should announce the release at the list

tag the release changeset in the repository (only for 'community'
packages)

hints:

htdocs/ (see above) at the web-site corresponds to htdocs/ in the
'project-web' package, but contains some more directories (in
particular, under htdocs/packages/, the html directories of the
individual packages), some generated files, and maybe some more
files. Note that htdocs/news.html is not necessarily always in sync
between the web-site and the 'project-web' package (the file at the
web-page being potentially newer; this is to avoid too frequent
commits to the project-web package).

I'm using a local copy of the web-site, serviced by apache2 for
localhost, and do any changes there first, before I propagate them to
the real web-site. Before I propagate the package html to Octave
Forge, I check from the local copy whether the package tarball is
already available for download.

signature.asc (application/pgp-signature, 833 B)