Just a reminder that there are six issues still in there without owners for 3.1.0. I'll flush those out tomorrow if no one claims them.
On Nov 13, 2012, at 3:25 PM, Jason van Zyl <ja...@tesla.io> wrote: > I have put together a simple roadmap using JIRA macros in Confluence to try > and communicate to users what we're planning to do. > > https://cwiki.apache.org/confluence/display/MAVEN/Roadmap > > There are several issues in the 3.1.0 list that are unassigned, so as a > matter of course if you want to work on it just assign it to yourself and the > stuff that isn't assigned should just get pulled out and pushed back to the > 3.1.x pool. For the folks who popped up to say they wanted to look at > particular issues I made the assignment. So take a look and if you do, or > don't, want to do something then change the assignment. > > I picked a tentative date of November 26th for the 3.1.0 and I think we just > time box it, get done what we can and move on. I'd like to try and get back > to making core releases every 6 weeks, if at all possible. > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder & CTO, Sonatype > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > There's no sense in being precise when you don't even know what you're > talking about. > > -- John von Neumann > > > > > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
