Re: [gemini-dev] Release 2.0.0 of gemini-blueprint

[Dmitry Sklyut <dmitry@xxxxxxxxxxx>]

Olaf,

The build is already in publishing SNAPSHOTS to repo.eclipse.org.

My main concern about releasing 2.0 is our inability to easily upgrade spring framework related artifacts. Spring EBR is dead.  Eclipse EBR is focused only on Eclipse artifacts only (if I understand it’s chapter properly).

I have finished upgrading all of the frameworks to R5  compliant releases.

Next step is to remove deprecated pieces, like PackageAdmin and support for ancient versions of frameworks.

I would like to resolve the spring framework dependency issue prior to releasing of 2.0.

What are your thoughts?

Kind Regards,

-- 
Dmitry Sklyut
Sent with Airmail

On June 10, 2014 at 9:54:47 AM, Olaf Otto (olaf@xxxxxxx) wrote:

Hi all,

 

I was wondering which issues are outstanding in order to ship release 2.0.0. Looking at the bugs (https://bugs.eclipse.org/bugs/buglist.cgi?component=Core&list_id=9328345&product=Gemini.Blueprint&resolution=---), I found nothing that looks like a blocker (but some that we may close / wontfix). I feel it is crucial to release to the eclipse maven repo (https://repo.eclipse.org/index.html) since our old releases are in the spring EBR which is scheduled for EOL.

 

@Dmitry, anything I could help with to get the release on the road?

 

Kind regards,

Olaf

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev