Bugzilla – Full Text Bug Listing
| Summary: | [restructure] modeling.mdt.papyrus Move to direct subproject of Modeling TLP | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cletavernier, rschnekenburger, sebastien.gerard |
| Version: | unspecified | ||
| Target Milestone: | 2017-Q3 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | http://wiki.eclipse.org/Modeling/project_termination_review_2012 | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | |||
| Bug Blocks: | 463929 | ||
|
Description
Wayne Beaton
(In reply to Wayne Beaton from comment #0) > The required restructuring review to move Papyrus was done some time ago > with the Great Modeling Restrucuturing Review of 2012. I'll use this bug to > track the actual move. > > AFAICT, the only thing that needs to change is the ID of the project. This > will affect our internal systems and: > > * The IPZilla component will change from modeling.mdt.papyrus to > modeling.papyrus > * We'll create a new URL to find the project in the PMI (the old one will > continue to work as well) > > AFAICT, no changes are required for Bugzilla, Git, or Hudson. > > Am I missing anything? AFAIK, the download area could be impacted (currently download.eclipse.org/modeling/mdt/papyrus/updates/...). For that part, we would like to impact only for the 'N' version of Eclipse, or at least be able to keep compatibility (maybe keep the 2 namespaces until no more old adress is needed, at the end of Mars maintenance). (In reply to Remi Schnekenburger from comment #1) > AFAIK, the download area could be impacted (currently > download.eclipse.org/modeling/mdt/papyrus/updates/...). For that part, we > would like to impact only for the 'N' version of Eclipse, or at least be > able to keep compatibility (maybe keep the 2 namespaces until no more old > adress is needed, at the end of Mars maintenance). You can decide what to do. The Webmaster can provision [downloads]/papyrus and you can maintain both locations as long as you need to. My only concern is that we not confuse our users. I'll leave it to you to best decide how you avoid that. Totally agree with you, we do not want to have users confused also. We will keep our existing versions (at least until Luna) on the mdt/papyrus namespace. We will switch for new versions on the new adress. We still have to consider the Mars case, but that will probably be the new one. In fact, we ship Papyrus in the mars/release namespace, so the mdt/papyrus should only be used for nightlies. We also use mdt/papyrus for released update sites which shouldn't change anymore, so we'll keep them where they are (Our internal release update sites contain sources + extra, which are not included in the release train) Mars can still be moved to the new location since it hasn't been released yet, but we need to do that early to anticipate any issue Is the archive.eclipse.org server also affected in the same way? (We also use modeling/mdt/papyrus there, but we can do the migration as well) (In reply to Camille Letavernier from comment #4) > Mars can still be moved to the new location since it hasn't been released > yet, but we need to do that early to anticipate any issue There's no need to wait for a review. You can ask the webmaster@eclipse.org to create this whenever you want it. > Is the archive.eclipse.org server also affected in the same way? (We also > use modeling/mdt/papyrus there, but we can do the migration as well) The archive server is structured the same way. You can leave the old structure in place there long term. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Let's try to tackle this in 2017Q3. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. I'm under motivated to lead this effort at this time. If somebody feels more strongly that this needs to happen, feel free to reopen. |