unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Pirate Praveen <praveen@debian.org>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public@bogomips.org
Subject: Re: Request to follow SemVer/mention it in homepage
Date: Wed, 30 Sep 2015 21:34:13 +0530	[thread overview]
Message-ID: <560C07FD.9060208@debian.org> (raw)
In-Reply-To: <20150929193627.GA7572@dcvr.yhbt.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wednesday 30 September 2015 01:06 AM, Eric Wong wrote:
> Pirate Praveen <praveen@debian.org> wrote:
>> On २९ सप्टेंबर, २०१५ १:०६:५० [PM] IST, Eric Wong <e@80x24.org> 
>> wrote:
>>> Pirate Praveen <praveen@debian.org> wrote:
>>>> Do you follow Semantic Versioning as defined by semver.org? 
>>>> If yes, can you mention it on the homepage? If not, can you 
>>>> consider it?
> 
> <snip>
> 
>>> I have considered it in the past, but decided against it...
>>> 
>>> unicorn is on the verge of becoming 5.x:
>>> 
>>> This is for internal changes which some weirdo projects 
>>> (notably Rainbows!) rely on; but was never considered public 
>>> API or marketed as such.  I absolutely do not want people 
>>> building server-specific apps when Rack exists.
>> 
>> Can you consider SemVer from 5.x?
> 
> Again, the answer is "no".  I do not want people to depend on 
> unicorn providing a stable API of any sort.  Even if in practice 
> and history it does: the config file directives and internal 
> constant names haven't changed at all in 5-6 years and there are
> no plans to change it.

Can you mention the recommended way of adding unicorn in a Gemfile in
your home page?

gitlab and diaspora has unicorn in their Gemfile, for a user they want
gitlab or diaspora and they don't care if its using unicorn or puma or
passenger.

I need some kind of an official statement about compatibility which I
can show to projects like gitlab and diaspora, so they don't insist on
exact patch release of unicorn. I could patch the Gemfile, but that
adds extra burden on me as a maintainer which I'd like to avoid if
possible.

>>> Regardless of a formalities such as semver, I'll work to
>>> ensure unicorn can be compatible[1] with any Rack apps in
>>> Debian main. Heck, perhaps Rack 0.9.x still works (assuming
>>> the installed Ruby version supports it).
>>> 
>>> Just let us know what real problems you find, they will be 
>>> fixed.
>> 
>> If you can convince gitlab to declare ~> 4.8 and assure it will 
>> work with 4.9, that will solve the issue for now.
>> 
>> See https://gitlab.com/gitlab-org/gitlab-ce/issues/2820
> 
> That's not a real compatibility bug with unicorn itself.  Again, 
> it's wrong of them to have a dependency on any Rack server at all.
> 
>> Also if you can help convinse diaspora upstream to declare a 
>> looser dependency, that will also help.
>> 
>>> Fwiw, Debian is my preferred platform and I can stay 100% 
>>> within email with the Debian BTS + lists.
> 
> I am only doing plain-text email.  I'm done with websites requiring
> login + registration.
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWDAf9AAoJEM4fnGdFEsIqYV0P/AmIFATrnxSF4V5Q5v05LT5G
LcVkXCzMhQYnPaVYwiAEi5JLGkiFw2r2Y5kWgF3WLynXHqWmUpGoNLEsG5tZG38V
109RYYKG5VgsGw6HlIoOwpy61MF9/d29+CRDXvLs0q7wc1/CbDEYqnhwLvKKOT9o
xZBD3bXsLuXiRl/BR8xk1q5fy4oS0rNnTU4MWcc8pEKU3KFE0xkXqA5WVS3ENShg
WLfqlUnll2SnQwyR1FzqFJws5OzejKpdNRZK1IOD1ivMd8aBVY25+0u6Q3o/2h/J
dW4ID9QV6R1fCtLybKqkI/fwljlKGs+shY+5lvUqE2KSYe8gwyHm6r1DslprzwM6
QhzLXqBtvDxSxX41sbcr12SoEt7poRztr+8gFXqni+iTkoljgsmODQMWX/ed/9O8
AekqfSrA//K1JfUpGKWHr1+UXhijHggYcKi0eoCJA2GH5ijLu5DIglEuGCQtthl9
z4/aI/na1M7goqBKw1Qtuxc/AHlBAkDcsott5n+4FIQInc5ooiyj54+Sek1AZNWw
/pp5F6z3axPgH3+h26Jf4W8OHl58gUeht9G7sl2j5GwMDkVSOtwlgwhLEYWdZ8Mw
pZcDXl/0VieD6LBFEh3N5MfkP+n3aYHrenCbsxRBh/jn6/+wczoUruNYl0SbSgUh
62qZ2q/7NgvHBdVPtXaB
=F2uT
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-09-30 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  6:38 Request to follow SemVer/mention it in homepage Pirate Praveen
2015-09-29  7:36 ` Eric Wong
2015-09-29  7:46   ` Lin Jen-Shin (godfat)
2015-09-29  8:00   ` Pirate Praveen
2015-09-29 19:36     ` Eric Wong
2015-09-30 16:04       ` Pirate Praveen [this message]
2015-09-30 19:51         ` Eric Wong
2015-10-01  4:56           ` Pirate Praveen
2015-10-01 11:18             ` Pirate Praveen
2015-10-01 19:06               ` Eric Wong
2015-09-29  9:26   ` Jérémy Lecour
2015-09-29 19:43     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560C07FD.9060208@debian.org \
    --to=praveen@debian.org \
    --cc=e@80x24.org \
    --cc=unicorn-public@bogomips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).