[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stable releases
From: |
address@hidden |
Subject: |
Re: Stable releases |
Date: |
Tue, 17 Jan 2012 09:52:28 +0100 |
On Jan 17, 2012, at 9:45 AM, Werner LEMBERG wrote:
>
>>> So, with this idea in mind, I'd like to kick off a discussion about
>>> the next stable release. Assuming that we can fix all the critical
>>> issues (I think that's possible, but may be a month out or so),
>>> what else should we plan to have part of the next stable?
>
> Normally, a route to a stable release means a code freeze, applying
> only fixes to problems within the code. This also means that no new
> bug fixes get applied. Are we going to do the same?
>
I don't understand the difference between the two - wouldn't a bug be a problem
within the code?
Cheers,
MS
Re: Stable releases, Janek Warchoł, 2012/01/16
- Stable release proposal, Carl Sorensen, 2012/01/16
- Re: Stable release proposal, Keith OHara, 2012/01/17
- Re: Stable release proposal, Francisco Vila, 2012/01/17
- Re: Stable release proposal, Trevor Daniels, 2012/01/17
- Re: Stable release proposal, David Kastrup, 2012/01/17
- Re: Stable release proposal, Werner LEMBERG, 2012/01/17
- Re: Stable release proposal, Janek Warchoł, 2012/01/17