Provide Dart Editor version information for dartlang.org download page

[DartBot]

This issue was originally filed by [email protected]

---

Please provide us with a versionnumber or a buildnumber in the ZIP-filename for download.
Right now it jus says something like: dart-editor-macosx.cocoa.x86_64.zip

In the current situation where things change so fast I am never sure if I already have the latest version or not.
A buildnumber or a remark on the download-page would solve this problem.

[kasperl]

Added Area-Editor, Triaged labels.

[danrubel]

Set owner to @danrubel.

[kevmoo]

Agreed. Version number on the zip would be awesome

And/or a version.txt file of some such in the zip would be great, too

[danrubel]

We plan to generate version information in a file for the dartlang.org download page to consume/display.

---

Added this to the M1 milestone.
Changed the title to: "Provide Dart Editor version information for dartlang.org download page".

[pq]

Set owner to @pq.
Added Accepted label.

[pq]

A simple VERSION file is now being created and uploaded as part of the editor build process. For example:

http://commondatastorage.googleapis.com/dart-editor-archive-continuous/latest/VERSION

Currently it only contains the build id. Open for discussion is whether this should contain more data and/or being in a standard format (e.g., JSON).

---

cc @sethladd.
Added Started label.

[sethladd]

It would be very nice to also include a "Built on YYYY-MM-DD" in the VERSION file.

[sethladd]

A JSON file with build metadata would be HOT. To do this, you'll have to turn on CORS headers for your download location (I don't have access, but it's not hard: https://developers.google.com/storage/docs/cross-origin )

Potential information to include:

• Build number
• Date (in YYYY-MM-DDTHH:MM:SS format)
• Integration or Continuous
• OS
• 64 or 32bit

Thanks!
Seth

[sethladd]

If you make this a JSON file and enable the CORS headers, I can consume from Dart (natively or when compiled to JS)

[pq]

Since one VERSION file describes all the build artifacts for a given build the JSON can't sensibly carry OS or arch details in its payload. Luckily both can be inferred from the artifact names. Integration vs. Continuous is also out since that's not known at build time when the file is created. That said, we can fetch this from the bucket name so not all is lost.

For starters, it looks like we've for a build number and date. Let's start spitballing formats. To kick it off, what about:

{"build" : {
  "id" : "1234",
  "date" : "2012-07-09" <-- is day enough?
  }
}

[sethladd]

Day is fine, yup. Since we can infer the rest of the information from the filename or bucket name, lgtm.

Kathy brings up a good point: version number, eg X.Y.Z. We'd want that included at some point, too.

[pq]

Cool.

Here's where we're heading:

{
  "revision" : "9826",
  "version" : "0.0.1_v2012070961811",
  "date" : "2012-07-09"
}

CL in flight: http://codereview.chromium.org/10689140/

[pq]

Basic version contents are being generated. See, for example:

http://commondatastorage.googleapis.com/dart-editor-archive-integration/latest/VERSION

I believe the last remaining bit is setting up the right CORS settings for the GS bucket.

Seth: could you update with status? Thanks!

---

Removed Type-Defect label.
Added Type-Enhancement label.

[sethladd]

cc @pq.
Set owner to @sethladd.
Removed Area-Editor label.
Added Area-Site label.

[sethladd]

Here's the CORS config for cloud storage:

<?xml version="1.0" ?>
<CorsConfig>
    <Cors>
        <Origins>
            <Origin>*</Origin>
        </Origins>
        <Methods>
            <Method>GET</Method>
            <Method>HEAD</Method>
        </Methods>
    </Cors>
</CorsConfig>

[sethladd]

CL at https://chromiumcodereview.appspot.com/10832333

[sethladd]

Added Fixed label.

[nicolasgarnier]

This issue has been moved to Github as part of a migration. Please use the Issue on Github going forward: https://github.com/dart-lang/dartlang.org/issues