Tom,
> > Personally I think it's reasonable to have some guidelines, not
> > hard rules. In this case maybe we could suggest a time constraint:
> > "major release" announcements are ok if they're at least a year apart.
> > (Or six months, or whatever we feel is appropriate.)
Absolutely. The reason why I brought it up is that it's apparent that not
everyone on this list, even, agrees what the guidelines ought to be. We need
a consensus.
> But, I do agree about the time constraints ... maybe throw in a 'past
> track record' also?
Well, that's where we make exceptions, sometimes. For example, if OpenACS
sent us an announcement that wasn't a major release, we might put it up
anyway -- becuase they're very friendly to postgres, they're OSS, and they
have yet to post an announcement of any kind. Bricolage, on the other hand,
we'd stick to the "rules"; David sends me an announcement every patch
release.
for instance, we release 7.5.0, and it will generally
> be ~1 month before 7.5.1 comes out, but it may be 3 before 7.5.2 does ...
Oh, for the PostgreSQL project we post whatever we want. It *is* the
postgresql.org web site, after all.
--
Josh Berkus
Aglio Database Solutions
San Francisco
