[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [octave forge] releasing (was: ... and template Makefiles)
From: |
Olaf Till |
Subject: |
Re: [octave forge] releasing (was: ... and template Makefiles) |
Date: |
Thu, 28 Mar 2019 15:23:35 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Wed, Mar 27, 2019 at 04:59:43PM -0700, Mike Miller wrote:
> On Wed, Mar 27, 2019 at 23:12:00 +0100, Olaf Till wrote:
> ...
> > tag the release changeset in the repository (only for 'community'
> > packages)
>
> Are any packages that would be going through this process *not* in this
> category?
The process of publishing is the same for both categories. The process
of reviewing may possibly be less strict for 'external' packages (?),
but I think checking licenses is important, and it should be possible
to generate the release from the OF repository.
> > From now on, we should inform each other before we start to publish a
> > certain release, so that the other(s) don't try to do it at the same
> > time. Since we don't know if and when Oliver comes back, we should
> > notify him also.
>
> Ok, how about we add a comment on the release tracker itself before we
> start to work on a particular package?
You're right, let's do it this way.
> > 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).
>
> So updating news.html for now means
>
> 1. scp ${username},address@hidden:htdocs/news.html .
> 2. edit news.html
> 3. scp news.html ${username},address@hidden:htdocs/news.html
>
> and then at some point in the future, periodically copy it into
> project-web and hg commit / push?
That's what I meant.
> Is there a reason to avoid commits to the project-web package?
The only reason has been not to clutter the repository with too many
changesets. I daresay it wouldn't do much harm, though, to commit any
news.html change. If you like, we can try to keep news.html in sync.
Olaf
--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net
signature.asc
Description: PGP signature
- Re: [octave forge] releasing (was: ... and template Makefiles), (continued)
- Re: [octave forge] releasing (was: ... and template Makefiles), Olaf Till, 2019/03/23
- Re: [octave forge] releasing (was: ... and template Makefiles), Olaf Till, 2019/03/24
- Re: [octave forge] please give me access again, Olaf Till, 2019/03/24
- Re: [octave forge] please give me access again, Carnë Draug, 2019/03/26
- Re: [octave forge] please give me access again, Olaf Till, 2019/03/27
- Re: [octave forge] releasing, Andrew Janke, 2019/03/25
- Re: [octave forge] releasing, Colin Macdonald, 2019/03/25
- Re: [octave forge] releasing (was: ... and template Makefiles), Mike Miller, 2019/03/26
- Re: [octave forge] releasing (was: ... and template Makefiles), Olaf Till, 2019/03/27
- Re: [octave forge] releasing (was: ... and template Makefiles), Mike Miller, 2019/03/27
- Re: [octave forge] releasing (was: ... and template Makefiles),
Olaf Till <=
- Re: [octave forge] releasing (was: ... and template Makefiles), Mike Miller, 2019/03/28
Re: [octave forge] releasing and template Makefiles, Nicholas Jankowski, 2019/03/14
Re: [octave forge] releasing and template Makefiles, Colin Macdonald, 2019/03/14
Re: [octave forge] releasing and template Makefiles, Andrew Janke, 2019/03/17
Re: [octave forge] releasing and template Makefiles, Julien Bect, 2019/03/14
RE: Re: [octave forge] releasing and template Makefiles, JohnD, 2019/03/15