Skip to content

Generate and consume the package spec (.packages) #23372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
12 tasks done
sethladd opened this issue May 4, 2015 · 22 comments
Closed
12 tasks done

Generate and consume the package spec (.packages) #23372

sethladd opened this issue May 4, 2015 · 22 comments
Assignees
@mit-mit
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). P1 A high priority bug; for example, a single project is unusable or has many test failures type-enhancement A request for a change that isn't a bug
Milestone
1.12

Comments

@sethladd
Copy link
Contributor

sethladd commented May 4, 2015 •
edited by kevmoo
Loading

This is the main tracking bug to implement the package spec proposal. This proposal has been accepted (but has not yet gone through TC52), and work has begun on implementing it.

This is the main tracking bug. Each platform's specific bug is below:

Note that additional work will be needed in phase 2, see #24112
@sethladd
Copy link
Contributor Author

sethladd commented May 4, 2015

Marked this as being blocked by #23373.

@sethladd
Copy link
Contributor Author

sethladd commented May 4, 2015

Marked this as being blocked by #23374.

@sethladd
Copy link
Contributor Author

sethladd commented May 4, 2015

Added Accepted label.

@sethladd
Copy link
Contributor Author

sethladd commented May 4, 2015

See also this JetBrains plugin tracking issue: https://youtrack.jetbrains.com/issue/WEB-16466

@sethladd
Copy link
Contributor Author

sethladd commented May 7, 2015

Added this to the 1.11 milestone.
Added Priority-High label.

@sethladd
Copy link
Contributor Author

And we're accepted! dart-archive/dart_enhancement_proposals#5

@sethladd
Copy link
Contributor Author

Added Started label.

@sigmundch
Copy link
Member

Marked this as blocking #23565.

@sethladd sethladd added area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). P1 A high priority bug; for example, a single project is unusable or has many test failures Started labels Jun 1, 2015
@sethladd sethladd added this to the 1.11 milestone Jun 1, 2015
@sigmundch sigmundch mentioned this issue Jun 3, 2015
Closed
@DartBot DartBot mentioned this issue Jun 4, 2015
Closed
@sethladd sethladd modified the milestones: 1.12, 1.11 Jun 11, 2015
@sethladd
Copy link
Contributor Author

dart2js has filed their merge request for this new functionality.

@sethladd sethladd changed the title Meta: Implementing package spec proposal Meta: Implementing package spec proposal (.packages) Jun 11, 2015
@nex3
Copy link
Member

nex3 commented Jun 29, 2015

Since I don't see it linked anywhere here, the issue tracking the VM's implementation is #23369.

@nex3 nex3 removed Started area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). labels Jul 2, 2015
@nex3 nex3 changed the title Meta: Implementing package spec proposal (.packages) Generate and consume the package spec (.packages) Jul 2, 2015
@nex3 nex3 added area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). Type-Enhancement and removed area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). labels Jul 6, 2015
@sethladd
Copy link
Contributor Author

sethladd commented Jul 8, 2015

Blocked by dart-lang/pub#1294

@nex3
Copy link
Member

nex3 commented Jul 8, 2015

@sethladd When adding new sub-issues to meta-issues, it would be nice to include them in the master list as well (I've done so for this one).

@sethladd
Copy link
Contributor Author

sethladd commented Jul 8, 2015

Sure. I didn't know if you wanted blockers that came up after we filed the meta issue, since they weren't original implementation issues.

@nex3
Copy link
Member

nex3 commented Jul 8, 2015

I think the main function of the meta-issue is to give people a single place to see "what is the current status of X", so having everything in the main list is a good idea. I'll mention it in the wiki entry.

@sethladd
Copy link
Contributor Author

sethladd commented Jul 8, 2015

sgtm!

@nex3 nex3 mentioned this issue Jul 10, 2015
Merged
@sethladd sethladd mentioned this issue Jul 30, 2015
Closed
This was referenced Jul 31, 2015
Closed
Closed
This was referenced Aug 17, 2015
Closed
Open
@mit-mit
Copy link
Member

mit-mit commented Aug 17, 2015

Meta bug, assigning to self to drive to completion for 1.12.

@mit-mit mit-mit self-assigned this Aug 17, 2015
@mit-mit
Copy link
Member

mit-mit commented Aug 18, 2015

Marking #23373 as complete in checlist

@mit-mit
Copy link
Member

mit-mit commented Aug 18, 2015

Moved #24093 to 1.13

@mit-mit mit-mit mentioned this issue Aug 18, 2015
Closed
8 tasks
@mit-mit
Copy link
Member

mit-mit commented Aug 18, 2015

Created a new issue #24112 to tracks the second phase for this feature targeted for 1.13. Deleting 1.13 work items from present issue that is bound to 1.12.

@mit-mit
Copy link
Member

mit-mit commented Aug 19, 2015

Marking testing task complete as #24092 was closed.

@mit-mit
Copy link
Member

mit-mit commented Aug 19, 2015

Marking this feature complete for 1.12. We will expand on this in 1.13, see #24112

@mit-mit mit-mit closed this as completed Aug 19, 2015
@sethladd
Copy link
Contributor Author

Note, there are many open issues around the implementation of this feature. A sample:

#24126
#24127
#24122
#24116

@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed type-enhancement labels Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mit-mit mit-mit

Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). P1 A high priority bug; for example, a single project is unusable or has many test failures type-enhancement A request for a change that isn't a bug
Projects
None yet
Milestone
1.12
Development

No branches or pull requests
6 participants
@nex3 @sethladd @kevmoo @sigmundch @floitschG @mit-mit