If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

release a 1.5 of popcorn.js and put it on popcornjs.org

RESOLVED FIXED

Status

Webmaker
popcorn.js
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: thecount, Assigned: thecount)

Tracking

Details

(Whiteboard: [popcornsite])

(Assignee)

Description

4 years ago
I know there is talk of updating the site to a new one, and using github pages and what not.

But, until then, we should just get a 1.5 out there. Too many people hit issues in 1.3, updating the page to 1.5 and pushing up a new tag should be easy. We should just do it.

cc'in jbuck because I don't know where that site lives or how to change it.
(Assignee)

Updated

4 years ago
Assignee: nobody → scott
(Assignee)

Comment 1

4 years ago
By release a 1.5 I mean we tag master as 1.5, and that's it.
Hah, I read this and totally thought "Wait, we released 1.4?". Would it be insane of me to consider making a basic github page site on the mozilla/popcorn-js repo that could point to some zip files or w/e containing the basics?

Comment 3

4 years ago
I think we can just update the repo that's stored on popcornjs.org to get 1.5 on there. And fix up some of the obvious mistakes, like Lighthouse being our bug tracker. Then we can file another bug "srsly, what's up with our website"
(In reply to Jon Buckley [:jbuck] from comment #3)
> I think we can just update the repo that's stored on popcornjs.org to get
> 1.5 on there. And fix up some of the obvious mistakes, like Lighthouse being
> our bug tracker. Then we can file another bug "srsly, what's up with our
> website"

srsly.

+1 to all of the things you've both said.

Updated

4 years ago
Whiteboard: [popcornsite]
(Assignee)

Comment 5

4 years ago
It is done: http://popcornjs.org/download

Long time coming.

I now have the ability to roll out updates as they come in. So we're going to move to a fast release cycle.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.