I can work on the permanent solution after I wrap up the Flex team page app (i.e. soon)
Chris, I am thinking of setting up a Jenkins web hook that builds and posts a new TourDeFlexJS web app every time a commit is made to a new TourDeFlexJS git repo. The website can be my personal github site for now. We can figure out if we want to do a new website or new subdomain on apache.org or simply a folder on flex.apache.org later. What do you think? Thanks, Om On Dec 30, 2016 2:08 PM, "Alex Harui" <aha...@adobe.com> wrote: > > > On 12/30/16, 10:24 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote: > > >PKumar, > > > >I think that may be our last step once we finished all work on components > >[1] itself. > > > >[1] https://cwiki.apache.org/confluence/display/FLEX/Table+Of+Components > > Any volunteer is welcome to start now. Should we create a new git repo > for a TourDeFlexJS? Seems like it should be a different release so it can > be updated independently of the FlexJS SDK? Or should it all be in one > bundle? > > Thoughts? > -Alex > >
