[p2pu-dev] [feedback needed] Development work-flow discussion (deadlines vs. priorities)

[zuzel.vp]

Hi everyone,

I want to get a better idea about the individual opinions of
developers and community members with respect to the pros an cons of
using dealines or priorities to organize the development of Lernanta.
I am starting with the development list to get the initial ideas but
we should later get feedback at the community mailing list and
disscuse in a community call.

A bit of history about lernanta's development workflow.

March - April: Biweekly releases adding new features based on the
priority+complexity+benefits of tickets open in lighthouse.
May - June: Biweekly releases adding new features with a defined
objective (make the migration) but no exact deadline.
July - September: Almost Biweekly releases (+ extra releases to match
deadlines and recently postponed releases waiting to finish all the
features pending from a deadline) with the clear objective of
implementing the features requested for one or many deadlines (e.g.
mojo course launch, school of ed launch, webmaking 101 launch).

List of pros and cons (please add the ones you can think when you reply)

Pros of Development by Deadlines:

* Easy for interested partners or users to plan projects and marketing
to start after the dealine.
*

Cons of Development by Deadlines:
* Hard to notice how an individual deadline affects the completion of
other developmen todos.
* Features not associated with a dealine do not get scheduled for development.
*

Pros of Development by Priorities:
* Easier for developers to organize their time working toward periodic
releases and use a tracker.
*

Cons of Development by Priorities:
* Restricts users/partners to make use of the features available at
p2pu at the moment and only provide desired features as feedback.
* Does not solves the subjective aspect of what features are more important.
*

Sugerences:
*

-- 
Thanks,
    Zuzel