I guess what Curt was saying is, him being the "release manager" of
the project, has to find appropriate and free time do all the things for
a release, which is fair enough and understandable.
Perhaps we can have more people to help doing a release? Personally
I've only witnessed one release of FG (0.9.9). And I don't know what's
the policy of this whole project. But could anyone else share the
workload of doing a release? Or it has to be Curt and Curt alone?
If we can do releases at any time, then surely we would have more
control on what we could put into a release?
I think most people, especially developers, prefers figuring out a
features list or goals for a release, and then work towards them. When
these are done, then we might want to go for a one month or two months
code freeze/bug fix/stabilising/testing, followed by the release.
And perhaps we could figure out some sort of roadmap?
> Look, rolling out a new release is a massive effort. We need to do a
> release more than once a year. But my time can be very limited
> depending on what other paying projects I'm involved with during the
> year. So I try to find a balance between a new release date that is
> appropriate for the project and my available time.
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
