Preparing for the 1.4 release: triaging open bugs

[Erik Huelsmann <..hidden..>]

Hi all,

In order to get closer to a 1.4 release, I'd like us to discuss open 1.4 bugs and triage them into two groups: blocking and non-blocking.

The issues in the blocking group define the release in the sense that a release cannot ship with those bugs -- that could be due to the fact that major functionality is broken or it's a bad first impression. Non-blocking issues will be fixed in the course of the 1.4 release cycle, but need not block the release in the sense that if it concerns broken functionality, this is not "core" functionality which can be fixed after the release without causing problems for the majority of users.

Do you think this is useful as well? If so, my proposed approach is that I classify outstanding 1.4 tickets into these two categories. Then I send that as a proposal to the -devel list where we can discuss.

Agreed?

--

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs

_______________________________________________
Ledger-smb-devel mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel