[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [octave forge] releasing (was: ... and template Makefiles)

From: Mike Miller
Subject: Re: [octave forge] releasing (was: ... and template Makefiles)
Date: Thu, 28 Mar 2019 12:02:17 -0700
User-agent: Mutt/1.10.1 (2018-07-13)

On Thu, Mar 28, 2019 at 15:23:35 +0100, Olaf Till wrote:
> 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.

I see, so for external packages the release has already been made
externally, it's more of a light review simply to approve posting the
release on the Forge site. Got it.

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

Not that important, just making sure I understand :)

I will try to set aside some time soon to review a couple packages.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]