incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <>
Subject Re: Websites, WebApps, and Release Policy
Date Mon, 25 Aug 2014 17:16:34 GMT
On Mon, Aug 25, 2014 at 9:51 AM, Alex Harui <> 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.
> But what about web apps?  Apache Flex is designed for creating web apps
> made from source code that is compiled into a SWF.
> Today, Apache Flex announced the release of Tour De Flex.  The source code
> is in one of our git repos, the source package is up on,
> and a compiled version of the source is on flex.a.o here:
> Users are playing with the app at that link and reporting bugs.  I'm
> wondering: can we modify the source with a bug fix and post the modified
> source and compiled results on flex.a.o without a release vote?  Tour De
> Flex is potentially different from most web apps because its job is to
> show you the source code behind the scenes.  Most web apps can be
> published without their source.
> Also, can we make other modifications?  One user found that a link was
> broken and we fixed it by copying an asset to where the source said the
> link was.  Therefore what is on flex.a.o right now is no longer the
> compiled results of the source.

This strikes me very similar to providing access to daily SNAPSHOT binary
artifacts. I would argue that labeling it appropriately is all you
need. In fact,
clearly labeling it would actually benefit your customers. After all, if you're
pushing updates it means that something that used to work yesterday
could stop working today. Personally, I find it very frustrating when this
happens on something that is clearly labeled as an immutable release.

Long story short, I guess if you labeled it something like:
   "Apache Flex Tour De Flex Component Explorer Daily Update XXX"
instead of ""Apache Flex  Tour De Flex Component Explorer 1.0"
I'd see no issues at all.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message