The link to the nightly builds is part of the source code page.
Again, we do *not* want people downloading the nightly builds unless they are interested in contributing to the project. That type of person is going to be looking for the source code too, so that's where the link is kept. If the link is more prominent, then people will confuse the development builds with alpha or beta releases, which they are not. We are always looking for volunteers to help with development, but we are not looking for an "audience" that might not understand the difference between a nightly development build and a beta release. -Ted. On 3/14/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
Ted, The layout is nice, but where is the link to download the test build? That's my point. I can't even find it just looking at the Development Build sub-section. If it had its own menu item underneath Development, that's the "strategic" position I am looking for. Paul Ted Husted wrote: > In the latest draft documents for Struts 2 (aka 2.0.7), we added a > development submenu to the main page. > > * http://struts.apache.org/2.x/index.html > > A key concept is that people who work with us on the nightly build are > no longer "an audience". They must be active and willing participants. > We don't want to confuse people who are just looking for a stable > release with the vagrancies of a development build. We need to make a > good faith effort to ensure that the people who do make use of the > development build realize that it is all subject to change, and some > nights it might not even build. We do want the links to be > "strategic," but strategic in the sense that a hapless passerby won't > stumble on to the development builds by mistake. > > We've been trying to do the nightly builds in the zone, but it seems > like success has been spotty. Back in the day, we used to build it > ourselves on our own machines and then upload the build as part of a > local nightly cron job. > > On 3/14/07, Paul Benedict <[EMAIL PROTECTED]> wrote: >> Marin, >> >> That's fine. We can always point to those builds from a developer page, >> but make the developer page also accessible from a non-developer page. >> That's how it is today, but we can just be more strategic in how to >> point to that page. >> >> But for the other question: how can we setup automated builds? >> >> Martin Cooper wrote: >> > On 3/14/07, Paul Benedict <[EMAIL PROTECTED]> wrote: >> >> >> >> Can we get the same system setup to create automated snapshot >> builds for >> >> Struts 1? I am willing to help out. >> >> >> >> Also do we have a policy about advertising snapshots on the Struts >> web >> >> site? I think it's a liability for only us to do the testing; we >> simply >> >> need the larger audience to help test out early builds. >> > >> > >> > Any "advertising" of snapshots or other non-release artifacts must >> be done >> > in such a way as to be very clearly directed towards developers, >> and not >> > end >> > users, of Struts. That is, any page that mentions non-release >> artifacts >> > must >> > be reachable only through links in the "Development" section of the >> menu on >> > the Struts web site. >> > >> > This is an ASF-wide thing, and not just a Struts thing. It's also >> why the >> > web site was restructured, not so long ago, to separate out the >> development >> > pages from the rest of the site. >> > >> > -- >> > Martin Cooper >> > >> > >> > Paul > > - HTH, Ted > <http://www.husted.com/ted/blog/>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
