Perhaps it's just me being lazy but I reckon that having defined 'beta' and RC packages available for download (with some form of marketing to inform people) would likely increase the sample size for testing, including different use cases. I'm pretty sure that there are a number of people that fit the sysadmin role rather than the devops or developer role who just won't go to the effort of trying to work out what to checkout, build and package themselves even if they did know how to. I realise that the audience for CS may be different to many other OS software projects out there but most well-used projects (including many commercial ones) that I work with go through this process. The only other issue would be that of feedback - I know it's an Apache thing but an online forum site would really make providing feedback much easier than the mailing list.
Adrian -----Original Message----- From: Nux! [mailto:n...@li.nux.ro] Sent: 10 October 2014 09:24 To: dev@cloudstack.apache.org Subject: Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu, why? Yes that's not a bad idea. At some point we had a chat with Hugo and David about having jenkins generate RPMs with incremented version and setup a repo for them which lead me to believe that at least Jenkins is capable of that. So, whoever is in charge of Jenkins, how can we achieve this? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Erik Weber" <terbol...@gmail.com> > To: "dev" <dev@cloudstack.apache.org> > Sent: Friday, 10 October, 2014 09:10:35 > Subject: Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu, why? > Or make a different folder for unreleased versions? > That way you could upload daily builds as well if you ever wanted to > > How about > - a stable/release folder, where released versions go > - a rc folder, for official release versions > - a nightly/dev folder, for either a nightly version or the latest > master build > > Couple it with jenkins and it would be easy for testers to verify that > a bug is fixed by upgrading their RC or dev version > > -- > Erik > > On Fri, Oct 10, 2014 at 9:46 AM, Daan Hoogland > <daan.hoogl...@gmail.com> > wrote: > >> I was thinking about that. I shouldn't have done this upload but had >> a reason to. I want to make these available for testers. maybe i can >> upload them without adding them to the rpm index...? >> >> On Thu, Oct 9, 2014 at 7:47 PM, Nux! <n...@li.nux.ro> wrote: >> >> > Perhaps we need a testing repo for non-final packages? >> > >> > -- >> > Sent from the Delta quadrant using Borg technology! >> > >> > Nux! >> > www.nux.ro >> > >> > ----- Original Message ----- >> > > From: "Daan Hoogland" <daan.hoogl...@gmail.com> >> > > To: "dev" <dev@cloudstack.apache.org> >> > > Sent: Thursday, 9 October, 2014 17:42:50 >> > > Subject: Re: Unreleased 4.4.1 packages on cloudstack.apt-get.eu, why? >> > >> > > i did >> > > >> > > On Thu, Oct 9, 2014 at 3:07 PM, Ian Duffy <i...@ianduffy.ie> wrote: >> > > >> > >> Wildo, >> > >> >> > >> Do we have no kind of audit on uploads? >> > >> >> > >> On 9 October 2014 12:25, Wido den Hollander <w...@widodh.nl> wrote: >> > >> >> > >> > >> > >> > >> > >> > On 10/09/2014 01:21 PM, Nux! wrote: >> > >> > > Hello, >> > >> > > >> > >> > > I've noticed there are 4.4.1 packages on >> > >> > http://cloudstack.apt-get.eu/rhel/4.4/. >> > >> > > Since 4.4.0 is latest release, how come? This is bad, people >> > >> > > will >> > >> > install broken stuff. >> > >> > > Can anyone fix this? >> > >> > > >> > >> > >> > >> > I removed the packages, but I'm not sure who uploaded them. >> > >> > >> > >> > They were uploaded on September 30th at 11:12 CET. >> > >> > >> > >> > Wido >> > >> > >> > >> > > Lucian >> > >> > > >> > >> > > -- >> > >> > > Sent from the Delta quadrant using Borg technology! >> > >> > > >> > >> > > Nux! >> > >> > > www.nux.ro >> > >> > > >> > >> > >> > >> >> > > >> > > >> > > >> > > -- >> > > Daan >> > >> >> >> >> -- >> Daan
