Return-Path: X-Original-To: apmail-asterixdb-dev-archive@minotaur.apache.org Delivered-To: apmail-asterixdb-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 9F02417957 for ; Mon, 4 May 2015 16:48:03 +0000 (UTC) Received: (qmail 79774 invoked by uid 500); 4 May 2015 16:48:03 -0000 Delivered-To: apmail-asterixdb-dev-archive@asterixdb.apache.org Received: (qmail 79725 invoked by uid 500); 4 May 2015 16:48:03 -0000 Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.incubator.apache.org Delivered-To: mailing list dev@asterixdb.incubator.apache.org Received: (qmail 79714 invoked by uid 99); 4 May 2015 16:48:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2015 16:48:03 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of sjaco002@ucr.edu does not designate 54.191.145.13 as permitted sender) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2015 16:47:55 +0000 Received: from mx2.ucr.edu (mx2.ucr.edu [138.23.62.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 6C21A20698 for ; Mon, 4 May 2015 16:47:35 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BiAgAloUdVlDJSfUpchECDGLBRCwaDPQFLlmcHTAEBAQEBARIBAQEBBwsLCR8whBciEXQBBzcCJBIBBQEiNYgJBaJvgzA+MYs5jm4BhFoKhg2NFoFFBYsZaJBegSSGRIxsEiOBFYQ3HoJ2AQEB X-IPAS-Result: A2BiAgAloUdVlDJSfUpchECDGLBRCwaDPQFLlmcHTAEBAQEBARIBAQEBBwsLCR8whBciEXQBBzcCJBIBBQEiNYgJBaJvgzA+MYs5jm4BhFoKhg2NFoFFBYsZaJBegSSGRIxsEiOBFYQ3HoJ2AQEB X-IronPort-AV: E=Sophos;i="5.13,366,1427785200"; d="scan'208";a="376118225" Received: from mail-wg0-f50.google.com ([74.125.82.50]) by smtp2.ucr.edu with ESMTP/TLS/RC4-SHA; 04 May 2015 09:47:15 -0700 Received: by wgso17 with SMTP id o17so156457422wgs.1 for ; Mon, 04 May 2015 09:47:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=DqshAyamN0aFME5K/sZ8FXob242l9IIh1FUhSd8j0d4=; b=SvdLAd1E4xxjyzf1uj6r/zvQT6VU0J+egMh6FZQ9p4JL3sJhail2s1IflYS411orOj cIffbEo18/JGKD+zPwSjVeWoZGSTN1k4+gYvoryYjU7J6drc3KqvlrAEffAx+19N7Ypg 6wiJkoEc2qFkdDJRk8HoWVLNCO1wYHeZzEoPlWayZYRQgsSnzD/I2f+zj03QnKIMxUDD 4KRzWZpJEpRK9xFUXyxkFV4Rrr/8KCIDA0zFGTJWCHpJAxq/SUjgvdzSGqBD6iVi6C0X EpeC/gqFugaaiavNAJzqJUj/yxh1LdVnpHMfkcj636jwThO95AlGm08aN7h8swocmU0B lQug== X-Gm-Message-State: ALoCoQkE5UhSCLo5RoVvCSsuNmxPfmNj2MbDiQ5bdfFB/Kuw6a2vgY/pkdc7VVzzPCjhlPZIQtmY5zR/+qf2tSS/0cCw9vH7YU75wgqN76SSHGU52Jy1vwcQolmjl5CMYfA3orWwi1Lt/jGxS5/1Y1E0zpZM+uKRuw== X-Received: by 10.180.106.73 with SMTP id gs9mr21615353wib.52.1430758034159; Mon, 04 May 2015 09:47:14 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.106.73 with SMTP id gs9mr21615330wib.52.1430758033936; Mon, 04 May 2015 09:47:13 -0700 (PDT) Received: by 10.28.173.8 with HTTP; Mon, 4 May 2015 09:47:13 -0700 (PDT) Date: Mon, 4 May 2015 09:47:13 -0700 Message-ID: Subject: Documentation branch name change From: Steven Jacobs To: "dev@asterixdb.incubator.apache.org" Content-Type: multipart/alternative; boundary=f46d04428fce5f640005154450ca X-Virus-Checked: Checked by ClamAV on apache.org --f46d04428fce5f640005154450ca Content-Type: text/plain; charset=UTF-8 Hi, I had a couple of questions as we are migrating to Apache. 1) As far as I know right now we have no way to push to the documentation branch on Google Code (As the code site is currently read-only, and there is no code review process set up except for the master branch). Is this being addressed in our migration? 2) I was wondering if we could take this opportunity to rename the documentation branch to be more clear. We could call it "release" or something similar. The reason I am asking is because I feel like calling it simply "documentation" is a little confusing. As far as I know, the "documentation" branch represents exactly what is available for end-users today, so it is not only the current documentation but also the latest official release of the code. This makes the name counter-intuitive, at least for me. Any thoughts? Steven --f46d04428fce5f640005154450ca--