On Mon, 8 Jun 2015 13:03:56 -0300 Claudio Freire <[email protected]> wrote:
> > Ohmygosh, you have to rpm install a bunch of -devel stuff? What a massive > > hardship. > > It's not about the 5 minutes of compile time, it's about the signalling. > > Just *when* is git ready for testing? You don't know from the outside. > > I do lurk here a lot and still am unsure quite often. > > Even simply releasing an alpha *tarball* would be useful enough. What > is needed is the signal to test, rather than a fully-built package. This. The clients I referred to earlier don't even use the rpm packages, they build from sources. They need to know when it is worthwhile to take a new set of sources and test. Some sort of labeling about what the contents are would enable them to do this. I don't think a monthly snapshot would work as well as the requirement is knowing that "grouping sets are in" not that "it is July now". -dg -- David Gould [email protected] If simplicity worked, the world would be overrun with insects. -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
