MJ Ray a écrit :
> "Joe Atzberger" <[EMAIL PROTECTED]> wrote:
>> A necessary component of finishing 3.0 is formally deciding what features
>> will NOT be a part of it, as documented by these RFC's.
>> These do not represent an assignment of priority.
>
> We've 3.0 betas out there. Can we simply d
"Joe Atzberger" <[EMAIL PROTECTED]> wrote:
> A necessary component of finishing 3.0 is formally deciding what features
> will NOT be a part of it, as documented by these RFC's.
> These do not represent an assignment of priority.
We've 3.0 betas out there. Can we simply declare feature freeze now?
On Tue, Jun 10, 2008 at 9:00 AM, MJ Ray <[EMAIL PROTECTED]> wrote:
> "Galen Charlton" <[EMAIL PROTECTED]> wrote:
> > While we work on bugfixing for 3.0, it is also time to give a concrete
> > thought or two for the future. Today I will start sending LibLime's
> > RFCs for new features for 3.2. [.
Hi,
On Tue, Jun 10, 2008 at 8:00 AM, MJ Ray <[EMAIL PROTECTED]> wrote:
> "Galen Charlton" <[EMAIL PROTECTED]> wrote:
>> While we work on bugfixing for 3.0, it is also time to give a concrete
>> thought or two for the future. Today I will start sending LibLime's
>> RFCs for new features for 3.2. [
"Galen Charlton" <[EMAIL PROTECTED]> wrote:
> While we work on bugfixing for 3.0, it is also time to give a concrete
> thought or two for the future. Today I will start sending LibLime's
> RFCs for new features for 3.2. [...]
Sorry to seem unappreciative of good drafting and some initiative, but
Hi,
While we work on bugfixing for 3.0, it is also time to give a concrete
thought or two for the future. Today I will start sending LibLime's
RFCs for new features for 3.2.
I have created a page for the RFCs on the wiki:
http://wiki.koha.org/doku.php?id=en:development:rfcs3.2
As many of the R
