I don't understand, are we accepting donations and letting people name
releases? What's the point of a "name"? Don't get me wrong, I love the
Toy Story release names for Debian
Counter-counter-proposal 1:
If we want to use this to raise awareness...
Do what Vim does. If people want to donate
Seems like consensus is that this is a bad idea--as formulated.
How about softening the proposal?
Counter-proposal A:
- Tweets, social media posts, changelog, etc. all use the number *only*
- There is a single sentence in the release announcement email and
blog post to the effect of "aka the X r
I'd KISS also - and stick with numbers only, so -0.5 as well
On Mon, Oct 27, 2014 at 9:41 PM, Joan Touzet wrote:
> -0.5 for all the reasons previously outlined.
>
> - Original Message -
> From: "Paul Davis"
> To: d...@couchdb.apache.org, andyw...@apache.org
> Cc: marketing@couchdb.apach
-0.5 for all the reasons previously outlined.
- Original Message -
From: "Paul Davis"
To: d...@couchdb.apache.org, andyw...@apache.org
Cc: marketing@couchdb.apache.org
Sent: Monday, October 27, 2014 3:39:55 PM
Subject: Re: [PROPOSAL] Naming releases
I'm a bit on the -1 side of things as
I'm a bit on the -1 side of things as well. Having two ways to refer
to a release has always annoyed me with projects like Debian/Ubuntu.
Granted they tend to use them a lot more interchangeably than Noah is
suggesting, though I do wonder if it'd still lead to confusion.
I think for the particular
On 27.10.2014 20:30, Andy Wenk wrote:
> I have a bit of a feeling, that the proposal is a bit misunderstood. Noah
> has written:
>
> "We'd mention the name in the release announcement and
> in the changelog. But otherwise, we'd continue to talk about releases
> using the release number."
>
> So w
I have a bit of a feeling, that the proposal is a bit misunderstood. Noah
has written:
"We'd mention the name in the release announcement and
in the changelog. But otherwise, we'd continue to talk about releases
using the release number."
So we use the name for a CouchDB release solely for market
I agree that it can be confusing. Ubuntu is doing that, and even though
I've been using it for almost a decade now (and thus follow its release
cycles pretty closely), I'm still getting confused about their release
names from time to time. Please make sure that our project won't run
the risk of c
Also not a fan, its confusing and there’s an effort involved in coming up with
a name, an artificial impediment to release cycles, and we have enough real
ones.
B.
> On 27 Oct 2014, at 16:45, Jan Lehnardt wrote:
>
> I’m not a fan, but I won’t be in the way of this.
>
> Best
> Jan
> --
>
>
I’m not a fan, but I won’t be in the way of this.
Best
Jan
--
> On 27 Oct 2014, at 14:49 , Noah Slater wrote:
>
> Hi folks,
>
> SUMMARY
>
> I'm currently working on the rewards for the CouchDB AdvocateHub. (See
> bottom of this email for a refresher.)
>
> One of the rewards I'd like to offe
Cool idea. RethinkDB does it very well: in additional they provide
nice branding for each release. It worth to take a look on their
experience.
But to let it works, our releases should be sweet and featured - this
would be hard with rapid releases policy.
--
,,,^..^,,,
On Mon, Oct 27, 2014 at 4:
Hi folks,
SUMMARY
I'm currently working on the rewards for the CouchDB AdvocateHub. (See
bottom of this email for a refresher.)
One of the rewards I'd like to offer is the ability to "name" a
CouchDB release. We'd mention the name in the release announcement and
in the changelog. But otherwise,
12 matches
Mail list logo
