brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Svetoslav Neykov <svetoslav.ney...@cloudsoftcorp.com>
Subject Re: vagrant version requirements
Date Mon, 04 Apr 2016 15:11:06 GMT
> where do you draw the line in terms of supporting old versions

Do we really need to draw it anywhere, could just drop the version requirement :). Don't think
the Vagrantfile relies on anything recently introduced?
I used a 1.7.x version not too long ago for example.
My point is that this breaks the user's experience if he has to upgrade Vagrant install for
no good reason. Vagrant seems to be the install-and-forget kind of software which you don't
really upgrade.

No strong opinion which versions to require exactly, just wanted to bring it up as a possible
pain point.
Another thing I suggest is to base it on the latest LTS release, having a bigger chance for
it to be already downloaded.

Svet.


> On 4.04.2016 г., at 17:57, John McCabe <john@johnmccabe.net> wrote:
> 
> Hi Svet,
> I agree the 1.8.1 is too specific, 1.8.x is actually sufficient. I reckon
> dropping to verified major version with a suggestion that the user update
> to the current version.
> 
> As for 1.7.x I don't think we want to encourage/support the use of obsolete
> versions - 1.7.0 is from December 2014. The tarball release remains
> available as a fallback in those cases (where do you draw the line in terms
> of supporting old versions).
> 
> wdyt?
> /John
> 
> On Mon, 4 Apr 2016 at 14:41 Svetoslav Neykov <
> svetoslav.neykov@cloudsoftcorp.com> wrote:
> 
>> // Changed subject from Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc2]
>> 
>> Current requirement is >=1.8.1, see [1]. I had 1.8.0 installed - that's
>> how I noticed. But I assume 1.7.x would be widely installed as well?
>> 
>> [1]
>> https://github.com/apache/brooklyn-dist/blame/master/vagrant/src/main/vagrant/Vagrantfile#L23
>> 
>> 
>>> On 4.04.2016 г., at 16:35, John McCabe <john@johnmccabe.net> wrote:
>>> 
>>> @svet, latest isn't required, 1.8+ should suffice.
>>> 
>>> On Mon, 4 Apr 2016 at 12:53 Svetoslav Neykov <
>>> svetoslav.neykov@cloudsoftcorp.com> wrote:
>>> 
>>>> +1 binding
>>>> 
>>>> * Tested the .zip & .tar.gz dists
>>>> * Tested CLI
>>>> * Tried a simple blueprint
>>>> * Tested the vagrant artifact - "vagrant up" *fails* because it's
>> looking
>>>> at the release url
>>>> 
>> https://www.apache.org/dyn/closer.lua?action=download&filename=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz
>>>> <
>>>> 
>> https://www.apache.org/dyn/closer.lua?action=download&filename=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz
>>> .
>>>> Once released should work.
>>>>  Unrelated, but do we require the absolute latest vagrant version on
>>>> purpose? Can we relax this version requirement?
>>>> 
>>>> Svet.
>>>> 
>>>> 
>>>>> On 4.04.2016 г., at 13:14, Sam Corbett <sam.corbett@cloudsoftcorp.com>
>>>> wrote:
>>>>> 
>>>>> +1 binding
>>>>> 
>>>>> I have:
>>>>> * Verified release signatures
>>>>> * Built from the source archive
>>>>> * Generated a project from the archetype
>>>>> * Verified all subsequent archetype instructions were correct
>>>>> * Verified a simple application deployed to AWS.
>>>>> * Given the CLI a work out.
>>>>> 
>>>>> 
>>>>> On 01/04/2016 16:58, Richard Downer wrote:
>>>>>> This is to call for a vote for the release of Apache Brooklyn 0.9.0
>>>> [rc2].
>>>>>> 
>>>>>> This release comprises of a source code distribution, and a
>>>>>> corresponding binary distribution, RPM packages, Vagrant environment
>>>>>> package, and Maven artifacts.
>>>>>> 
>>>>>> The source and binary distributions, including signatures, digests,
>>>>>> etc. can be found at:
>>>>>> 
>>>> 
>> https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc2
>>>>>> 
>>>>>> The artifact SHA-256 checksums are as follows:
>>>>>> 426ca93aad28ac8281b2015fc0ea419cd6db19c3ed87ffd11910a6baf2e9e3ab
>>>>>> *apache-brooklyn-0.9.0-rc2-1.noarch.rpm
>>>>>> b2a65642fb86198b9fd9992ef3464025d9b41c453c4dd5366699d569a65709c6
>>>>>> *apache-brooklyn-0.9.0-rc2-bin.tar.gz
>>>>>> 999fd6f1d21417278ffe153fc1f0346d44235dfbbd39f200815f61cea82edbe5
>>>>>> *apache-brooklyn-0.9.0-rc2-bin.zip
>>>>>> 00e0a76775775957e92498d0b5ea3e13f844155eda3251a8ead05cf4b4a4455b
>>>>>> *apache-brooklyn-0.9.0-rc2-src.tar.gz
>>>>>> c7a9a286993b1d520ae6a32e25c0dd3bef7227290d59347256bd96480b70a02b
>>>>>> *apache-brooklyn-0.9.0-rc2-src.zip
>>>>>> 907267c5d2e7c1622e11f2bc57b6afe12ddf2136d82bad63661e43570aaa78fa
>>>>>> *apache-brooklyn-0.9.0-rc2-vagrant.tar.gz
>>>>>> 0ae8384426d6b7197ca3d194c1e8032b85c5bb80671157c274487220d3ba65e9
>>>>>> *apache-brooklyn-0.9.0-rc2-vagrant.zip
>>>>>> 
>>>>>> The Nexus staging repositories for the Maven artifacts are located
at:
>>>>>> 
>>>> 
>> https://repository.apache.org/content/repositories/orgapachebrooklyn-1016
>>>>>> 
>>>> 
>> https://repository.apache.org/content/repositories/orgapachebrooklyn-1017
>>>>>> 
>>>>>> All release artifacts are signed with the following key:
>>>>>> https://people.apache.org/keys/committer/richard.asc
>>>>>> 
>>>>>> KEYS file available here:
>>>>>> https://dist.apache.org/repos/dist/release/brooklyn/KEYS
>>>>>> 
>>>>>> The artifacts were built from these Git commit IDs:
>>>>>> brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c
>>>>>> brooklyn-client: 64573c8e1b8630f59b23356520282c91cc46a8a1
>>>>>> brooklyn-dist: 0b8b81df458fa4323939582d9f0dda10b2f6eaee
>>>>>> brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518
>>>>>> brooklyn-library: 2565e6eb2868468ec2528df74fe85efdb887b6d2
>>>>>> brooklyn-server: d031cea080613645219ba982c93264943798d4fc
>>>>>> brooklyn-ui: 307382128951bb237bc351ac22136745e5d50475
>>>>>> All of the above have been tagged as "apache-brooklyn-0.9.0-rc2".
>>>>>> 
>>>>>> 
>>>>>> Please download the artifacts, test, and vote on releasing this
>>>>>> package as Apache Brooklyn 0.9.0.
>>>>>> 
>>>>>> The vote will be open for at least 72 hours.
>>>>>> [ ] +1 Release this package as Apache Brooklyn 0.9.0 (please describe
>>>>>> the tests you have performed)
>>>>>> [ ] +0 no opinion
>>>>>> [ ] -1 Do not release this package (please describe why not)
>>>>>> 
>>>>>> Thanks
>>>>>> Richard.
>>>>> 
>>>> 
>>>> 
>> 
>> 


Mime
View raw message