Community
Participate
Working Groups
As Wayne mentioned in bug 329970 we have some occurrences of "Helios" in the Sim Rel tracking code. The ones I know about are in "PHP" code which I can help fix. If fact, these "grid" pages are current in the old /helios/ directory. I'd like to move them to the /indido/ directory and hope/assume they will run there fine. I'll be doing this this evening (Thursday evening) ... unless someone else really wanted to do it? Once that's done, there may be other "database" type things I couldn't do, but seems to get the PHP page in the right spot is the first step.
There are numerous hard-coded references to Helios and URLs. We'll need to work these out. I realize that this is a once-a-year problem, but can we do this more generally? I've created a new file, grid.php, in which I've tried to generalize by parameterizing the name of the release you're targeting (defaulting to the most recent). It's just a start. Rather than create a /indigo directory for these tools, is there a more general name we can use? "/release"? Thoughts?
> > Rather than create a /indigo directory for these tools, is there a more general > name we can use? "/release"? > > Thoughts? I think it is useful to always have a meaningful URL to go with a release. But, I agree, in PHP code it'd be good to "factor out" name dependencies into just a few spots, or one. And ... if this allows it ... then, some common files files could to be located in a more common directory such as /releases, that'd be good. But ... I suggest the first step of that is to copy/past for indigo, and as we find things that need to be "factored out" that we do so, and perhaps then for indigo+1 we'd be in a better position to make a cleaner split of files ... but, even then, I think its more user friendly to always have an 'indigo' in the url, so nothing we do now would be "wasted" or incorrect ... it'd just become more "back ground" or common as we move forward. Want to make a "/releases" directory now? Even if only grid.php is only thing in there? And, btw, ... if you have strong feelings about this, and are ready to do the work ... have at it ... I just wanted to help ... but, help just a little :) not commit to a lot of refactoring of code I'm not familiar with. Perhaps what needs to happen is more obvious to you.
Oh, and in case you've forgotten, there already is a www/indigo directory ... which is where some 'planning' documents are already ... I was just going to copy more there ... but, am fine to go with what you'd like to do.
I copied the "planning" files to www/indigo/planing, but did not get too far testing the grid. When I try to access http://www.eclipse.org/indigo/planning/SimultaneousReleaseGrid.php I get this error message: Execution from Invalid Path (portal_rw). This attempt has been logged. Please contact webmaster@eclipse.org So ... I think this new path needs permission to access databases? I did try to reduce the number of hard coded places where "helios" was. All low hanging fruit, such as to change working to when specific release name not needed, I created/moved one files to a "SimRel" directory in wiki, instead of having specific to a year. Such as http://wiki.eclipse.org/SimRel/Simultaneous_Release_Tracker_FAQ#What_is_an_.27exception.27.3F The other low hanging fruit is that some anchor/link references spell out full URLs, and some of them can be made relative to the current base document, I believe. So ... Wayne ... webmasters ... can you authorize db queries from 'indigo/planning? Wayne ... think this approach is workable? Or would you rather take over and refactor a different way? Thanks all,
(In reply to comment #4) > I get this error message: > > Execution from Invalid Path (portal_rw). This attempt has been logged. Please > contact webmaster@eclipse.org > > So ... I think this new path needs permission to access databases? Correct. We need to send a note to webmaster asking for access to be granted. We can consider moving the common stuff into the /projects directory; I'd rather not add anything new to the root if we can avoid it.
As Wayne and Webmasters know, note was sent and after a few initial failures it all seems to be magically working now .... not sure who fixed what, but thanks! Before closing this as fixed, I'll make one (or two) more arguments to start a "releases" directory. 1) It would mirror what we have on "downloads" server, where we have URLs such as http://download.eclipse.org/releases/helios/ http://download.eclipse.org/releases/indigo/ 2) if some "common" stuff could be put in "releases" instead of "projects" seems more likely those helping with this section of the releases pages could help make changes there, if you'd want, such as myself ... otherwise, every little change to wording, etc., in the common pages (if any) would have to go through Foundation staff. Of course, that could be good thing too ... keep me or others from "breaking" anything. So, I'll leave this open until I hear a response to "releases" directory question, but I certainly don't think it's urgent to do that, just wanted to be sure that decision was final before "announcing" this to rest of the world (and projects). For now, the three main pages all seem to be working correctly and say "indigo" instead of "helios" and all seem to link to the right stuff. http://eclipse.org/indigo/planning/SimultaneousReleaseGrid.php http://eclipse.org/indigo/planning/SimultaneousReleaseGrid.php?showallprojects=true http://eclipse.org/indigo/planning/SimultaneousReleaseOverview.php I'm sure the actual pages still need some fixes to account for the few changes to list of requirements that we made this year, but I'll open a separate bug for those. Let me know if you want to reconsider "releases" directory, but I'm also perfectly fine with the way things are, or if you'd rather just work with putting core, common stuff in "projects".
I'm marking this bug as WONTFIX. I believe that the /projects/releases page serve in place of the grids (which are based on data that we stopped supporting a while back).
