Contents |
Project design in progress,
Bundles and repositories are currently built using the code in the "bundling" project. This has caused us problems, because the bundling scripts only get run when we're ready to do an update to a LSB release. Furthermore, repositories can get out of date with what's available on the FTP site.
Ideally, repository maintenance would be automatic, pulling off what's available on the FTP site. Bundles should be an independent job, and should be automatic for updates to things not tied to a particular LSB version.
A rough proposed schedule for this project. When we anticipate that we will reach certain milestones. Also, if the project has an absolutely-must-be-completed-by date, mention it here.
| Milestone | Plan Date | Outlook | Comments |
|---|---|---|---|
| Split bundling, repository, and task-package code. | |||
| Make repository management totally automatic. |
No resources have been dedicated to this project.
No hardware has been dedicated to this project.
List of people who are working on the project and their roles.
| Name | Role |
|---|---|
| Jeff Licquia | Project Owner |
Tasks will map many-to-one to milestones. Tasks are specific actionable work items that need to be completed in order to reach a milestone
| Task | Owner | Status | Outlook |
|---|
| Task | Owner | Status | Outlook |
|---|
Tasks that can't be scheduled yet because they are waiting on some other task or external entity
| Task | Owner | Status | Outlook |
|---|
No comments yet.