seaside-dev August 2016

seaside-dev@lists.squeakfoundation.org

3 participants
20 discussions

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub
by Torsten Bergmann 16 Jul '18

16 Jul '18

Hi, The bundling with magritte polluted the repo and the Bootstrap project with stuff that was not really needed for "Seaside + Bootstrap" only. Also a "Bootstrap-Demo" package appeared that was more a demo for magritte than for Bootstrap. Since there already was an "Bootstrap-Examples" package this added more confusion (at least on my side). I now took action and cleaned up the Bootstrap project again to remove the magritte stuff. If one wants to to use Bootstrap with Seaside he does not necessarily have to go the Magritte path, so IMHO this was necessary. The magritte stuff for Bootstrap is now hosted as an own separate project on STHub which would also help to see to which part code additions really belong. As a result: ============ 1. The Bootstrap project now again only contains and loads the initial three packages: - Bootstrap-Core - Bootstrap-Tests-Core - Bootstrap-Examples assembled by the known ConfigurationOfBootstrap 2. The Magritte support on top of Bootstrap is now separated in an own project to avoid too much mixin. See "BootstrapMagritte" on SmalltalkHub. The new repo "http://smalltalkhub.com/#!/~TorstenBergmann/BootstrapMagritte" has the same commiters as the old one, so feel free to continue with your work. This project includes two packages: - Bootstrap-Magritte-Core (former Bootstrap-Magritte) - Bootstrap-Magritte-Examples (former Bootstrap-Demo) assembled by a new ConfigurationOfBootstrapMagritte for this particular project 3. The Bootstrap/ConfigurationOfBootstrap is now available as - a release version 0.4.0 for Seaside 3.0.9 - a release version 0.5.0 for Seaside 3.0.10 - a release version 0.6.0 for Seaside 3.1.0 (#stable) - a development version 0.7.0 for Seaside 3.1.0 for new stuff 4. The CI for Bootstrap is green for Pharo 2.0 and now also Pharo 3.0 5. The config browser is updated for Pharo 2.0 and Pharo 3.0 with the "Bootstrap" package So you can now also open a fresh Pharo 3.0 image, open World menu -> Configuration Browser to load "Bootstrap". Then run ZnZincServerAdaptor startOn: 8080 and start coding your web application with the latest Seaside 3.1.0. Next steps: Setting up a CI for the new project "BootstrapMagritte"/ConfigurationOfBootstrapMagritte Have fun! Bye Torsten

3 7

Jenkins build became unstable: Seaside » 50,bleedingEdge,vm #826
by ci-pharo-contribution＠inria.fr 02 Sep '16

02 Sep '16

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=50,VERSION=bleedin…>

1 1

Jenkins build became unstable: Seaside » 40,bleedingEdge,vm #826
by ci-pharo-contribution＠inria.fr 02 Sep '16

02 Sep '16

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=40,VERSION=bleedin…>

1 1

Jenkins build became unstable: Seaside » 30,bleedingEdge,vm #826
by ci-pharo-contribution＠inria.fr 02 Sep '16

02 Sep '16

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=30,VERSION=bleedin…>

1 1

Jenkins build became unstable: Grease » 40,bleedingEdge,vm #543
by ci-pharo-contribution＠inria.fr 25 Aug '16

25 Aug '16

See <https://ci.inria.fr/pharo-contribution/job/Grease/PHARO=40,VERSION=bleeding…>

1 2

Jenkins build became unstable: Grease » 50,bleedingEdge,vm #543
by ci-pharo-contribution＠inria.fr 25 Aug '16

25 Aug '16

See <https://ci.inria.fr/pharo-contribution/job/Grease/PHARO=50,VERSION=bleeding…>

1 2

Jenkins build became unstable: Grease » 20,bleedingEdge,vm #543
by ci-pharo-contribution＠inria.fr 25 Aug '16

25 Aug '16

See <https://ci.inria.fr/pharo-contribution/job/Grease/PHARO=20,VERSION=bleeding…>

1 2

Jenkins build became unstable: Grease » 30,bleedingEdge,vm #543
by ci-pharo-contribution＠inria.fr 25 Aug '16

25 Aug '16

See <https://ci.inria.fr/pharo-contribution/job/Grease/PHARO=30,VERSION=bleeding…>

1 2

Release 3.2.0
by Johan Brichau 23 Aug '16

23 Aug '16

Hi Philippe, Dale, Stephan, Esteban and other contributors, I propose to release 3.2.0 as it is right now [1]. What do you think? Anything missing? The new website and reworking Seaside Welcome + Config can be postponed. Though the new website is the next thing on my stack. At the same time, I want to propose that the github repository becomes the main repository. I’ve been setting up Grease and Seaside on github with the SmalltalkCI and it’s very nice to have that test coverage on all platforms [2]. It also means we can have a more organised way of contributions via pull requests and feature branches. Any opinions? Perhaps I should write up a small page on how contributing would work (technically) for those who are not into Smalltalk+Git cheers Johan [1] https://ci.inria.fr/pharo-contribution/job/Seaside/ <https://ci.inria.fr/pharo-contribution/job/Seaside/> [2] https://travis-ci.org/SeasideSt/Seaside/builds <https://travis-ci.org/SeasideSt/Seaside/builds>

3 7

Jenkins build became unstable: Seaside » 50,bleedingEdge,vm #816
by ci-pharo-contribution＠inria.fr 22 Aug '16

22 Aug '16

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=50,VERSION=bleedin…>

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev August 2016