Bugzilla – Full Text Bug Listing
| Summary: | Babel update site should be in all packages | ||
|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | package content | Assignee: | Project Inbox <epp.packager-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jonah, kitlo, mknauer |
| Version: | unspecified | ||
| Target Milestone: | later | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Wayne Beaton
So far we never did this, but it sounds interesting and technically there is no reason not to do this... but my first questions are always the same: Who is going to test it, who is responsible for such cross-package inclusions, do we need a policy (e.g. we do not include the repo in the first June release, but add it at a later date with the SR1 release), why don't we include it in the common simultaneous release repository, ...? I think this should be discussed with the community (or planning council) and not only in EPP. Certainly one option is to get Babel to join the release train. I still think that this could be interesting. Adding Kit to the bug, maybe we can get some comments from the Babel project team. *** Bug 333616 has been marked as a duplicate of this bug. *** The bugzilla component "package content" is being decommissioned. Bugs need to be assigned to their specific package. If the issue affects all packages, use the "all-packages" component. Therefore any remaining bugs are now being closed as WONTFIX. If this bug is still relevant, please make a comment and we'll move it to the correct project/component for further investigation. This change was made as part of a bulk change. |