** Changed in: zeitgeist
Status: Confirmed = In Progress
** Changed in: zeitgeist
Assignee: Zeitgeist Framework Team (zeitgeist) = Markus Korn (thekorn)
** Changed in: zeitgeist
Milestone: 0.5.1 = 0.6
** Changed in: zeitgeist
Status: In Progress = Fix Committed
--
Add
revno: 1578 [merge]
fixes bug(s): https://launchpad.net/bugs/628678
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Fri 2010-09-10 10:16:13 +0200
message:
Added information about the bug triaging process within
** Branch linked: lp:zeitgeist
--
Add bugtriaging guidlines to HACKING
https://bugs.launchpad.net/bugs/628678
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Fix Committed
Bug
** Changed in: zeitgeist
Milestone: None = 0.5.1
--
Add bugtriaging guidlines to HACKING
https://bugs.launchpad.net/bugs/628678
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is a bug assignee.
Status in Zeitgeist Framework: Confirmed
Bug
Seif, I disagree with you. It is fine if this changes to our bugtriaging
policy lands at the very beginning of our 0.6 dev cycle.
** Changed in: zeitgeist
Milestone: 0.5.1 = 0.6
** Changed in: zeitgeist
Milestone: 0.6 = 0.5.1
--
Add bugtriaging guidlines to HACKING
Uhm I would like to have this bug fixed with the 0.5.1 release marking a new
start on 0.6 so please lets discuss this before i final verdict is taken.
On Tue, Sep 7, 2010 at 6:15 PM, Markus Korn thek...@gmx.de wrote:
Seif, I disagree with you. It is fine if this changes to our bugtriaging
Seif, we are not shipping HACKING in our release tarball, so it does not really
matter *when* changes to the HACKING document enter lp:zeitgeist.
So my idea is, let's get 0.5.1 out first, then discuss this topic further, and
once our bug triaging process is described in HACKING it takes effect.
7 matches
Mail list logo
