You can assign them to me On 4/13/12 7:48 AM, "Joe Bowser" <[email protected]> wrote:
>Except it did break. It broke in 1.6.0 due to neglect, and was most likely >broken in 1.5 as well. > >I personally despise the build tools, since there seems to be no good >happy >medium for them. They either totally get neglected or they attract so >much >attention when they're written in the flavor of the week that people >bikeshed the hell out of them. > >But it sounds like the majority want to keep it. Who do I assign build >tool ticket to in this case? If people really care about them, who wants >to >do the work? >On Apr 13, 2012 5:43 AM, "Patrick Mueller" <[email protected]> wrote: > >> On Thu, Apr 12, 2012 at 18:53, Filip Maj <[email protected]> wrote: >> >> > We're trying to figure out what the command line tooling is gonna look >> > like ... >> > >> > Until that decision is made I don't think we should touch the scripts. >> > >> >> +1 Ain't broke, don't fix it. >> >> But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we >> make a "decision" on command line tooling. I'm figuring that we'll be >> doing one or two CLI's to "throw away" [1] before figuring out what >>works. >> (and so, the sooner we start building the throw aways, the better). >> >> And especially: I don't want to remove it in 1.7 only to have to add it >> back in 1.8. >> >> [1] >> >>http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away >> >> -- >> Patrick Mueller >> http://muellerware.org >>
