Re: Next release

[Adrian Robert]

On Mar 17, 2005, at 6:50 AM, Stefan Urbanek wrote:

> Citát Adam Fedor <address@hidden>:
>
> > Really, the hard part is not 'making' the release. That's quite easy
> > and almost fun.  The part I really want help with is having people who
> > know each library well to act as library managers - make up a list of
> > release criteria and tell me when a good time to make a release is.
> > GNUstep is to big and too much work for me to do this all by myself.
>
> What about explicitly assigning and publishing a core developer(s) to 
> each
> GNUstep package? The package development leader should:
> - publish TODO list and goals for the package
> - publish plans for the next release (can be discussed with others)
> - approve releases

It's probably not necessary to burden "core developers" with these 
tasks if others are willing to help out.  There are some people who do 
a lot of coding in base and gui and tend to give advice on patches and 
the like.  If any of them want to serve as release manager for base, 
gui, or back then that's great.  But it if not, that's great too, as 
long as they can coordinate with someone else who handles the mechanics 
of managing bug reports, doing stabilization branches, etc..  In this 
model, the release manager gets advice on technical issues and good 
time points for releases from the technical folks, who go on 
concentrating on coding and reviewing patches.

Communications are important -- this would only work if there were 
specific designated people the release manager could contact with 
questions and who are committed to helping them with decisions.

If this could be set up, then it might also be possible to consider 
some kind of regularized release schedule, which might help people 
delivering apps, packaging for distributions, etc..