Websites, WebApps, and Release Policy

2014-08-25 Thread Alex Harui
Hi Incubator Folks, My understanding is that changes to a website like flex.a.o don't require a release vote, even though one could consider and html file pushed to the site as publishing source beyond the group that owns it. But what about web apps? Apache Flex is designed for creating web

Re: Websites, WebApps, and Release Policy

2014-08-25 Thread Roman Shaposhnik
On Mon, Aug 25, 2014 at 9:51 AM, Alex Harui aha...@adobe.com wrote: Hi Incubator Folks, My understanding is that changes to a website like flex.a.o don't require a release vote, even though one could consider and html file pushed to the site as publishing source beyond the group that owns it.

Re: Websites, WebApps, and Release Policy

2014-08-25 Thread Justin Mclean
Hi, The whole point point of the release process is to: 1. Have legal overview by the PMC 2. Engage and involve the community Why would we want to avoid either? As [1] says Under no circumstances are unapproved builds a substitute for releases. If this policy seems inconvenient, then release

Re: Websites, WebApps, and Release Policy

2014-08-25 Thread Justin Mclean
Hi, This strikes me very similar to providing access to daily SNAPSHOT binary artifacts. I would argue that labeling it appropriately is all you need. Except that is this case the intended audience of the application is users. After all, if you're pushing updates it means that something that

Re: Websites, WebApps, and Release Policy

2014-08-25 Thread Alex Harui
Hi Justin, Are you addressing me personally or Roman or the incubator in general? -Alex On 8/25/14 3:21 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, The whole point point of the release process is to: 1. Have legal overview by the PMC 2. Engage and involve the community Why would we

Re: Websites, WebApps, and Release Policy

2014-08-25 Thread Justin Mclean
Hi, Are you addressing me personally or Roman or the incubator in general? Was sent to general@ so the content of them is for the incubator in general, the emails were not personally addressed. But if it helps my second email was to clarify / add to Roman's comments. Thanks, Justin

Re: Websites, WebApps, and Release Policy

2014-08-25 Thread Roman Shaposhnik
On Mon, Aug 25, 2014 at 3:24 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, This strikes me very similar to providing access to daily SNAPSHOT binary artifacts. I would argue that labeling it appropriately is all you need. Except that is this case the intended audience of the

Re: Websites, WebApps, and Release Policy

2014-08-25 Thread Branko Čibej
On 26.08.2014 00:24, Justin Mclean wrote: Hi, This strikes me very similar to providing access to daily SNAPSHOT binary artifacts. I would argue that labeling it appropriately is all you need. Except that is this case the intended audience of the application is users. Bloodhound has