Seaside 3.2.4 bugfix release available

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside 3.2.4 bugfix release available

Johan Brichau-2
Hi all,

Seaside 3.2.4 fixes an important bug [1][2]. 
If you are on 3.2.x, you want to upgrade.

cheers
Johan



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

Mariano Martinez Peck
Hi Johan,

Thanks for your effort. Let me ask, what is the status of https://github.com/SeasideSt/Seaside/pull/931 ?
I mean...it was merged but it wasn;'t included in 3.2.4..was that on purpose?

Thanks

On Fri, Jul 14, 2017 at 6:19 AM, Johan Brichau <[hidden email]> wrote:
Hi all,

Seaside 3.2.4 fixes an important bug [1][2]. 
If you are on 3.2.x, you want to upgrade.

cheers
Johan



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

Johan Brichau-2
Hi Mariano,

The reason is merely ‘the order I did this’...

In essence, the version number (and release) on github is just to indicate the correspondence with the version in the ConfigurationOfSeaside3
The master branch on github should always have a stable version. 

I *could* update the version number to latest commit if you want ;)

Johan

On 14 Jul 2017, at 14:58, Mariano Martinez Peck <[hidden email]> wrote:

Hi Johan,

Thanks for your effort. Let me ask, what is the status of https://github.com/SeasideSt/Seaside/pull/931 ?
I mean...it was merged but it wasn;'t included in 3.2.4..was that on purpose?

Thanks

On Fri, Jul 14, 2017 at 6:19 AM, Johan Brichau <[hidden email]> wrote:
Hi all,

Seaside 3.2.4 fixes an important bug [1][2]. 
If you are on 3.2.x, you want to upgrade.

cheers
Johan



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

Mariano Martinez Peck


On Fri, Jul 14, 2017 at 1:09 PM, Johan Brichau <[hidden email]> wrote:
Hi Mariano,

The reason is merely ‘the order I did this’...

In essence, the version number (and release) on github is just to indicate the correspondence with the version in the ConfigurationOfSeaside3
The master branch on github should always have a stable version. 

I *could* update the version number to latest commit if you want ;)


I am not sure I am following you..I was just wondering why if PR was merged into master, why couldn't have we create the tag 3.2.4 AFTER hat merge, so that that PR gets in in 3.2.4 tag/release.

Thanks
 
Johan

On 14 Jul 2017, at 14:58, Mariano Martinez Peck <[hidden email]> wrote:

Hi Johan,

Thanks for your effort. Let me ask, what is the status of https://github.com/SeasideSt/Seaside/pull/931 ?
I mean...it was merged but it wasn;'t included in 3.2.4..was that on purpose?

Thanks

On Fri, Jul 14, 2017 at 6:19 AM, Johan Brichau <[hidden email]> wrote:
Hi all,

Seaside 3.2.4 fixes an important bug [1][2]. 
If you are on 3.2.x, you want to upgrade.

cheers
Johan



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

Mariano Martinez Peck
OK, I think I understand what you mean...by "order" you mean that you simply created the tag 3.2.4 BEFORE merging PR 931  to master. And you are saying that I can take master as it's always the latest stable and so it will have PR 931. 
But... for my app load I first load Seaside, then lock it, then load the rest. And I don't want/like to lock/refer a symbolic thingy like master. I want to stick with a fixed version I easily know which it is. And that's why I like the tags.

In summary, if you can update the tag 3.2.4 to take the latest master commit (which should include 931) , I would really appreciate that.

Thanks!

On Fri, Jul 14, 2017 at 1:25 PM, Mariano Martinez Peck <[hidden email]> wrote:


On Fri, Jul 14, 2017 at 1:09 PM, Johan Brichau <[hidden email]> wrote:
Hi Mariano,

The reason is merely ‘the order I did this’...

In essence, the version number (and release) on github is just to indicate the correspondence with the version in the ConfigurationOfSeaside3
The master branch on github should always have a stable version. 

I *could* update the version number to latest commit if you want ;)


I am not sure I am following you..I was just wondering why if PR was merged into master, why couldn't have we create the tag 3.2.4 AFTER hat merge, so that that PR gets in in 3.2.4 tag/release.

