Sorry for not responding sooner. Yes, Bryce put forth the most compelling reason/tradition. One more would be that it gives us incentive to get the pre#-builds started sooner rather than later so we can keep up some momentum. The contest doesn't serve to keep momentum as it's really separate from development and has a fixed timeframe that is easier to control.

As Bryce mentioned, we still have a few of things that ought to be updated or at least looked at first. I will also say that if some of the newer LPEs making their way into the Experimental branch are deemed to be ones we will end up shipping with, I would recommend we consider getting them into trunk to ship the builds with those to have for the contest.

One side task for the contest is that we should come up with a theme or concept. People don't need to adhere to the theme with their submissions, but it's always interesting to see what people come up with when they do. Given the amount of time between major releases I think something along the lines of "shedding skin" (like a snake or cicada), I don't know, something "transformative". Any suggestions anyone?

Cheers,
Josh


On Fri, May 9, 2014 at 11:23 PM, Bryce Harrington <bryce@...961...> wrote:
On Fri, May 09, 2014 at 10:19:38PM -0400, Martin Owens wrote:
> On Fri, 2014-05-09 at 16:28 -0700, Josh Andler wrote:
> > I'm still planning on running this as usual, however, this can't be
> > started until we have at least pre0 tarballs and the relevant test
> > builds available.
>
> Sorry Josh, looks like my email was cut in two. I went on to weave an
> amazing tale of daring do the likes of which we shall not see for a long
> time.
>
> Why do we need prebuilds? I know our todo lists don't have a dependency
> chain shown, so is this because we need artists to use the new version
> to make the about screen? Sort of, "look it works!"

Right, we like to encourage artists to showcase some of the new
features, thus they need access to official binary packages.

Speaking of a pre0... looking through the codebase I see we have 0.48
spread to some unusual files:

src/extension/dbus/Makefile_insert:libinkdbusincludedir = $(includedir)/libinkdbus-0.48/libinkdbus

Why is libinkdbus-0.48 hardcoded as 0.48 here?
This looks wrong.

Bryce