Return-Path: X-Original-To: apmail-metamodel-dev-archive@minotaur.apache.org Delivered-To: apmail-metamodel-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F1E07112D6 for ; Mon, 30 Jun 2014 09:08:46 +0000 (UTC) Received: (qmail 60772 invoked by uid 500); 30 Jun 2014 09:08:46 -0000 Delivered-To: apmail-metamodel-dev-archive@metamodel.apache.org Received: (qmail 60736 invoked by uid 500); 30 Jun 2014 09:08:46 -0000 Mailing-List: contact dev-help@metamodel.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@metamodel.incubator.apache.org Delivered-To: mailing list dev@metamodel.incubator.apache.org Received: (qmail 60719 invoked by uid 99); 30 Jun 2014 09:08:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jun 2014 09:08:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of i.am.kasper.sorensen@gmail.com designates 209.85.212.180 as permitted sender) Received: from [209.85.212.180] (HELO mail-wi0-f180.google.com) (209.85.212.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jun 2014 09:08:42 +0000 Received: by mail-wi0-f180.google.com with SMTP id hi2so5585332wib.1 for ; Mon, 30 Jun 2014 02:08:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=q2G4VVDwoUsPh6F3LSMuWhfjSxO17fpXg+Hd/s7hTrw=; b=jfs/1PZTEKnsgav1cvS3B6cV8q/s1wA5glycaPmaahvC9+Ca6iAwpglHb5394OK7g/ oIz/B8twVrZAiOExXzzzwxVqFUTTgTJ6fSamy3MZJzccxveA8YNSQrsXwsDDsUb0Rs/W vGp1hJRUxfA08RImBu/yWrzHAzBDcueI0sX4YMqKxdOdaObtyN9Zh9GtxFNFSOnRNsuB hYKwC15oMkLKP4QA8pxPvY5saWNnzsNJyZt/Y5qqQ3zj/3NEQtpQrVBlRFU2TXxavo5w a8XYgP0RR4TBm7CgD4DXFzARh//J5SwBZRsbzCr4cJtaTTIMzdj8zaZjabikBv3VPiIh Exxw== MIME-Version: 1.0 X-Received: by 10.194.119.9 with SMTP id kq9mr33167333wjb.49.1404119298367; Mon, 30 Jun 2014 02:08:18 -0700 (PDT) Received: by 10.194.163.7 with HTTP; Mon, 30 Jun 2014 02:08:18 -0700 (PDT) In-Reply-To: References: <20140625141504.04D6F2388D4E@eris.apache.org> Date: Mon, 30 Jun 2014 11:08:18 +0200 Message-ID: Subject: Re: Incubator PMC/Board report for Jul 2014 ([ppmc]) From: =?UTF-8?Q?Kasper_S=C3=B8rensen?= To: "dev@metamodel.incubator.apache.org" Content-Type: multipart/alternative; boundary=089e0118451e0067de04fd0a003f X-Virus-Checked: Checked by ClamAV on apache.org --089e0118451e0067de04fd0a003f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable OK that makes sense I guess. I would then suggest we go for 4.2.0 next time, since it's again adding a lot of stuff (and especially the part about making ColumnType an interface instead of an enum is a big change from compatibility POV). I'll update the CHANGES.txt file because that is currently a mess on master branch then :-P 2014-06-30 9:45 GMT+02:00 Henry Saputra : > Unfortunately that was not the way release in interpreted in ASF, the > RC is a release candidate number for 4.1.0. > So technically we have released 4.1.0 which delivered with RC1. > > I missed the subject of the email you sent out for the last MetaModel > release VOTE, which included the RC postfix. > Mea culpa from me, I assume you know that RC tags are just used to > discriminate different attempts to get particular release. > > We could do next 4.1.1 or 4.2.0. > > - Henry > > On Mon, Jun 30, 2014 at 12:36 AM, Kasper S=C3=B8rensen > wrote: > > Well in my opinion we only released "RC1", so one milestone on the way > > towards 4.1 ... But maybe that part needs more sharing of ideas etc. I > > would also be fine calling the next release 4.2 and then just skip the > > RC-suffix. > > > > > > 2014-06-30 6:49 GMT+02:00 Henry Saputra : > > > >> HI Kasper, > >> > >> Thanks for taking stab at the report. > >> > >> I believe 4.1.0 is out so I recommend change the status to "Apache > >> MetaModel 4.1.0-incubating was released on Jan 21. This time ..." > >> > >> For the "Three most important issues to address in the move towards > >> graduation" section, why no 2 is about finalize 4.1 release? > >> The 4.1.0 release is out already so we just need to mention about > >> having more releases to demonstrate understanding of ASF policies? > >> > >> - Henry > >> > >> On Sun, Jun 29, 2014 at 12:17 PM, Kasper S=C3=B8rensen > >> wrote: > >> > How about something like this... > >> > - Kasper > >> > > >> > ---- > >> > > >> > MetaModel > >> > > >> > MetaModel is a data access framework, providing a common interface f= or > >> > exploration and querying of different types of datastores. > >> > > >> > MetaModel has been incubating since 2013-06-12. > >> > > >> > Three most important issues to address in the move towards graduatio= n: > >> > > >> > 1. More contributors to increase diversity of the community > >> > 2. Finalize 4.1 release to demonstrate new functionality and > evolution > >> > within Apache > >> > 3. Connect with other projects from Apache's ecosystem such as > HBase, > >> > Phoenix, Cassandra, Optiq > >> > > >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to b= e > >> > aware of? > >> > > >> > None > >> > > >> > How has the community developed since the last report? > >> > > >> > A few new people have started to work actively on the mailing list= . > It > >> is > >> > still a small > >> > community, and growth is needed. On the positive side we do see > certain > >> > new individuals > >> > starting to contribute continuously to the project. > >> > > >> > We have been working on blogging, tweeting etc. to create more > >> out-going > >> > communication > >> > about MetaModel. We feel that more of such activity is needed. > >> > > >> > How has the project developed since the last report? > >> > > >> > Apache MetaModel 4.1.0-RC1-incubating was released on Jan 21. This > time > >> > with a new > >> > release engineer, which meant that the release instructions were > >> > re-iterated and updated. > >> > > >> > Communication on mailing list is improving and we see more > diversity of > >> > requests. > >> > For instance, connectivity to Hadoop and HBase was previously not > very > >> > active > >> > but now it's is taking a good share of the focus. > >> > > >> > Date of last release: > >> > > >> > May 12th > >> > > >> > When were the last committers or PMC members elected? > >> > > >> > June 2013 (but a new committer is being invited just now) > >> > > >> > > >> > 2014-06-25 19:27 GMT+02:00 Henry Saputra : > >> > > >> >> Any volunteer to write up report for July? > >> >> > >> >> - Henry > >> >> > >> >> On Wed, Jun 25, 2014 at 7:15 AM, Marvin wrote= : > >> >> > > >> >> > > >> >> > Dear podling, > >> >> > > >> >> > This email was sent by an automated system on behalf of the Apach= e > >> >> Incubator PMC. > >> >> > It is an initial reminder to give you plenty of time to prepare > your > >> >> quarterly > >> >> > board report. > >> >> > > >> >> > The board meeting is scheduled for Wed, 16 July 2014, 10:30:30:00 > PST. > >> >> The report > >> >> > for your podling will form a part of the Incubator PMC report. Th= e > >> >> Incubator PMC > >> >> > requires your report to be submitted 2 weeks before the board > meeting, > >> >> to allow > >> >> > sufficient time for review and submission (Wed, Jul 2nd). > >> >> > > >> >> > Please submit your report with sufficient time to allow the > incubator > >> >> PMC, and > >> >> > subsequently board members to review and digest. Again, the very > >> latest > >> >> you > >> >> > should submit your report is 2 weeks prior to the board meeting. > >> >> > > >> >> > Thanks, > >> >> > > >> >> > The Apache Incubator PMC > >> >> > > >> >> > Submitting your Report > >> >> > ---------------------- > >> >> > > >> >> > Your report should contain the following: > >> >> > > >> >> > * Your project name > >> >> > * A brief description of your project, which assumes no knowledg= e > of > >> >> the project > >> >> > or necessarily of its field > >> >> > * A list of the three most important issues to address in the mo= ve > >> >> towards > >> >> > graduation. > >> >> > * Any issues that the Incubator PMC or ASF Board might wish/need > to > >> be > >> >> aware of > >> >> > * How has the community developed since the last report > >> >> > * How has the project developed since the last report. > >> >> > > >> >> > This should be appended to the Incubator Wiki page at: > >> >> > > >> >> > http://wiki.apache.org/incubator/July2014 > >> >> > > >> >> > Note: This manually populated. You may need to wait a little befo= re > >> this > >> >> page is > >> >> > created from a template. > >> >> > > >> >> > Mentors > >> >> > ------- > >> >> > Mentors should review reports for their project(s) and sign them > off > >> on > >> >> the > >> >> > Incubator wiki page. Signing off reports shows that you are > following > >> the > >> >> > project - projects that are not signed may raise alarms for the > >> >> Incubator PMC. > >> >> > > >> >> > Incubator PMC > >> >> > > >> >> > >> > --089e0118451e0067de04fd0a003f--