FAQ
Recently released clojure.tools.cli 0.2.0 has breaking API changes that, as
it turns out [1], were announced on the clojure-dev
mailing list but not here. While clojure-dev archives are indeed public,
many regular Clojure users are not aware of that mailing list and cannot
join it
easily (my request was rejected, for example). This is not the first time I
personally come across breaking API changes in "ex-contrib" libraries that
were never announced on this mailing list.

While I have no problem with there being another mailing list I cannot
easily monitor, the fact that breaking API changes that affect end users
are not
announced on this mailing list doesn't sound right to me. clojure-dev is
not mentioned in clojure.tools.cli README and cannot be easily discovered
via clojure.org.

So, Mr. Hickey & other Clojure/core members: please consider changing
"ex-contrib" library release process to include mandatory announcements of
all of all releases on this mailing list. Highlighting breaking API changes
is also very worth doing, in my opinion.

Thank you.

1.
https://github.com/clojure/tools.cli/commit/439917eda8899f90ad75cc92fe37e966420df043#commitcomment-687839
--
MK

http://github.com/michaelklishin
http://twitter.com/michaelklishin

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Search Discussions

  • Gaz jones at Nov 1, 2011 at 7:53 pm
    Hey dude, as I mentioned in the git link you pointed at there...
    apologies for any confusion. The intent was always to make an
    announcement WRT the breaking changes. I think you just caught me in
    the middle of the "merging the changes into master and getting a
    release cut" process. I am not making breaking changes with the
    intention of antagonizing people :D

    ...

    OR AM I

    On Tue, Nov 1, 2011 at 11:49 AM, Michael Klishin
    wrote:
    not
    --
    You received this message because you are subscribed to the Google
    Groups "Clojure" group.
    To post to this group, send email to clojure@googlegroups.com
    Note that posts from new members are moderated - please be patient with your first post.
    To unsubscribe from this group, send email to
    clojure+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/clojure?hl=en
  • Gaz jones at Nov 1, 2011 at 7:54 pm
    Just to clarify.. no I'm not.
    On Tue, Nov 1, 2011 at 2:52 PM, gaz jones wrote:
    Hey dude, as I mentioned in the git link you pointed at there...
    apologies for any confusion. The intent was always to make an
    announcement WRT the breaking changes. I think you just caught me in
    the middle of the "merging the changes into master and getting a
    release cut" process. I am not making breaking changes with the
    intention of antagonizing people :D

    ...

    OR AM I

    On Tue, Nov 1, 2011 at 11:49 AM, Michael Klishin
    wrote:
    not
    --
    You received this message because you are subscribed to the Google
    Groups "Clojure" group.
    To post to this group, send email to clojure@googlegroups.com
    Note that posts from new members are moderated - please be patient with your first post.
    To unsubscribe from this group, send email to
    clojure+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/clojure?hl=en
  • Stuart Halloway at Nov 1, 2011 at 8:58 pm

    Recently released clojure.tools.cli 0.2.0 has breaking API changes that, as it turns out [1], were announced on the clojure-dev
    mailing list but not here. While clojure-dev archives are indeed public, many regular Clojure users are not aware of that mailing list and cannot join it
    easily (my request was rejected, for example). This is not the first time I personally come across breaking API changes in "ex-contrib" libraries that were never announced on this mailing list.

    While I have no problem with there being another mailing list I cannot easily monitor, the fact that breaking API changes that affect end users are not
    announced on this mailing list doesn't sound right to me. clojure-dev is not mentioned in clojure.tools.cli README and cannot be easily discovered via clojure.org.

    So, Mr. Hickey & other Clojure/core members: please consider changing "ex-contrib" library release process to include mandatory announcements of all of all releases on this mailing list. Highlighting breaking API changes is also very worth doing, in my opinion.

    Thank you.

    1. https://github.com/clojure/tools.cli/commit/439917eda8899f90ad75cc92fe37e966420df043#commitcomment-687839
    --
    MK

    http://github.com/michaelklishin
    http://twitter.com/michaelklishin
    Hi Michael,

    I agree with you, it would be good if the contrib project READMEs all mentioned the dev list. Any contrib authors want to create a page in the dev wiki with a standard minimal README for library authors to refer to?

    Rich has already covered the main point, that all releases should be announced here.

    Thanks for your feedback.

    Stu
    Clojure/core

    --
    You received this message because you are subscribed to the Google
    Groups "Clojure" group.
    To post to this group, send email to clojure@googlegroups.com
    Note that posts from new members are moderated - please be patient with your first post.
    To unsubscribe from this group, send email to
    clojure+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/clojure?hl=en

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupclojure @
categoriesclojure
postedNov 1, '11 at 4:54p
activeNov 1, '11 at 8:58p
posts4
users3
websiteclojure.org
irc#clojure

People

Translate

site design / logo © 2022 Grokbase