On Mon, Nov 21, 2011 at 12:11 PM, ant elder <ant.el...@gmail.com> wrote: > Gosh. Well perhaps its me that needs to go back to school then. But i > find this most unexpected. The ASF FAQ on what is a release says "All > releases are in the form of the source materials needed to make > changes to the software being released." if no unit tests are included > in the source release can anyone seriously be expected to be able to > make non-trivial changes to the source? I now wonder what is the point > of the source release at all, other than IDE debugging or reading > APIs, for real development you'd ave to get the SVN tag. And there is > the how to vote on the release artifacts too, other than checking > theres no compile errors how do release reviewers know the release is > good, or with 60 something modules to manually build is there really > any expectation that anyone other than the RM even attempts a build?
I didn't say that I was happy about the missing tests or the state of svn or anything else, just that there's no requirement that a TLP make monolithic releases. This is kind of an extreme case. I think that Joe and I are thinking about Maven: lots of little plugin modules, no monolithic release at all. On the other hand, no vote involving all of them all at once. If ACE's target model looks like maven (many components releasing on decoupled schedules), then the requirement is that the process of releasing each component is conformant. If ACE's target model is to release a giant school of fish all at once every time, I do share some concern. On the other hand, where have we been all this time? They've shipped as many releases as they've shipped, and gotten votes from this PMC, and now, at the time of the graduation vote, all this produces a ton of email? --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
