: Re: AW: AW: AW: AW: AW: [Website] Progress on the Website-Generation
topic
On 10/19/16, 2:18 AM, "Christofer Dutz" wrote:
>Ok picking up this thread again ...
>
>
>Well I think that allowing non-comitters to contribute to the page is a
>pretty slim benefit. I couldn
On 10/19/16, 2:18 AM, "Christofer Dutz" wrote:
>Ok picking up this thread again ...
>
>
>Well I think that allowing non-comitters to contribute to the page is a
>pretty slim benefit. I couldn't say that we have used that even for a
>single time in the past. And I think it would be good not to a
te-maven" and different solutions
could co-exist. All that I want, is the ability to produce the sites of
sub-modules such as FlexJS (and it's part) automatically.
Chris
Von: Alex Harui
Gesendet: Freitag, 14. Oktober 2016 17:20:05
An: dev@flex.apache.org
Bet
On 10/14/16, 12:42 AM, "Christofer Dutz" wrote:
>
>So if we are comparing the new three-step user workflow:
>
>1. Do changes
>
>2. Test them locally with a "mvn clean site"
>
>3. Commit changes
>
>
>to the current user workflow, which is:
>
>1. Do changes
>
>2. Commit changes
>
>3. Wait for bui
Von: Christofer Dutz
Gesendet: Donnerstag, 13. Oktober 2016 07:49:01
An: dev@flex.apache.org
Betreff: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic
Hi Alex,
Well you do need buildbot ... nothing else is allowed to commit. But nothing
else than buildbot.
I was ta
Hi Alex,
Well you do need buildbot ... nothing else is allowed to commit. But nothing
else than buildbot.
I was talking about the user workflow. These three steps are the steps you
need, if you want to change something and I guess you can't get any simpler
than that. Especially with the abil