I get the point about either adding it soon or not adding it. At least I then just want to bring up some discussion topics around potential breaking changes that we could make (will post individual mail threads based on issues/ideas we have on the old bugtracker [1]). But taking them all on would probably mean that the release wouldn't be doable soon. So it's kind of a priority issue, since I also felt that having a release soon is a priority in order to show activity from the incubation perspective.
Maybe a snapshot (or other non-final) way of releasing would be good? Maybe my use of the word "release" wasn't entirely in line with what we can define as a "proper" release. What I had in mind is at least to make public a set of artifacts on the maven central, so that people can start using MetaModel with the org.apache namespace. Potentially well-knowing that there will be some breaking changes coming in the near future. Like what I would normally call an "alpha" release or so. Is that doable on short notice, and then we can rather plan a roadmap to a more official/final release? [1] http://eobjects.org/trac/query?milestone=MetaModel+X.0 2013/7/24 Noah Slater <[email protected]> > Good catches, Matt. Thanks! > > > On 24 July 2013 14:46, Matt Franklin <[email protected]> wrote: > > > We should look into using the svn pub-sub staging area for releases (the > > dist area is required for approved releases already) rather than anything > > on people.apache.org > > > *Facepalm* > > Yes, this is the recommended approach these days! ;) > > > > Assuming we are deploying to the Nexus Maven repository, we can have the > CI > > engine deploy SNAPSHOTS to repository.apache.org. > > > > "Snapshots" work also. ;) Just "release" is a very special word. We need to > be careful with it. > > > > We should document our release process on the website the first time we > run > > through it [2] [3]. > > > > [1] http://rave.apache.org/docs/governance/lazyConsensus.html (there is > a > > comdev page, I just found this one first) > > [2] http://bval.apache.org/release-management.html > > [3] http://rave.apache.org/release-management.html > > > Here's another example: > > http://wiki.apache.org/couchdb/Release_Procedure > > (I've been honing this document for the best part of a decade.) > > -- > NS >
