> 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.
Derrell, I really don't know what you are talking about. The commit that changed the 'source' job and added 'source-each' was on Aug 19 [1], and on the exact same day this change was announced in the weekly [2], among other things naming 'source-each'. [1] http://qooxdoo.svn.sourceforge.net/viewvc/qooxdoo?view=revision&revision=28514 [2] http://news.qooxdoo.org/the-week-in-qooxdoo-2011-08-19 > Typing "generate.py --help" to get a list of jobs didn't list > it, You knew before that --help doesn't give you the job list, didn't you?! > 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. Yeah, that's a good one. I forgot to mention this in the blog post, and I would have loved to see a bug for it opened. > This is a > sufficiently "advanced" feature that I don't feel it's appropriate to put > people through it. Derrell, you must be kidding. It will work out of the box for new projects, and for existing projects to add a few entries in the "export" section is a no-brainer if you're instructed to do so. This will be in the release notes, and all the way we are working on an automatic conversion that might be able to cover this. Either way should be fine for users. For people working on trunk it should go without saying that they may bump into such issues, which are easily resolved with a post on the mailing list. (Of course I also expect those guys to regularly read the weeklies...). > 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. I really don't see the issue here. We had previous releases which required some manual adjustments to the config, and they were all pretty easy, like this one. I cannot see why anybody would have a problem with it. T. ------------------------------------------------------------------------------ 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 qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
