Re: Formalising the release naming process [Was: GNOME Development Release 2.5.3]

[Tom Lamm <dustyshoes osageinc com>]

I don't chime in often but.... Let's not throw the baby out with the  
bathwater. The names are cool and an important part of the culture. The public  
image of Gnome and the development team is also important. I think we can  
agree that if the name can be announced at a public event, or approved by your  
girlfriend's mother, it's probably ok.

"That and a case of beer" should have been ok. Any reference to body parts  
that are typically covered in public is probably not.

Keep the process simple; remember that we all represent something much  
greater.

Tom Lamm

On 02/09/04 16:22:35, Jeff Waugh wrote:
> <quote who="Miguel de Icaza">
>
> > I agree that it is an extra step for the release process, and if we
> > trusted people to not do something like this, we would not need this, but
> > obviously this trust is not there now.
> >
> > So it is time to formalize this.
>
> Proposal for Formalisation of the GNOME Release Names Process:
>
>   Release names are unimportant and meaningless, and if people start making
>   noises about them being inappropriate, let's just do away with the whole
>   thing entirely for development releases, the same as we've done for our
>   official stable releases. So, going forward, stable and development GNOME
>   aggregate releases (such as the Desktop and Developer Platform) will no
>   longer have release names. Individual module maintainers may continue to
>   do whatever they like.
>
> Let's not spend an enormous amount of time on peripheral issues like this.
>
> - Jeff
>
> --
> GVADEC 2004: Kristiansand, Norway                    http://2004.guadec.org/
>
>                           chown -R us:us yourbase
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Attachment: pgpUw6f85m0Ba.pgp
Description: PGP signature