IMO, it can wait until you're ready. We definitely want it to look good, but I would expect folks will find lots of stuff when they start poking around, so I wouldn't spend too much time on it. IMO, if a problem is found, it would be fine to modify the repo, make a local build, and drop new files on the website. CTR, no need for voting. Then at some point, we can cut another release.
And/Or, if you want to be really bold, we could set up Jenkins to deploy a nightly build to the site. But that's for later. I'm fine with whatever you put up there. -Alex On 8/22/14 10:05 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: >I have the RC3 bits from when I built it, but my main goal here is to make >sure that whatever goes on the website looks really good. > >I will get the tag and build from there and see how things go. > >Also, do we want to announce on the weekend? Let's wait until Monday >morning. That will also give me more time to work on the site. > >Thanks, >Om >On Aug 22, 2014 9:45 PM, "Alex Harui" <aha...@adobe.com> wrote: > >> IIRC, I think you have to manually build that one example. That was a >> build script change, but still, a change to the released sources. And >>we >> might want to figure out why the OSMF video is black and that might >> require a code change. >> >> On 8/22/14 9:40 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >> >> >Hi, >> > >> >> IMO, it doesn't matter since we're going to muck with the results to >>fix >> >> two or three known issues. >> >Much about == change where a few files live, I don't believe there >>needs >> >to be any changes to code or anything else. >> > >> >Thanks, >> >Justin >> > >> > >> >>
