[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat, 25 Jul 2015 10:05:30 -0400, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> On Fri, Jul 24, 2015 at 4:41 AM, Peter Wang <novalazy@xxxxxxxxxx> wrote:
>
> >
> > Cool. I assume releases will go on github as well.
> >
> >
> I haven't tried it, but it seems
> https://github.com/liballeg/allegro5/releases allows uploading arbitrary
> binary files together with a release - so it should work just fine. I
> suppose a release is always tied to a git tag, which is fine. What's your
> github username btw.? Also Trent, what's yours? Or anyone else who needs
> developer access to the github project.
wangp
> I think we'll be good on github+gna.
We'll see what they say.
> As for the website, I had some time and just for fun converted most of the
> current
>
> http://alleg.sourceforge.net
>
> to Jekyll-github
>
> http://liballeg.github.io
>
> . Still has some broken links and some missing stuff but I think it would
> be a good way. Jekyll is very similar to our pandoc system. The markdown is
> basically the same, unfortunately minus the nice pandoc tables. And Jekyll
> has quite a few minor annoyances... the one advantage is that instead of
> building locally and rsyncing, github will automatically rebuild it on
> their server whenever a change is committed. Not sure we could install
> pandoc on travis-ci and do the same without... anyway, the Jekyll website
> source is here:
For me, building locally is a positive as I would not commit without
previewing, and the copying is trivial to script and does not lock us to
a provider. Whatever works for whoever is doing the releases.
Peter