| Summary: | Member distros updates for Mars | ||
|---|---|---|---|
| Product: | Community | Reporter: | Denis Roy <denis.roy> |
| Component: | Website | Assignee: | phoenix.ui <phoenix.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chris.guindon, ian.skerrett, Paul.White, perri.lavergne |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Denis Roy
Also, do we extend the Distros program to include the installer? (In reply to Denis Roy from comment #1) > Also, do we extend the Distros program to include the installer? For now, I suggest we just leave the distro program focused on the packages. This is done. Member Distros are working well for Mars. (In reply to Ian Skerrett from comment #2) > (In reply to Denis Roy from comment #1) > > Also, do we extend the Distros program to include the installer? > > For now, I suggest we just leave the distro program focused on the packages. Since the Installer is now the default download, I think we should make it part of the member distros program. (In reply to Denis Roy from comment #4) > (In reply to Ian Skerrett from comment #2) > > (In reply to Denis Roy from comment #1) > > > Also, do we extend the Distros program to include the installer? > > > > For now, I suggest we just leave the distro program focused on the packages. > > > Since the Installer is now the default download, I think we should make it > part of the member distros program. +1 (In reply to Ian Skerrett from comment #5) > (In reply to Denis Roy from comment #4) > > (In reply to Ian Skerrett from comment #2) > > > (In reply to Denis Roy from comment #1) > > > > Also, do we extend the Distros program to include the installer? > > > > > > For now, I suggest we just leave the distro program focused on the packages. > > > > > > Since the Installer is now the default download, I think we should make it > > part of the member distros program. > > +1 +1 Can this be done for SR1? For members to pick up the distros and replicate them on their servers, I need to know where they are located on our download servers. Bug 477920 suggests download.eclipse.org/oomph/epp/mars/R1/eclipse-inst-* Is that their permanent home?
> +1
>
> Can this be done for SR1?
I have started taking requests for distros for SR1, and each member distro must re-conform for each release.
So now is the time.
(In reply to Denis Roy from comment #7) > For members to pick up the distros and replicate them on their servers, I > need to know where they are located on our download servers. > > Bug 477920 suggests download.eclipse.org/oomph/epp/mars/R1/eclipse-inst-* > > Is that their permanent home? I think you need to ask Eike this question. I guess what I'm getting at -- is that we typically don't ask the members to pull in new packages except for three times per year. Are these the Oomph installer files that we will live with until next February? Or, will we be asking the Members to pull new files once in a while when the Eclipse installer is updated? (In reply to Denis Roy from comment #11) > Or, will we be asking the Members to pull new files once in a while when the > Eclipse installer is updated? I think we will need to ask Members to pull new files. This is long gone. |