|Version 1 (modified by gbastien, 7 years ago)|
gbastien: This is a tentative approach to wifidog development. Let's see how it works for some time and if anything can be improved. Comments are welcome.
To keep up to date with development, we will do monthly sprints, the output of which will be a dated stable release of the auth server AND gateway.
Here's the calendar for a monthly sprint:
- Last friday of the month (R-day): Date of the official dated release
- Week before R-day: testing blitz. No patches will be accepted unless they are related to a ticket solved in this release or they are critical to the stability of the software.
- Friday before R-day (C-day): All patches must be committed or posted
- Last R-day to C-day: Development time. Developers publicly commit themselves to fixing bugs or developing features.
Participate in the sprint
Sprints allow people to publicly commit themselves to solving a ticket before a certain deadline. In order to participate in the sprint,
- Pick a ticket in the trac (or create a new one) and assign it to yourself.
- Add the ticket and yourself to the sprint page:
- Navigate to the appropriate spring page (for a realistic deadline, remember C-day is the important date)
- Choose the sprint you want to participate in
- Click on the edit button for this page
- Under the section Tasks, add the ticket number and your name. Eg.
That is your public committment to resolve it!
- Get to work!
- When you are done, either post the patch on the ticket or commit the code and add a mention that you're done on the Sprint page
Should anyone fail to produce a patch before C-day, it's ok, it's not the end of the world. But some tickets do need solving, so any difficulty should be discussed with other developers. If you just don't have time to resolve it, then remove your assignment from the ticket so someone else can take it up.
Note: it is always possible to solve a ticket without commiting to a certain sprint. In that case, do it the usual way, as stated in the contribute page.