Re: Minor enhancement: CI server now builds trunk packages

> > This is great btw. Just one thought — do you know what the version > number/stability labels are for these builds? > > It's whatever is in the current svn. I didn't feel up to mucking about with a package file class to add a faux release - feel free! > I'm a little concerned that something built from trunk might get out > as a stable version and pear upgrade could easily get confused. > Perhaps a stability level of -dev? with some date as the version > suffix? I'm not sure the best way to name a snapshot built from trunk, > but it might be worth thinking about. > > +1 > > There's only so many hours in a day; and if a lot of the QA tasks we do > > within PEAR can be fully or semi automated; I think we could actually > make a > > dent in the growing lists of tasks without burning out our volunteers. > > > > Very good work. This shouldn't be too difficult with Pyrus. One > alternative approach might be tag, then and then build & release from > the tag. That might be useful to a wider PEAR audience than just the > QA team. > Can you show me?