Thanks
 
Johan

On 14 Jul 2017, at 14:58, Mariano Martinez Peck <[hidden email]> wrote:

Hi Johan,

Thanks for your effort. Let me ask, what is the status of https://github.com/SeasideSt/Seaside/pull/931 ?
I mean...it was merged but it wasn;'t included in 3.2.4..was that on purpose?

Thanks

On Fri, Jul 14, 2017 at 6:19 AM, Johan Brichau <[hidden email]> wrote:
Hi all,

Seaside 3.2.4 fixes an important bug [1][2]. 
If you are on 3.2.x, you want to upgrade.

cheers
Johan



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--



--

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

Johan Brichau-2

On 14 Jul 2017, at 19:36, Mariano Martinez Peck <[hidden email]> wrote:

In summary, if you can update the tag 3.2.4 to take the latest master commit (which should include 931) , I would really appreciate that.

Done!

cheers
Johan

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

Mariano Martinez Peck


On Fri, Jul 14, 2017 at 3:11 PM, Johan Brichau <[hidden email]> wrote:

On 14 Jul 2017, at 19:36, Mariano Martinez Peck <[hidden email]> wrote:

In summary, if you can update the tag 3.2.4 to take the latest master commit (which should include 931) , I would really appreciate that.

Done!



Awesome!!!!   That's perfect now. Thank you VERY MUCH!

 
cheers
Johan

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
bpi
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

bpi
In reply to this post by Johan Brichau-2
Hi all,

I just loaded Seaside in a new Pharo image I created using get.pharo.org. (Pharo 6.0, Latest update: #60535)

Then I used the script to install Seaside from https://github.com/SeasideSt/Seaside to install it directly from GitHub:
Metacello new
        baseline:'Seaside3';
        repository: 'github://SeasideSt/Seaside:master/repository';
        load

I had expected that I would get the latest released version 3.2.4. However, GRPlatform current seasideVersion greaseString answers 3.2.2.

What is the reason for that? Did I forget something?

Bernhard

> Am 14.07.2017 um 11:19 schrieb Johan Brichau <[hidden email]>:
>
> Hi all,
>
> Seaside 3.2.4 fixes an important bug [1][2].
> If you are on 3.2.x, you want to upgrade.
>
> cheers
> Johan
>
> [1] https://github.com/SeasideSt/Seaside/issues/932
> [2] https://github.com/SeasideSt/Seaside/issues/909
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
bpi
Reply | Threaded
Open this post in threaded view
|

Re: Seaside 3.2.4 bugfix release available

bpi
Hi all,

I tried installing the other install script which uses configurations from SmalltalkHub.

Metacello new
 configuration:'Seaside3';
 repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
 version: '3.2.4';
 load.

"GRPlatform current seasideVersion greaseString" still evaluates to 3.2.2.

How can I find out reliably which version I have?

When I browse ConfigurationOfSeaside3 I see that the stable version is already at 3.2.5. However, there is no release tag on https://github.com/SeasideSt/Seaside/releases.

Bernhard

> Am 25.02.2018 um 15:02 schrieb Bernhard Pieber <[hidden email]>:
>
> Hi all,
>
> I just loaded Seaside in a new Pharo image I created using get.pharo.org. (Pharo 6.0, Latest update: #60535)
>
> Then I used the script to install Seaside from https://github.com/SeasideSt/Seaside to install it directly from GitHub:
> Metacello new
> baseline:'Seaside3';
> repository: 'github://SeasideSt/Seaside:master/repository';
> load
>
> I had expected that I would get the latest released version 3.2.4. However, GRPlatform current seasideVersion greaseString answers 3.2.2.
>
> What is the reason for that? Did I forget something?
>
> Bernhard
>
>> Am 14.07.2017 um 11:19 schrieb Johan Brichau <[hidden email]>:
>>
>> Hi all,
>>
>> Seaside 3.2.4 fixes an important bug [1][2].
>> If you are on 3.2.x, you want to upgrade.
>>
>> cheers
>> Johan
>>
>> [1] https://github.com/SeasideSt/Seaside/issues/932
>> [2] https://github.com/SeasideSt/Seaside/issues/909

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside