Closed joshzarrabi closed 4 years ago
@paketo-buildpacks/content Please review
After discussion we decided the following ordering will be less likely to break apps that rely on the current order:
- paketo-buildpacks/staticfile
- paketo-community/ruby
- paketo-buildpacks/dotnet-core
- paketo-buildpacks/nodejs
- paketo-buildpacks/go
- paketo-community/python
- paketo-buildpacks/php
- paketo-buildpacks/nginx
- paketo-buildpacks/httpd
- paketo-buildpacks/java
- paketo-buildpacks/procfile
We don't think that there is a hard and fast rule that we can follow to make sure the ordering is correct, and any new buildpack will need careful consideration.
This is an rfc with a proposed method of ordering buildpacks.
Co-authored-by: Arjun Sreedharan asreedharan@vmware.com