FAQ
Is this a byproduct of working in open source, or perhaps a continuous
integration methodology being followed?

(to see this for yourself (on a mac): cd /usr/local/go;grep --exclude=*.o
-rnw . -e "todo" -e "TODO" -e "todo")

Thanks for any clarification!
Jean

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • Jean de Klerk at May 11, 2014 at 11:57 pm
    edit: bad copy paste. cd /usr/local/go;grep --exclude=*.o -rnw . -e "todo"
    -e "TODO" should do it. No need for the double "todo" :)
    On Sunday, May 11, 2014 7:18:19 PM UTC-4, Jean de Klerk wrote:

    Is this a byproduct of working in open source, or perhaps a continuous
    integration methodology being followed?

    (to see this for yourself (on a mac): cd /usr/local/go;grep --exclude=*.o
    -rnw . -e "todo" -e "TODO" -e "todo")

    Thanks for any clarification!
    Jean
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • David Symonds at May 12, 2014 at 12:42 am
    I'm not sure what you're asking. TODOs mark things that are yet to be
    done, either because people haven't had the time or knowledge to do
    them, or aren't in a hurry to do them. They're perfectly normal in
    large code bases.

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Jean de Klerk at May 12, 2014 at 1:53 am
    I suppose I had thought that TODOs in a complex project would be contained
    in something like github issues or some other issue/feature tracking thing,
    rather than lying around in code.

    However, I'm pretty new to code bases of this size, so I wouldn't know
    either way. Just seemed odd.

    Maybe a better question would be, "How do the go dev folks keep track of
    issues/features outside of TODOs, and how do they correlate their (tickets,
    github issues, etc) to the TODO sitting in code?"

    Jean
    On Sunday, May 11, 2014 8:42:48 PM UTC-4, David Symonds wrote:

    I'm not sure what you're asking. TODOs mark things that are yet to be
    done, either because people haven't had the time or knowledge to do
    them, or aren't in a hurry to do them. They're perfectly normal in
    large code bases.
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Hotei at May 12, 2014 at 1:56 am
    There's a separate issue tracking system that's part of the code review
    process. It's not as "ad-hoc" as it looks.
    On Sunday, May 11, 2014 9:53:13 PM UTC-4, Jean de Klerk wrote:

    I suppose I had thought that TODOs in a complex project would be contained
    in something like github issues or some other issue/feature tracking thing,
    rather than lying around in code.

    However, I'm pretty new to code bases of this size, so I wouldn't know
    either way. Just seemed odd.

    Maybe a better question would be, "How do the go dev folks keep track of
    issues/features outside of TODOs, and how do they correlate their (tickets,
    github issues, etc) to the TODO sitting in code?"

    Jean
    On Sunday, May 11, 2014 8:42:48 PM UTC-4, David Symonds wrote:

    I'm not sure what you're asking. TODOs mark things that are yet to be
    done, either because people haven't had the time or knowledge to do
    them, or aren't in a hurry to do them. They're perfectly normal in
    large code bases.
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Silvan Jegen at May 12, 2014 at 2:29 am

    On Monday, May 12, 2014 3:56:02 AM UTC+2, Hotei wrote:
    There's a separate issue tracking system that's part of the code review
    process. It's not as "ad-hoc" as it looks.

    The issues list is here: https://code.google.com/p/go/issues/list

    The code reviews take place on this
    platform: https://codereview.appspot.com/all

    There are Google groups for development (
    https://groups.google.com/forum/#!forum/golang-dev ) and code reviews (
    https://groups.google.com/forum/#!forum/golang-codereviews ) as well.


    Cheers,

    Silvan

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Jean de Klerk at May 12, 2014 at 2:59 am
    Thank you, this makes more sense.

    Jean
    On Sunday, May 11, 2014 10:29:21 PM UTC-4, Silvan Jegen wrote:
    On Monday, May 12, 2014 3:56:02 AM UTC+2, Hotei wrote:

    There's a separate issue tracking system that's part of the code review
    process. It's not as "ad-hoc" as it looks.

    The issues list is here: https://code.google.com/p/go/issues/list

    The code reviews take place on this platform:
    https://codereview.appspot.com/all

    There are Google groups for development (
    https://groups.google.com/forum/#!forum/golang-dev ) and code reviews (
    https://groups.google.com/forum/#!forum/golang-codereviews ) as well.


    Cheers,

    Silvan
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedMay 11, '14 at 11:18p
activeMay 12, '14 at 2:59a
posts7
users4
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase