Smalltalk › Frameworks & Tools › Seaside › Seaside Development

Grease and Seaside github primary codebase?

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 6 messages Options
Johan Brichau-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Grease and Seaside github primary codebase?

Johan Brichau-2
Hi guys,

We have been using the Smalltalkhub repository as the primary repository until now.
The most recent version of Grease (1.3.0) is only on github at this time.

However, I would prefer using the github repos as the main repositories because it supports branching a lot better than MC and it offers the ability for people to fork their own version and pull their changes back in a ‘controlled’ way (i.e. reviewed pull requests).

The work on git for Pharo (Iceberg) is advancing very well. Although not entirely stable at this time, everybody can already use git repos for smalltalk by means of the filetree format in MC.
We have also been using git repos for Smalltalk in the GemStone/S universe for years now.

Once we start using git for development, we can still copy the packages back to an MC repository, although that’s something I would want to avoid as well.
I would simply update the ConfigurationOf and have it refer to the github repos for the new versions on the latest platform versions.

What do you all think?

cheers
Johan
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Max Leske
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Grease and Seaside github primary codebase?

Max Leske

> On 26 May 2017, at 09:29, Johan Brichau <[hidden email]> wrote:
>
> Hi guys,
>
> We have been using the Smalltalkhub repository as the primary repository until now.
> The most recent version of Grease (1.3.0) is only on github at this time.
>
> However, I would prefer using the github repos as the main repositories because it supports branching a lot better than MC and it offers the ability for people to fork their own version and pull their changes back in a ‘controlled’ way (i.e. reviewed pull requests).
>
> The work on git for Pharo (Iceberg) is advancing very well. Although not entirely stable at this time, everybody can already use git repos for smalltalk by means of the filetree format in MC.
> We have also been using git repos for Smalltalk in the GemStone/S universe for years now.
>
> Once we start using git for development, we can still copy the packages back to an MC repository, although that’s something I would want to avoid as well.
> I would simply update the ConfigurationOf and have it refer to the github repos for the new versions on the latest platform versions.
>
> What do you all think?

I fully agree.

>
> cheers
> Johan
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

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

Re: Grease and Seaside github primary codebase?

CyrilFerlicot
In reply to this post by Johan Brichau-2
Le 26/05/2017 à 09:29, Johan Brichau a écrit :

> Hi guys,
>
> We have been using the Smalltalkhub repository as the primary repository until now.
> The most recent version of Grease (1.3.0) is only on github at this time.
>
> However, I would prefer using the github repos as the main repositories because it supports branching a lot better than MC and it offers the ability for people to fork their own version and pull their changes back in a ‘controlled’ way (i.e. reviewed pull requests).
>
> The work on git for Pharo (Iceberg) is advancing very well. Although not entirely stable at this time, everybody can already use git repos for smalltalk by means of the filetree format in MC.
> We have also been using git repos for Smalltalk in the GemStone/S universe for years now.
>
> Once we start using git for development, we can still copy the packages back to an MC repository, although that’s something I would want to avoid as well.
> I would simply update the ConfigurationOf and have it refer to the github repos for the new versions on the latest platform versions.
>
> What do you all think?
>
I totally agree too!

> cheers
> Johan
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>


--
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France


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

signature.asc (836 bytes) Download Attachment
Philippe Marschall
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Grease and Seaside github primary codebase?

Philippe Marschall
In reply to this post by Johan Brichau-2
On Fri, May 26, 2017 at 9:29 AM, Johan Brichau <[hidden email]> wrote:

> Hi guys,
>
> We have been using the Smalltalkhub repository as the primary repository until now.
> The most recent version of Grease (1.3.0) is only on github at this time.
>
> However, I would prefer using the github repos as the main repositories because it supports branching a lot better than MC and it offers the ability for people to fork their own version and pull their changes back in a ‘controlled’ way (i.e. reviewed pull requests).
>
> The work on git for Pharo (Iceberg) is advancing very well. Although not entirely stable at this time, everybody can already use git repos for smalltalk by means of the filetree format in MC.
> We have also been using git repos for Smalltalk in the GemStone/S universe for years now.
>
> Once we start using git for development, we can still copy the packages back to an MC repository, although that’s something I would want to avoid as well.
> I would simply update the ConfigurationOf and have it refer to the github repos for the new versions on the latest platform versions.
>
> What do you all think?

I agree, the configurations are a pain. It would be cool if there was
a short tutorial for noobs like me on how to check out and commit.

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Johan Brichau-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Grease and Seaside github primary codebase?

Johan Brichau-2

On 28 May 2017, at 11:56, Philippe Marschall <[hidden email]> wrote:

I agree, the configurations are a pain. It would be cool if there was
a short tutorial for noobs like me on how to check out and commit.

Hey Philippe,

It would be good to know what questions you still have after reading the links I posted in the first paragraphs here: [1] 
I can the complete [2] with more info following your questions. 

Would that work?

I’m currently also trying to use Iceberg on Pharo 6. It’s still unstable but will solve many of the inconveniences we have working with git filetree.


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

Re: Grease and Seaside github primary codebase?

Philippe Marschall
On Sun, Jun 4, 2017 at 10:25 AM, Johan Brichau <[hidden email]> wrote:

>
> On 28 May 2017, at 11:56, Philippe Marschall <[hidden email]>
> wrote:
>
> I agree, the configurations are a pain. It would be cool if there was
> a short tutorial for noobs like me on how to check out and commit.
>
>
> Hey Philippe,
>
> It would be good to know what questions you still have after reading the
> links I posted in the first paragraphs here: [1]
> I can the complete [2] with more info following your questions.
>
> Would that work?
>
> I’m currently also trying to use Iceberg on Pharo 6. It’s still unstable but
> will solve many of the inconveniences we have working with git filetree.

You're currently working with Pharo 5, the Git merge driver and filetree?

What I'm missing somehow right now is a guide on how to get started. Eg

- Pharo 5, filetree and the merge driver. With links to the pages and doits.
- Clone the GitHub repo (I assume)
- Set up the Monticello repositories based on the GitHub checkouts.
This is probably a doit involving Metacello.

And then the commit, I assume something like this:
- git checkout -b
- save the Monticello repositories
- git add
- git commit
- git push
- open PR

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Free forum by Nabble Edit this page