unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Pirate Praveen <praveen@debian.org>
Cc: unicorn-public@bogomips.org
Subject: Re: Request to follow SemVer/mention it in homepage
Date: Tue, 29 Sep 2015 19:36:27 +0000	[thread overview]
Message-ID: <20150929193627.GA7572@dcvr.yhbt.net> (raw)
In-Reply-To: <40CB6BDA-920D-44E1-B364-D7228248C747@debian.org>

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.

> >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.

  reply	other threads:[~2015-09-29 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  6:38 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 [this message]
2015-09-30 16:04       ` Pirate Praveen
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=20150929193627.GA7572@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=praveen@debian.org \
    --cc=unicorn-public@bogomips.org \
    --subject='Re: Request to follow SemVer/mention it in homepage' \
    /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

Code repositories for project(s) associated with this inbox:

	../../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).