Re: [Gimp-developer] Setting Up a Release Procedure


On Tue, Dec 10, 2013 at 5:00 AM, Sam Gleske <sam mxracer gmail com> wrote:
On Mon, Dec 2, 2013 at 11:09 AM, Sam Gleske <sam mxracer gmail com> wrote:

What are the Windows packagers using for the build?  If they're using a
proprietary package system I suggest moving to a more open one such as NSIS
and customizing that.  Windows builds can easily be automated using NSIS.
Another advantage of using NSIS is checking the scriptable installer code
into SCM.

Does this mean that nobody on this list knows what the release process is
on Windows for building installers?

As Michael answered too, of course we have people in charge of the
Windows release procedure. Simply I am hoping we can improve it by
merging efforts, since several people are also known to do their own
quality release outside us. And our procedure is far from perfect. I
wish it were more systematic and without a fault.

But we do have an existing procedure since we do have releases and
code for it in our repo. And we are slowly improving it (for instance
you may have noticed the recent improvement: now all releases go in
the ftp, instead of using a third party provider).


gimp-developer-list mailing list
List address:    gimp-developer-list gnome org
List membership:

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