| Summary: | Incorrect or incomplete auto generated data on project overview page | ||
|---|---|---|---|
| Product: | Community | Reporter: | Kevin Sutter <kwsutter> |
| Component: | Project Management & Portal | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chris.guindon, eric.poirier, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Kevin Sutter
AFAICT, this is happening because there are fewer than ten releases. Obviously, this is wrong. The offending code is on line 412 of releases.module. In determining the contents of this list, the implementation asks for the at most ten most recent releases. Following that, instead of looking for the tenth element in the list to determine the start date, it should just grab the last element in the list. Chris or Eric, can you have a look, please? (In reply to Wayne Beaton from comment #1) > AFAICT, this is happening because there are fewer than ten releases. > Obviously, this is wrong. > > The offending code is on line 412 of releases.module. In determining the > contents of this list, the implementation asks for the at most ten most > recent releases. Following that, instead of looking for the tenth element in > the list to determine the start date, it should just grab the last element > in the list. > > Chris or Eric, can you have a look, please? Wayne, I created a patch to address this issue: https://foundation.eclipse.org/r/#/c/1789/ (In reply to Christopher Guindon from comment #2) > (In reply to Wayne Beaton from comment #1) > > AFAICT, this is happening because there are fewer than ten releases. > > Obviously, this is wrong. > > > > The offending code is on line 412 of releases.module. In determining the > > contents of this list, the implementation asks for the at most ten most > > recent releases. Following that, instead of looking for the tenth element in > > the list to determine the start date, it should just grab the last element > > in the list. > > > > Chris or Eric, can you have a look, please? > > Wayne, > > I created a patch to address this issue: > https://foundation.eclipse.org/r/#/c/1789/ This patch is now live: https://projects.eclipse.org/projects/technology.microprofile Closing this bug! Thanks, (In reply to Christopher Guindon from comment #3) > Closing this bug! Um... (In reply to Wayne Beaton from comment #4) > (In reply to Christopher Guindon from comment #3) > > Closing this bug! > > Um... ? (In reply to Christopher Guindon from comment #5) > (In reply to Wayne Beaton from comment #4) > > (In reply to Christopher Guindon from comment #3) > > > Closing this bug! > > > > Um... > > ? Sorry. I was trying to be clever. You hadn't actually closed the bug :-/ (In reply to Wayne Beaton from comment #6) > (In reply to Christopher Guindon from comment #5) > > (In reply to Wayne Beaton from comment #4) > > > (In reply to Christopher Guindon from comment #3) > > > > Closing this bug! > > > > > > Um... > > > > ? > > Sorry. I was trying to be clever. You hadn't actually closed the bug :-/ I changed it to "RESOLVED". This is what I normally do. Is it better for us to use FIXED? Whether you call it Resolved or Fixed, doesn't matter to me... The web page looks much better now. Thank you! (In reply to Christopher Guindon from comment #7) > I changed it to "RESOLVED". This is what I normally do. Is it better for us > to use FIXED? When I looked at the but this morning, it was still marked "NEW". You said in comment 3 that you were closing the bug, but must have accidentally neglected to actually change it to "RESOLVED" before you saved changed. I just changed the status from NEW to RESOLVED/FIXED that last part and tried (and failed) to be really clever about it. Let's take further discussion (if necessary) off line. |