Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 521000

Summary: Incorrect or incomplete auto generated data on project overview page
Product: Community Reporter: Kevin Sutter <kwsutter>
Component: Project Management & PortalAssignee: 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 CLA 2017-08-15 21:07:53 EDT
Sent a note to EMO as follows:

On our main Overview page (https://projects.eclipse.org/projects/technology.microprofile), part way down the page, there is a reference to our "Latest Releases".  But, the wording is very strange:

Latest Releases: 

From to November 17th, 2017

It's like it's missing the "from date".  Maybe it should say "From Now to ...", or "From July 7 to ..." or something.

How can we get this to generate better text?  If this is something I can fill in, I haven't figured it out yet.

Reply from Wayne:

I hadn't noticed that before. Please open a bug report.

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Project%20Management%20%26%20Portal
Comment 1 Wayne Beaton CLA 2017-08-17 18:00:44 EDT
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?
Comment 2 Christopher Guindon CLA 2017-08-18 13:22:42 EDT
(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/
Comment 3 Christopher Guindon CLA 2017-09-06 14:28:29 EDT
(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,
Comment 4 Wayne Beaton CLA 2017-09-07 13:30:11 EDT
(In reply to Christopher Guindon from comment #3)
> Closing this bug!

Um...
Comment 5 Christopher Guindon CLA 2017-09-07 13:36:03 EDT
(In reply to Wayne Beaton from comment #4)
> (In reply to Christopher Guindon from comment #3)
> > Closing this bug!
> 
> Um...

?
Comment 6 Wayne Beaton CLA 2017-09-07 13:36:59 EDT
(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 :-/
Comment 7 Christopher Guindon CLA 2017-09-07 13:40:35 EDT
(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?
Comment 8 Kevin Sutter CLA 2017-09-07 14:04:03 EDT
Whether you call it Resolved or Fixed, doesn't matter to me...  The web page looks much better now.  Thank you!
Comment 9 Wayne Beaton CLA 2017-09-07 14:44:06 EDT
(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.