Community
Participate
Working Groups
Jetty is participating in Juno. IP log and review documentation received. IP log has been sent back with questions about one library.
The review documentation states the version as 8.1.3; the project meta data contains an entry only for 7.6.4. Which is correct? Review documentation also states an incorrect review date and copyright date.
Created attachment 216052 [details] Review documentation (ODP)
Depends on how you want to setup metadata really... 7.6.4 will be the next release of jetty, as will 8.1.4 but 8.1.3 is what is going into juno
actually which metadata are you looking at? I see our main metadata and the review date is from when it was initially reviewed? or is this considered a brand new review just re-reviewing the review from before?
I see 7.6.4 in the main metadata under release (perhaps incorrectly) but I don't see it in the simultaneous release metadata screens... and regardless, we are staging the 7.6.4 and 8.1.4 releases today, likely out next week but they are not what we are contributing to juno so....I am not seeing where we can adjust this value
(In reply to comment #5) > and regardless, we are staging the 7.6.4 and 8.1.4 releases today, likely out > next week but they are not what we are contributing to juno so....I am not > seeing where we can adjust this value We pick up the release record with a date that aligns with the simultaneous release. You can actually have multiple versions included with the release by creating multiple release records (the Eclipse project does this). Because there is no explicit linkage in our database, we have to guess at which releases are aligned with the simultaneous release. This is made more difficult by projects that do not consistently enter the actual release date. After much trial and error, I gave up and now just pick any release that occurs in the same month as the simultaneous release. So the current implementation is picking up your 7.6.4 which is in very early June. I believe that we're collectively getting better at specifying correct metadata, so I'll play with narrowing the date range to the week of the release.
ok, for the record it is 8.1.3 that we will be going with for juno then
(In reply to comment #7) > ok, for the record it is 8.1.3 that we will be going with for juno then Add a release record to your project metadata for that, please.
added
(In reply to comment #9) > added I don't see it. Where did you add it?
release jetty-7.6.3 jetty-8.1.3 jetty-7.6.4 under Eclipse Project Metadata in the portal?
I see a 8.1.3 release on 2012-04-16. That doesn't coincide with Juno. The release date needs to be 2012-06-27.
ok, I'll adjust it... and I have to say, this just defies logic in so many ways....:)
updated
(In reply to comment #13) > and I have to say, this just defies logic in so many ways....:) I've explained the logic. The simultaneous release is on June 27th. Unless my undestanding of the words "simultaneous" and "release" are flawed, it seems pretty logical to me that all participating projects release on the same day.
i understand where you are coming from, it just seems backwards to me or crazy that everyone is _releasing_ on the same day it makes far more sense to me that the simultaneous release is actually just the aggregated release of a bunch of software that already released already at some other point in the past year the intended jetty release for juno was released on april 16th...though we have rerolled it into a p2 repo today to address a security issue that cropped up...but that just means the release going into juno was released May 22nd. anyway, kinda funny how 'release' can have so many different meanings to different people...jeff mcaffer and I used to verbally spar on this topic from time to time
Tossing my two cents in here. Jetty 8.1.3 will have already been released by the project. It is just what is contributed to the release train (at least that is my understanding), so it doesn't make sense to have it's release date the same date as Juno, as it's already been released by the project before then.
If Jetty is including a service release in Juno, then no review is necessary. Marking as INVALID, but I really mean UNNECESSARY.
