Merge lp:~rharding/launchpad/yuiff into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Richard Harding on 2012-07-16 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 15635 |
| Proposed branch: | lp:~rharding/launchpad/yuiff |
| Merge into: | lp:launchpad |
| Diff against target: |
66 lines (+10/-12) 2 files modified
buildout.cfg (+7/-10) lib/lp/app/templates/base-layout-macros.pt (+3/-2) |
| To merge this branch: | bzr merge lp:~rharding/launchpad/yuiff |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Benji York (community) | code | 2012-07-16 | Approve on 2012-07-16 |
|
Review via email:
|
|||
Commit Message
Wire up buildout to install multiple YUI versions and wire up feature flag to YUI Config.
Description of the Change
= Summary =
In order to test different YUI versions behind the feature flag, we need to
have the ability to load up multiple versions into the combo loader directory
and to change which version you get based on the feature flag setting:
js.yui_version
== Pre Implementation ==
Talked with Orange, Curtis, William, and Robert on various ways to tackle dealing with the YUI dep.
== Implementation Notes ==
This is a second pass that expands on the current method of getting YUI from the download-cache through buildout.cfg.
This sets up only the currently used/testing versions and makes sure both are installed by default.
The download cache is updated to pull the raw YUI upstream .zip files to make it easier to update in the future vs rolling our own .tar.gz of things.
This also updates the YUI config to use the already built in value for the
js.yui_version feature flag. When not set, it's set to yui and uses the
default symlink. Otherwise you can specify the actual version file.
Currently you can use the feature flag below to run under the latest 3.5.1
release.
js.yui_version default 1 yui-3.5.1
== Tests ==
All tests should pass as normal. No new tests for this.
== LoC Qualification ==
Yay negative LoC
| Richard Harding (rharding) wrote : | # |
> This looks good to me.
>
> I am a little confused as to why the [yui-3.4] section is gone altogether
> though.
3.4 is gone because it was only ever used to test that the buildout setup was working in budapest. It was constructed to be able to switch the version of yui in development, but we want to be able to run several YUI versions side v side without swapping one for the other. The goal is to jump from the current 3.3.0 to 3.5.1 skipping 3.4.
| Benji York (benji) wrote : | # |
On Mon, Jul 16, 2012 at 5:10 PM, Richard Harding
<email address hidden> wrote:
>> This looks good to me.
>>
>> I am a little confused as to why the [yui-3.4] section is gone altogether
>> though.
>
> 3.4 is gone because it was only ever used to test that the buildout
> setup was working in budapest. It was constructed to be able to switch
> the version of yui in development, but we want to be able to run
> several YUI versions side v side without swapping one for the other.
> The goal is to jump from the current 3.3.0 to 3.5.1 skipping 3.4.
Gotcha.
--
Benji York

This looks good to me.
I am a little confused as to why the [yui-3.4] section is gone altogether though.