We should definitely include
https://issues.apache.org/jira/browse/BROOKLYN-597 "Remove MD5 and SHA-1
checksums" as part of 1.0.0.  I'd be happy to do this but I see it's got
you assigned to it Richard. Do you have work in progress on this, or would
you like me to look into it? I have a notion that I might polish up the
signing procedure a bit.

Cheers
Geoff

On Sun, 1 Dec 2019 at 14:13, Geoff Macartney <[email protected]>
wrote:

> Hi Ludo,
>
> I am indeed pleased to see this!  I had been thinking of mailing the
> community again on the matter after Christmas was out of the way, let's let
> 2020 be the year of Brooklyn 1.0.0!
>
> That's a great list of things to address. One thing to add would be
> removing some deprecated code. Do you think they are all small changes, or
> do any require extensive work or have a wide impact?
>
> The reason I ask is that I think it would be good to restrict ourselves to
> relatively easy and limited impact changes between now and 1.0.0. My fear
> is that larger changes will take a longer time and push back a release even
> further. It seems to me things are quite stable now; I'd say let's polish
> it up and release it rather than try to make significant improvements.
>
> What does everyone think?
>
> Cheers
> Geoff
>
>
>
>
> On Thu, 28 Nov 2019 at 11:04, Ludovic Farine <[email protected]> wrote:
>
>> Hi everyone,
>>
>> Hope you are all doing well!
>>
>> Christmas is fast approaching and well hopefully a gift we would all like
>> to have: Brooklyn 1.0.0 release :) Geoff would be pleased to hear!
>>
>> Working towards this goal of first official release, these are a few bug
>> fixes and improvements that I believe are worth considering
>> (non-exhaustive
>> and not ordered wishlist!) :
>>
>> Bug fixes:
>>
>>    -
>>
>>    Broken icon links for ELK and DNS entities
>>    -
>>
>>    REST API Swagger error
>>    -
>>
>>    Two different versions of jetty-server
>>    -
>>
>>    Karaf version bump
>>
>>
>> Improvements:
>>
>>    -
>>
>>    Session Management: introduce expiry settings for inactivity or
>> repeated
>>    background API calls
>>    -
>>
>>    User Experience: blueprints ordered by date deployed, cookies to
>>    remember preferred sort criteria and palette preferences
>>
>>
>> Clean-up:
>>
>>    -
>>
>>    Review existing open Pull Requests
>>    -
>>
>>    Fix most of the Jenkins tests
>>
>>
>> What are your thoughts on this scope? Any other suggestions you would like
>> to deliver in this next release?
>>
>> Looking forward to get the community engaging in the next weeks and
>> months.
>>
>> Remember you can participate with others on the official Slack channel
>> *#brooklyn* on the official Apache group. Sign up here
>> https://s.apache.org/slack-invite to join the discussion!
>>
>> Thanks
>>
>> Ludo
>>
>>
>> --
>>
>> Ludovic Farine
>>
>> Senior Technical Project Manager
>>
>>
>> Cloudsoft <https://cloudsoft.io/> | Bringing Business to the Cloud
>>
>> E: [email protected]
>>
>> T: +44 7584 748013
>>
>> L: https://www.linkedin.com/in/ludovicfarine/
>>
>

Reply via email to