Re: [Mingw-cross-env-list] Broken Links

[Tony Theodore]

On 8 June 2011 10:20, Volker Grabsch <address@hidden> wrote:
[...]
>
> I don't think we should have separate branches for every release.
> For example, as soon as 2.19 is released, we don't want anyone to
> use 2.18 anymore. It doesn't make sense to maintain download links
> to outdated software.
>
> Instead, a single "stable" branch is all we need. Note that this
> branch has always been there, but in a quite informal way. That's
> why I just created a formal stable branch in the Mercurial repository.
> That is, we have two branches by now: "default" and "stable". Although
> it might be obvious, here are some guidelines:
>
> 1) Any change in the build scripts goes into "default".
>
> 2) Any package upgrade goes into "default".
>
> 3) Any documentation upgrade that refers to a feature not
>   present in stable goes into "default".
>
> 4) Anything else that doesn't effect the build goes into "stable".
>
> 5) Any non-critical improvement to the main Makefile
>   goes into "stable".
>
> 6) Any improvement in the package download URLs or
>   package version recognition goes into "stable".
>
> 7) When in doubt, use "default" rather than "stable".
>
> 8) After a successful testing phase, the whole "default" branch
>   will be merged (moved) into "stable".

I've "html-ified" the above and added to the docs as a starting point.

http://hg.savannah.gnu.org/hgweb/mingw-cross-env/raw-file/tip/doc/index.html
http://hg.savannah.gnu.org/hgweb/mingw-cross-env/rev/481770a673b4

Cheers,

Tony