On Mon, Sep 26, 2011 at 04:33, Tino Butz <[email protected]> wrote:
>
> So what is your opinion? Do you think we did the right thing by promoting
> the "source-hybrid" job to "source"?
>
I had two problems with this change. Firstly, it was initially "announced"
only in the commit message that changed it. The real announcement came
months later. The problem this produced was that although I'd seen the
commit message, I couldn't remember the name "source-each" and it was
difficult to track it down to figure out what command to use for the "old"
behavior. Typing "generate.py --help" to get a list of jobs didn't list it,
due to problem 2...
The second big issue I had was that "generate.py source-each" wouldn't work
because my config.json didn't know about it. I had to manually add
"source-each" to the export list before it could be used. This is a
sufficiently "advanced" feature that I don't feel it's appropriate to put
people through it.
If everyone with an existing project has to add "source-each" to their
export list, I feel that the change should not be made. It may be, however,
that that would not be typically required. I don't know.
Derrell
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
