On Fri, 2003-06-13 at 17:16, The Hermit Hacker wrote:
> On Fri, 13 Jun 2003, Robert Treat wrote:
> > i think the disconnect here is that in the past all aspects of marketing
> > postgresql have been made by the technical guys. now you have a group
> > of people who want to change the way that things are done and if the new
> > people's decisions are going to override the previous policies that were
> > put in place, we need some form acceptance of that and the folks who i
> > see giving that acceptance is the core group. The press releases fall
> > into this category, since the current standard is that we don't make
> > announcements of "point" releases, but the advocacy group is recognizing
> > that something could be gained from spreading the word to right right
> > target audiences. Should we just go and do it? I guess based on Tom's
> > post we should.
>
> I think so too ... but, just curious ... we generally mention something on
> -hackers at least a week before we do any point releases ... shouldn't
> that be enough time to throw together a press release so that the release
> doesn't have to be delayed? same with major releases, there is such a
> long, drawn out beta period before that, where features are frozen ...
> shouldn't there be enough time in there to make one helluva powerful press
> release?
>
I don't want to go into a detailed rehash of the releases, but out of
the last few we've had releases that were wrapped and/or packaged and
announcements sent out to the mailing lists and there was either no
mention on the websites, issues with the ftp mirrors, or no press
releases given. I know for 7.3.3 the actual release date got bumped
around enough I felt unsure when it came to reporting the release status
in the weekly news.
Right now I believe there are two "release process" documents floating
around, one by the advocacy group, and one in the cvs. We'll see how
well they work for the next release.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
