Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates
 209.85.220.177 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: 
 <CAOBL_k7_VAAjnxvCEkycv9Zc5046HHdD3TK_gk-GqN2kTu6zHA@mail.gmail.com>
References: <20150202223550.6262862.55201.6364@blackberry.com>
 <CAOBL_k7_VAAjnxvCEkycv9Zc5046HHdD3TK_gk-GqN2kTu6zHA@mail.gmail.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Tue, 3 Feb 2015 08:55:36 -0500
Message-ID: 
 <CAEeF2TdCm0nS+iamjjpGES5YCSuyrc=p4QwkkFwuhzZZ0c7pfQ@mail.gmail.com>
Subject: Re: Cordova-Android 3.7.0 Blog Post
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7b471f0618837d050e2f6ecb

--047d7b471f0618837d050e2f6ecb
Content-Type: text/plain; charset=UTF-8

Its nice when people have a place to look up what changed when they notice
a new version is out.  (Also, when we do a tools release and updated pinned
platforms, we can point back to these posts).  Additionally, some of our
users have come to this list asking for a blog post just recently, so its
not completely unread..

On Tue, Feb 3, 2015 at 6:06 AM, Joe Bowser <bowserj@gmail.com> wrote:

> I don't really like how this is part of the release process at all, and the
> only reason that I'm doing it is because we have to for some reason.  I
> don't really think any of our users actually read this, and I really just
> want to see this done so that it can't be used as an excuse to not ship
> 4.0.x.  I think that the blog posts should be completely decoupled from the
> release process, since my desire to see software released is completely
> different from my desire to further condense release notes that I don't
> think our users read.
> On Mon Feb 02 2015 at 2:36:21 PM Josh Soref <jsoref@blackberry.com> wrote:
>
> > I sent a basic pull request.
> >
> > Offhand, that list should probably be shortened a bit more.
> >
> > Note that if something didn't change between the current release and
> > 3.7.0, readers of the release announcement don't care. I can't figure out
> > if some gradle changes were superceeded by others, or relate to different
> > gradle env targets, if they were superceeded, the ones that don't apply
> as
> > of 3.7.0 should of course be dropped.
> >
> > Offhand, CB-4914 could probably be dropped; CB-8204 probably should be
> > dropped; one instance of CB-8143 should probably be dropped (or not, if
> > they're really different things/for different targets). CB-7410 should
> > probably be dropped too.
> >
> > It's also helpful to group things by area.
> >
> >
>

--047d7b471f0618837d050e2f6ecb--