-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wednesday 30 September 2015 01:06 AM, Eric Wong wrote: > Pirate Praveen <[email protected]> wrote: >> On २९ सप्टेंबर, २०१५ १:०६:५० [PM] IST, Eric Wong <[email protected]> >> wrote: >>> Pirate Praveen <[email protected]> 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-----
