[p2pu-dev] Suggestion for developemnt process

zuzel.vp zuzel.vp at gmail.com
Tue May 10 16:34:05 UTC 2011

Also after the initial beta hight priority tasks are in we should try
to enrich our tests suit so it becomes easier to detect bugs. This
release had a change that was highly risky (allowing multiple
organizers) but since the tests we have are only a few we got from
batucada it was not possible to fully use them to check that things
were fine.


On Tue, May 10, 2011 at 12:28 PM, zuzel.vp <zuzel.vp at gmail.com> wrote:
> Forwarding to the development list for feedback.
> On Tue, May 10, 2011 at 11:38 AM, Vladimir Támara Patiño
> <vtamara at pasosdejesus.org> wrote:
>> It would be
>> good to think a development process that ensures testing more before
>> releasing and updating living site to a new version.
> Yes we should work on defining a development schedule.
>> An idea, since there are new versions every two weeks:
>> Week 1. The big changes are introduced (new features), pull
>> requests of new features are reviewed and possibly integrated.
>> Week 2. Functionality freezes and the developers concentrate in testing
>> and fixing bugs, only pull requests that fix bugs are accepted.
>> Localization is expected this week.
> Week 1 has other time consuming tasks -- organizing/reading pending
> emails/creating new tickets email discussion threads/writing past
> release change list, merging contributions (pull requests and
> batucada). This makes hard to concentrate new features only that week.
> Maybe freezing half way through the second week could help.
> Thoughts?
> --
> Thanks,
>    Zuzel

More information about the p2pu-dev mailing list