Bug 535371 - [release] technology.usssdk 2.0.0
Summary: [release] technology.usssdk 2.0.0
Status: RESOLVED WONTFIX
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Proposals and Reviews (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Management Organization CLA
QA Contact:
URL: https://projects.eclipse.org/projects...
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2018-05-30 23:22 EDT by Wayne Beaton CLA
Modified: 2018-06-01 14:35 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Beaton CLA 2018-05-30 23:22:29 EDT
We'll use this bug to track the release

We require IP Team approval of the IP Log.

We require PMC approval of the release and review materials.
Comment 1 Christopher Guindon CLA 2018-05-31 09:18:34 EDT
Brian are we still planing to release 2.0?


Based off our last conversation, I assume the only feature we will include is the removal of Session authentication?
Comment 2 Brian de Alwis CLA 2018-06-01 13:00:51 EDT
I think no: let's keep 1.1.0.  I'd like to use 2.0 as an opportunity to really go through the code and break API if necessary.  None of the known consumers of the USS-SDK use the Sessions API, and the classes involved are not documented in devguide (https://wiki.eclipse.org/Eclipse_USS) and were marked as deprecated in 1.1.0.
Comment 3 Wayne Beaton CLA 2018-06-01 13:17:41 EDT
(In reply to Brian de Alwis from comment #2)
> I think no: let's keep 1.1.0.  I'd like to use 2.0 as an opportunity to
> really go through the code and break API if necessary.  None of the known
> consumers of the USS-SDK use the Sessions API, and the classes involved are
> not documented in devguide (https://wiki.eclipse.org/Eclipse_USS) and were
> marked as deprecated in 1.1.0.

AFAICT all of the bundles in the simrel repository have 2017 dates on them. Are these the 1.2 bits?

I'll need a release record for version 1.2. You can create a new one, or change the information in the existing 2.0 record. Once you've sorted that out, I'll need the IP Log submitted, please.
Comment 4 Brian de Alwis CLA 2018-06-01 14:07:58 EDT
1.1, not 1.2.
Comment 5 Wayne Beaton CLA 2018-06-01 14:35:03 EDT
(In reply to Brian de Alwis from comment #4)
> 1.1, not 1.2.

My apologies. So the same bits as last year then. I'll update the Photon participation record.

Please update the existing 2.0 record with a new (later) release date. 

I'll mark this bug as WONTFIX. We'll reopen it when we start the release process for 2.0.