On Mon, Dec 2, 2013 at 11:09 AM, Sam Gleske sam.mxra...@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.
Sam Gleske sam.mxra...@gmail.com wrote:
On Mon, Dec 2, 2013 at 11:09 AM, Sam Gleske sam.mxra...@gmail.com
wrote:
Does this mean that nobody on this list knows what the release process
is on Windows for building installers?
Innosetup is used for the installers, and the scripts for it are in the
Hi,
On Tue, Dec 10, 2013 at 5:00 AM, Sam Gleske sam.mxra...@gmail.com wrote:
On Mon, Dec 2, 2013 at 11:09 AM, Sam Gleske sam.mxra...@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
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
Hi,
On Sun, Dec 1, 2013 at 12:44 PM, Jehan Pagès jehan.marmott...@gmail.com wrote:
On Sun, Dec 1, 2013 at 2:50 AM, Simone Karin Lehmann sim...@lisanet.de
wrote:
Here’s the link to the current epository (not totally complete, I’ll update
this if I find some time…. and I know, some code
Am 28.11.2013 um 22:25 schrieb Jehan Pagès jehan.marmott...@gmail.com:
Hi,
Well actually the 4 main points are:
1/ testing: right now, releases are sudden, out of nowhere, and we
discover release issues afterwards.
yes, we really need a test cycle before a release goes public. Especially if
Hi,
On Sat, Nov 30, 2013 at 11:37 PM, Simone Karin Lehmann
sim...@lisanet.de wrote:
Am 28.11.2013 um 22:25 schrieb Jehan Pagès jehan.marmott...@gmail.com:
Hi,
Well actually the 4 main points are:
1/ testing: right now, releases are sudden, out of nowhere, and we
discover release issues
Hi,
Am 30.11.2013 um 12:26 schrieb Jehan Pagès jehan.marmott...@gmail.com:
Well... that's why I was proposing testing and collaborating *before*
releasing, and not after. :-/
yes. Sadly, now the „no-outline-issue“ is another showstopper.
It’s not about building. I wrote a couple of scripts
On Sat, 30 Nov 2013 11:37:05 +0100, Simone Karin Lehmann simone lisanet
de wrote:
I just discovered a new bug, which is IMO release
critical. On OS X Mavericks, the pencil and brushes outline doesn’t show,
so it’s almost impossible to paint,
clone and brush.
Don't blame OS X Mavericks.
This wasn't a Mavericks bug; it can happen on linux too. For some
reason, this only triggered on clang. Anyway, I just fixed it in gimp
git (see commit 95becc7615c7e9cf2f6135c8d5b0fe1cca86648f).
So, this will be fixed for the next release.
-- drawoc
On Sat, Nov 30, 2013 at 9:26 AM, Maurizio
Hi,
On Sun, Dec 1, 2013 at 2:50 AM, Simone Karin Lehmann sim...@lisanet.de wrote:
Hi,
Am 30.11.2013 um 12:26 schrieb Jehan Pagès jehan.marmott...@gmail.com:
Well... that's why I was proposing testing and collaborating *before*
releasing, and not after. :-/
yes. Sadly, now the
Jehan Pagès (jehan.marmott...@gmail.com) wrote:
Oh right. I just checked again. In the AUTHORS page, there is actually
a Sven Neumann as maintainer alongside Mitch. I actually realize I
made a mistake, because that's another Sven!
Indeed :)
Sven N. hasn't been very active in Gimp development
Hi all,
I'd like to propose to set-up some procedure for releases.
That's not necessarily code and scripts (though in the end, the more
automatized we can be, the better), but at first it could be at least
just writing one wiki page saying what happens in general for a
release, then we write 1
27 нояб. 2013 г. 5:14 пользователь Jehan Pagès jehan.marmott...@gmail.com
написал:
Also I propose that before a build is officially released, they are
first listed on this page for willing people to test it and an email
should also be sent on the dev mailing list. If all goes well, all
tasks
14 matches
Mail list logo
