netbeans-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Lenz" <>
Subject Aw: Re:
Date Mon, 21 Nov 2016 09:59:47 GMT

great to see the discussion about the page. The source is on bitbucket:
in a private repo.
So I can add people as contributors or we can change the repo hoster if you want, I don't

I will set a feature branch with the stuff, that I changed for
Will do it today in the afternoon.

It is a static page without any build processes, ok we have sass and a minification, but for
this I use netbeans, I don't have any gulp or npm script for this yet.



Gesendet: Montag, 21. November 2016 um 10:00 Uhr
Von: "Daniel Gruno" <>
Betreff: Re:
On 11/21/2016 09:55 AM, Tushar Joshi wrote:
> On Mon, Nov 21, 2016 at 2:14 PM, Daniel Gruno <> wrote:
>> You will likely also need to keep the site in two places. In subversion,
>> you would keep the source in a source/ dir and the published content in
>> a publish/ dir, while in git you would keep the source in the master
>> branch and the published site in the asf-site branch.

Just to avoid confusing people here:
asf-site is the branch that gets published and ends up on netbeans.a.o.
any other branch may contain the source code for the site.

> So just like gh-pages Apache uses asf-site branch for source of site and
> master branch for the distributable public build.
> Is there a feature where we can use service like Travis.CI usually used by
> Github users to build the site as soon as something is committed to
> asf-site branch?

Possibly, although you would think any decent site you can generate
locally to test your changes.

> We may also think of maintaining a develop branch for maintaining a
> intermediate version of the site for reviews before we merge content to
> asf-site for reviews and pull requests, as asf-site will be bound to
> trigger a build through such a build service.
> with regards
> Tushar

View raw message