Seems reasonable. I can set up that wiki page and update the website at the end of the week, unless someone else gets to it first.
Maybe I should know this already - is there a nightly build that's already created we could also point people to? Jon On Mon, Nov 4, 2019 at 2:59 PM Michael Shuler <mich...@pbandjelly.org> wrote: > wiki != project website > > I think this sounds completely reasonable for a wiki page, and anyone > can edit easily. Good suggestion. > > Michael > > On 11/4/19 3:18 PM, Joshua McKenzie wrote: > > Is there an opportunity to consider a separate "upcoming release testing" > > type page with downloads to alpha releases? Sounds like, as per letter of > > the law, we wouldn't that on the official project page but getting > > something going where we can have project-wide "test out this alpha" or > > where individual devs could post builds of a feature they're working on > at > > similar milestones (alpha, beta, etc) might be helpful in terms of > getting > > a healthier dev <-> user feedback cycle going on some things. Maybe a > wiki > > page with this type of information? > > > > Ultimately I'd like to see a way for us to reduce friction to users > getting > > involved in the testing of C* if possible without crossing that line into > > risking people running alpha code on accident in a production > environment. > > > > On Mon, Nov 4, 2019 at 3:10 PM Michael Shuler <mich...@pbandjelly.org> > > wrote: > > > >> I will also add that I did send the user@ list 4.0-alpha release notes, > >> along with dev@, and also added to the @cassandra tweet last week. I > >> thought those were acceptable to get a little wider audience, but didn't > >> want to link from downloads page, since this is explicit. > >> > >> Michael > >> > >> On 11/4/19 2:06 PM, Michael Shuler wrote: > >>> -1 (I looked into this when we released 4.0-alpha1) > >>> > >>> "During the process of developing software and preparing a release, > >>> various packages are made available to the developer community for > >>> testing purposes. Do not include any links on the project website that > >>> might encourage non-developers to download and use nightly builds, > >>> snapshots, release candidates, or any other similar package. The only > >>> people who are supposed to know about such packages are the people > >>> following the dev list (or searching its archives) and thus aware of > the > >>> conditions placed on the package. If you find that the general public > >>> are downloading such test packages, then remove them." > >>> > >>> http://www.apache.org/legal/release-policy.html#what > >>> > >>> Michael > >>> > >>> On 11/4/19 1:11 PM, Dinesh Joshi wrote: > >>>> I think this is a good idea. I am +1 on making this more discoverable > >>>> on our website. Please add instructions to report bugs and give us > >>>> feedback around it. > >>>> > >>>> Dinesh > >>>> > >>>>> On Nov 4, 2019, at 10:53 AM, Jon Haddad <j...@jonhaddad.com> wrote: > >>>>> > >>>>> I noticed we don't currently list the alpha in the downloads section. > >>>>> Anyone object if I add the relevant information after the "Older > >>>>> supported > >>>>> releases" section in the downloads page? I'd make it clear that this > >> is > >>>>> alpha and non-production release, and we're soliciting feedback. > >>>>> > >>>>> http://cassandra.apache.org/download/ > >>>>> > >>>>> Jon > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > >>>> For additional commands, e-mail: dev-h...@cassandra.apache.org > >>>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > >> For additional commands, e-mail: dev-h...@cassandra.apache.org > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
