FUDforum: FUDforum 3.0+ » Improving development process

Home » FUDforum Development » FUDforum 3.0+ » Improving development process

Show: Today's Messages :: Unread Messages :: Polls :: Message Navigator
| Subscribe to topic | Bookmark topic

Improving development process [message #165930]

Fri, 26 August 2011 18:21

JanRei

Messages: 361
Registered: October 2005
Location: Germany

Karma: 0

Senior Member
Contributing Core Developer
Translator

remove from buddy list
ignore all messages by this user

I have some ideas regarding the development process and would like to hear what you think about it.

1) Sometimes it's difficult for me to keep track of the posted suggestions and bugs. I am not sure whether some things go lost if nobody has time and knowledge to implement it right now. Over time the corresponding topic moves down the topic listing. Also, sometimes I am not sure whether somebody else is already working on it. Maybe it would be helpful to use some bug tracking system or enhancing the forum so that it can be used like that.

2) When we are in the RC phase (or even at the final RC before release) it makes sense to include only small or important fixes to prevent the introduction of new issues. Maybe we could create a branch for the stable version then so we can continue to use trunk for unimportant bug fixes and new features.

Report message to a moderator

Rate author: +1 -1

Message by The Witcher is ignored [reveal message] [reveal all messages by The Witcher] [stop ignoring this user]

Re: Improving development process [message #165935 is a reply to message #165932]

Sat, 27 August 2011 04:29

naudefj

Messages: 3771
Registered: December 2004

Karma: 28

Senior Member
Administrator
Core Developer

add to buddy list
ignore all messages by this user

1. Good idea. There is an issue issue tracker on sourceforge.net we can use. Maybe you should evaluate it and let us know if it fits the bill.

2. You can commit changes against tags as well. For example, if big changes are committed to 'trunk', we can continue committing smaller fixes against 'fud3_0_3RC2' and eventually create a 'fud3_0_3' from it. It all depends on what you want to accomplish. If you want a separate area to implement something that may be disruptive, a branch makes sense.

In addition, we also need establish a wiki page with coding standards for the project.

Report message to a moderator

Rate author: +1 -1

Re: Improving development process [message #165941 is a reply to message #165935]

Sun, 28 August 2011 21:01

JanRei

Messages: 361
Registered: October 2005
Location: Germany

Karma: 0

Senior Member
Contributing Core Developer
Translator

remove from buddy list
ignore all messages by this user

1. I had a look at the Tracker feature. It seems to offer the basic things. Because we have Trac already enabled we could use this as bugtracker. At the moment I would prefer Trac because it allows to specify milestones for tickets and to create roadmaps for them. What do you think?

2. Currently I don't have something really disruptive. I meant a way to commit fixes that, for example, might be too risky for 3.0.3 and should go into 3.0.4.

As I am still learning PHP I am not sure I can write a documentation for the coding standards.

Report message to a moderator

Rate author: +1 -1