#6018 closed enhancement (wontfix)
composer.lock should be in the repo
Reported by: | slaFFik | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Core | Keywords: | |
Cc: | tjnowell |
Description
As composer will be added to BuddyPress, composer.lock
should be in the repo, more info here and here.
This means that anyone who sets up the project will download the exact same version of the dependencies.
(c) getcomposer.org
Attachments (1)
Change History (9)
#3
@
10 years ago
- Cc tjnowell added
- Keywords 2nd-opinion added
- Milestone changed from 2.2 to Awaiting Review
- Type changed from task to enhancement
#4
@
10 years ago
I don't see what benefit this gives, since the only dependency is the composer installer, and we always want the latest version of that. Perhaps on tagged versions/branches if we added any further dependencies it would be useful
#5
@
10 years ago
- Keywords has-patch removed
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
Let's not do this for now. We can revisit if we start adding extra dependencies in the future. Thanks for the feedback Tom.
Note: See
TracTickets for help on using
tickets.
Copying in Tom for a second opinion, who is my Composer guru. Tom -- should we include this?