On 25 May 2013 14:22, Justin Ross <justin.r...@gmail.com> wrote: > I've mocked up nightly release pages in a way I hope is similar to how > you envisioned it. I like how it turns out. > > > http://people.apache.org/~jross/transom/head/releases/index.html#nightly-releases > > http://people.apache.org/~jross/transom/head/releases/qpid-nightly/index.html > > http://people.apache.org/~jross/transom/head/releases/qpid-proton-nightly/index.html > > This is exactly what I was thinking, so I also like it :)
On the first link the setence about older releases seems like it should move up a section, it was presumably in 'Past Releases' before? > Most of the links on the release pages themselves are broken, and we > need some more advisory text, but it serves to illustrate one way to > do it. > > Things we'll need or want in order to fill in the broken links: > > - A place to push nightly builds. > "http://www.apache.org/dist/qpid/nightly/"; perhaps? > You aren't allowed to use the main dist area (and thus mirrors) for stuff like this, only actual releases. There is now a separate dev distribution area but I believe thats still only intended for e.g betas and release candidates. > > - To adapt doc gen scripts to produce docs from trunk. I can > definitely do that. > > - A way for a cron job to commit to our svnpubsub path. I'm not > sure about this one. > I was envisaging that we would set up jobs on the Buildbot instances and simply link to the job output, or if possible have those jobs able to commit somewhere (with their own credentials) that uses svnpubsub to deploy the output to a specific tree of the website that we wouldnt otherwise touch ourselves. > > Justin > > On Fri, May 24, 2013 at 11:31 AM, Justin Ross <justin.r...@gmail.com> > wrote: > > On Fri, May 24, 2013 at 11:05 AM, Robbie Gemmell > > <robbie.gemm...@gmail.com> wrote: > >> Part of me think that if we had a page that looked a bit bare then > maybe we > >> would be better about putting more stuff on it when people see it and > >> wonder where the missing bits are. Hiding it away where people won't > see it > >> gives less incentive and also means that the stuff that already is there > >> won't get used to the extent it could. > > > > Okay, I'll split it out. > > > >>> It would be my preference to treat trunk documentation as just another > >>> kind of nightly build, with a prominent section next to other nightly > >>> artifacts and a link from the documentation page. > >>> > >> > >> I was thinking along the lines of 'nightly release' page(s)...such that > by > >> the time it comes to the point to release the component(s) it should to > >> some extent effectively be a case of making a copy of what has already > been > >> published previously for the component(s). > > > > Okay, that seems like a fine approach. For what it's worth, it's a > > little annoying from the scripting standpoint because you need to > > conditionally link to trunk or a branch, and you need to > > conditionalize other stuff as well, such as download links. Right now > > the scripts count on there being tags in svn and artifacts up on dist. > > > > But that's not the big piece of work. To really make a "nightly > > release" look just like a numbered release, we have a fair bit of work > > to do yet to automate builds. > > > >> I might be the exception, but when I bother myself to write new docs I > tend > >> to want them on the site and publish them immediately. > > > > There's no blocking problem with doing this. The trunk docs can be > > generated and pushed in a different fashion. There's no terribly > > great need to add the site nav around the trunk docs, though I agree > > it would be nice once the above mentioned scripting is sorted out. > > > > Justin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > >
