After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs
* -> see recent #ujet Slack convo from Jan 9 for details
Freeze
* Turn off new PRs and issues
* change README to redirect to new home
* Is there a github native way to make this a smooth DX?
Post Freeze
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* Review package.json for other detritus
Bug 1611226 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs
* -> see recent #ujet Slack convo from Jan 9 for details
Freeze
* Turn off new PRs and issues
* change README to redirect to new home
* Is there a github native way to make this a smooth DX?
Post Freeze
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* Review package.json for other detritus
* anything using package.json’s config "mc_dir ": "../mozilla-central" probably can be removed
* ...
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs
* -> see recent #ujet Slack convo from Jan 9 for details
Freeze
* change README to redirect to new home
* Is there a github native way to make this a smooth DX?
* Turn off new issues/PRs
Post Freeze
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* Review package.json for other detritus
* anything using package.json’s config "mc_dir ": "../mozilla-central" probably can be removed
* ...
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs
* -> see recent #ujet Slack convo from Jan 9 for details
Freeze
* change README to redirect to new home
* Is there a github native way to make this a smooth DX?
* Turn off new issues/PRs
* disable taskcluster runs
* disable travis runs
Post Freeze
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* remove .travis.yml
* Review package.json for other detritus
* anything using package.json’s config "mc_dir ": "../mozilla-central" probably can be removed
* ...
* Draft post
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs (UNDER REVIEW)
Freeze
* change README to redirect to new home (DONE)
* change README to redirect new issues/PRs (IN PROGRESS)
* disable taskcluster runs
* disable travis runs
Post Freeze
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* remove .travis.yml
* Review package.json for other detritus
* anything using package.json’s config "mc_dir ": "../mozilla-central" probably can be removed
* ...
* Draft post
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs (UNDER REVIEW)
Freeze
* change README to redirect to new home (DONE)
* change README to redirect new issues/PRs (DONE)
* disable travis runs (DONE)
* disable taskcluster runs
Post Freeze
* send announcement w/links to new docs
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* remove .travis.yml from m-c
* Review package.json for other detritus
* anything using package.json’s config "mc_dir ": "../mozilla-central" probably can be removed
* ...
* Draft post
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs (UNDER REVIEW)
Freeze
* change README to redirect to new home (DONE)
* change README to redirect new issues/PRs (DONE)
* disable travis runs (DONE)
* archive repo itself (DONE)
* disable taskcluster runs (believed DONE by archiving)
Post Freeze
* send announcement w/links to new docs
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* remove .travis.yml from m-c
* Review package.json for other detritus
* anything using package.json’s config "mc_dir ": "../mozilla-central" probably can be removed
* ...
* Draft post
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work.
The punch list looks something like this:
Before freeze
* Make all necessary doc stuff available (and discoverable) in fx-source-docs (UNDER REVIEW)
Freeze
* change README to redirect to new home (DONE)
* change README to redirect new issues/PRs (DONE)
* disable travis runs (DONE)
* archive repo itself (DONE)
* disable taskcluster runs (DONE by archiving)
Post Freeze
* send announcement w/links to new docs
* get rid of (or DRY up) duplicate/unnecessary machinery in newtab package.json
* eslint
* prettier
* export
* remove .travis.yml from m-c
* Review package.json for other detritus
* anything using package.json’s config "mc_dir ": "../mozilla-central" probably can be removed
* ...
* Draft post
After discussion with the Messaging System and New Tab teams, we've decided to freeze development in the mozilla/activity-stream github repo, since all development is now happening in mozilla-central. This is a meta bug to track that work. The punch list looks something like this: Before freeze * Make all necessary doc stuff available (and discoverable) in fx-source-docs (DONE) Freeze * change README to redirect to new home (DONE) * change README to redirect new issues/PRs (DONE) * disable travis runs (DONE) * archive repo itself (DONE) * disable taskcluster runs (DONE by archiving) Post Freeze * send announcement w/links to new docs (DRAFTED - waiting for autoland to merge) * get rid of obsolete junk (IN REVIEW - bug 1619405)