[FFmpeg-cvslog] [ffmpeg.org]: r457 - trunk/src/download

[Reinhard Tartler]

On Sun, Jun 13, 2010 at 18:50:01 (CEST), michael wrote:

> Author: michael
> Date: Sun Jun 13 18:50:00 2010
> New Revision: 457
>
> Log:
> The truth about 0.5.*
>
> Modified:
>    trunk/src/download
>
> Modified: trunk/src/download
> ==============================================================================
> --- trunk/src/download	Fri Jun 11 15:42:09 2010	(r456)
> +++ trunk/src/download	Sun Jun 13 18:50:00 2010	(r457)
> @@ -73,6 +73,9 @@
>  shed"</h2>
>  
>  <p>
> +The 0.5 branch is ONLY for distributions and not end users, it is over a

what are end users supposed to be? I don't expect any end user like my
parents to even know what a compiler is.

> +year outdated and unsupported by us. SVN/GIT head is much better in every

what do you mean with 'support'? Diego and I are doing point releases,
so there *is* at least *some* amount of support available. 

> +respect including stability, bug count and security.

the release branches are definitly more 'stable' than trunk, as there
are a lot less chnages compared to trunk. The probablility that a change
in a release branch will break existing applications, require
recompilation, or similar (this would be "my" understanding of
"stability" is close to zero.  Maybe you meant to write something else
than 'stability'?

As for bug count, the set of bugs is not likely to increase over the
time in release branches. This is more likely in trunk, as only there
new features are integrated. If you wanted to say that since all
bugfixes happen in trunk and therefore, using trunk greatly increases
the chance to get a particular bug fixed, then I'd agree but think this
comment could be improved.

As for security, I wonder why do you say that trunk/ snapshots are more
'secure' than release branches. For me, a security issue is always a
serious bug that needs to be fixed. Known bugs in release branches will
be fixed by the next point release. There is obviously a considerable
latency for such fixes to "propagate" to release branches, but I
wouldn't necessarily conclude that using release branches were "more
risky" to run than trunk.

Having said this, would you mind reverting the change until we have
found a less confusing wording?

>  0.5.2 appeared on 2010-05-25. It is the latest point release from the 0.5
>  release branch cut on 2009-03-02.
>  </p>

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4