Re: Pre-release feature freeze for trunk

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Fiedler wrote:
> Hi all,
> 
> here's my first proposal for an official feature freeze of trunk as a 
> preparation for the next release:
> 
> <quote>
> When preparing source releases, the core developers set a Feature Freeze on 
> the core parts of trunk, which means that 

Core parts meaning anything not flagged CORE as well as scripts/ misc/
architecture/ and so on?

> * only bug and security fixes are applied until trunk is found stable and 
> well-tested enough for a new release. 
> * Package updates can be applied if they contain bug fixes only, or security 
> fixes - adding features should be avoided, to prevent introducing new bugs 
> (in other places). 

Sounds good.

> Source releases are named by their respective revision numbers. Official 
> binary releases are based on source releases and created by core developers.

What's the naming scheme here?


What tests should be conducted? What must work for a release? What doesn't need
to work?

- - target/* ?
- - x86? alpha? sparc? x86_64?

What about maintaining releases? Security fixes and stuff.
What about gem repositories for Crystal releases?


Greetings,
	Benjamin

- --
Benjamin 'blindCoder' Schieder
Registered Linux User #289529: http://counter.li.org
finger blindcoder-1k+CIuW/[email protected] | gpg --import
- --
/lusr/bin/brain: received signal: SIGIDIOT
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFEkPFir0OTeImXvg8RAstCAKCTAR9W1avasZxESsEyJyeA7gsifgCfdlLG
6EdxHkqLl14UIKfkBJIQFqY=
=f661
-----END PGP SIGNATURE-----