Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Tudor Girba

Hi everyone (and in particular Stef), I would just like to thank you for the repackaging effort! This is a really important topic that we needed to advance since a long time. Besides being beneficial for Moose, I am also sure that this effort will have ripple effects in the whole Pharo ecosystem. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years, 9 months

Release process for Moose components and subcomponents

by stepharo

Hi I really think that - everybody should use versionner :) because now that I use it it is really nice. - we should use baseline for development during development - we should use stable or versionned for external packages such as XML. - with versionner we can release at the end of every week or two in probably some clicks. (I can ask christophe for some improvements). So can we agree on that because we can make sure that we have the advantges that now and have at the end of every week a versionned released? Stef

10 years, 9 months

Re: [Pharo-dev] Versioner

by Diego Lont

Hi Christophe, > Hi Diego, > > Le 30 juin 2014 à 09:23, Diego Lont a écrit : > >> I am very happy that versioner is being built. We need more and better software configuration tools, and versioner will make our life easier. That being said, I am getting a bit nervous about how versioner is released. It should aim to improve the way people can work, and not to create a single workflow for all people working on pharo projects. I hope my fears are unfounded. > > You're right, Versionner enforces a single workflow. We tried to do a simple tool that can fit most people and very easy to use. Versionner is far from perfect but allows to easily manage project dependencies and release for a "classical" workflow. There are also some known limitations (e.g., no support of platform-specific sections). > Versionner does not aim that ALL people use a single workfow but tries to provide guidelines. If one needs another workflow, it is possible by using Metacello directly. If needed, we can also add features to Versionner. It may be done from feedbacks. > To summarize, it is not "One Ring to rule them all" but rather one tool to fit more needs and make configuration management easy. That is exactly my point. But Stef currently tries to enforce this workflow of working to Moose. And since this workflow will not work well for Moose (because of the demands on the process), I object to this. >> Within the Pharo community we have at least 3 different workflows: >> A. For Pharo core, we have a pharo inbox, where suggested fixes for reported bugs are put. These fixes are reviewed and, if accepted, integrated into Pharo. This ensures that the changes in Pharo hold (most of the time) to quite some quality standards. > It is the same workflow that GitHub favors: you fork the code, do your changes and provide a pull request that will be accepted or not. It works quite well. >> B. For the “cross-platform” projects (Grease, Seaside, Magritte, etc.) all suggested fixes are put in the main repository on smalltalkhub. The fixes are, after review and tests, released by putting them in a “released” version of the configuration. Since not all fixes should be in all versions, and sometimes only concern a certain platform, the process for Pharo core would not work: releasing fixes are more complex because of the cross-platform issues. > I don't see your point here. What is really different except that you don't have an inbox (some kind of dedicated branch)? Instead, you publish in the same repository, creating new branches. >> C. For the “moose” projects all suggested fixes are put in the main repository and are accepted by default. Since most projects evolve very fast, quality assurance is done afterwards, by submitting bug fixes. > Here, there is no review, ok. Your response shows that I have not made my point well. I wanted to point out that we need different workflows because of the different demands. A workflow is more than only a tool, but starts with people building something and ends with people using something. And you point out that versioner has one workflow implemented, and therefor will not be applicable to all projects. A. For pharo core all projects are included in pharo. The number of external influences (VM, plugins) is very limited. It works here to have no configuration at all, since there is only 1 release-branch: the current one. And since the file server creates a version of each build, we can always go back to a specific build. Quality is very important to pharo as a lot of users depend on a good working pharo. B. For the “cross-platform” projects this workflow is not sufficient, because there are much more external influences. So here we use the configurations to manage the releases. And the complexity of the configuration of Seaside shows this is a very complex thing to do. This complexity is not from Metacello. Metacello allows us to do a decent job here for the supported platforms. For the unsupported platforms there is some additional manual work involved, with all risks to this. The complexity here stems from the Software Configuration challenges Seaside faces. A simple inbox won’t do the job for us. Quality here is also very important as a lot of users depend on a good working Seaside. Also there are more demands on reproducibility, as there are quite some systems depending on Seaside that should function 24/7. C. For the “moose” projects, we have a few advantages above the cross-platform projects, and a few disadvantages: + Moose only needs to work for pharo. So we can cut out a lot of platform specific junk. Some projects are suited for multiple platforms, but not for the amount of platform Seaside should work on. + There are far less projects depending on Moose. Most of them are integrated, so tests will automatically be fired. And the projects that do depend on Moose usually do not have run 24/7. - Moose depends on more projects then Seaside. To create an exact version is therefor much harder. - A large part of the Moose bugs comes from the change rate of the projects Moose depends on. Pharo has a very drastic strategy to improve its architecture. This causes quite some maintenance work. So that there is no review is not the point. The point is that because of these different demands we need to accept a lower quality standard for moose. This lower quality standard is maybe undesirable, but is not easily improved. Having no review is a consequence of this, not the cause. If we want to improve this quality standard, better SCM tools will not suffice. On the other hand, this lower quality standard has so far worked for Moose, as there are less people who depend on Moose. Regards, Diego

10 years, 10 months

GraphET2

by stepharo

Hi stable and development points to the same. Then I do not see why GraphET requires RoassalPdfExporter2 and Neo. Again this configuration looks to me like a way to load everything. I think that I will really try another way to manage Moose because I start to think that it goes nowhere. This is like the XMLSupport that loaded the clients like SIXX of XML. I did XMLParser and XMLWriter and this is much much nicer, smaller, less complex. Stef

10 years, 10 months

Versioner

by Diego Lont

I am afraid this mail is going to be too long, but I feel it needs to be written. I will start with the conclusion, so you can skip the mail if you feel it does not interest you. Please keep the discussion on the Moose list, as there the discussion was started. I am very happy that versioner is being built. We need more and better software configuration tools, and versioner will make our life easier. That being said, I am getting a bit nervous about how versioner is released. It should aim to improve the way people can work, and not to create a single workflow for all people working on pharo projects. I hope my fears are unfounded. Software configuration management (SCM) is in my opinion an undervalued topic within the software world. One cannot find very many good books on them, and I am afraid this lack of knowledge shows in the way people go around with their SCM. So I would like to write down some observations of the SCM processes in Pharo that I believe we should keep in mind. The main target of SCM is to keep the impact of changes as minimal as possible. Good SCM allows all people working on a certain project, to make their changes, without causing trouble for other project members and people using this project. Open source projects are (in SCM terms) rather complex, as they involve a lot of people, including some people we do not know. 1. One of the best things of Metacello is that it does not require you to follow a certain workflow. It is very flexible and supports a large range of possible workflows. Within the Pharo community we have at least 3 different workflows: A. For Pharo core, we have a pharo inbox, where suggested fixes for reported bugs are put. These fixes are reviewed and, if accepted, integrated into Pharo. This ensures that the changes in Pharo hold (most of the time) to quite some quality standards. B. For the “cross-platform” projects (Grease, Seaside, Magritte, etc.) all suggested fixes are put in the main repository on smalltalkhub. The fixes are, after review and tests, released by putting them in a “released” version of the configuration. Since not all fixes should be in all versions, and sometimes only concern a certain platform, the process for Pharo core would not work: releasing fixes are more complex because of the cross-platform issues. C. For the “moose” projects all suggested fixes are put in the main repository and are accepted by default. Since most projects evolve very fast, quality assurance is done afterwards, by submitting bug fixes. I can say a lot about why I believe these workflows are appropriate for their different projects, but the point I am trying to make here, is that these workflows have come to existence because of the different demands on them. And to stress my point about the flexibility (thank you Dale): When there was a problem with the workflow in the cross platform projects, I could find a solution (using releases) that Metacello supported. 2. Unfortunately Metacello does not have a good UI. And for large configurations like Seaside, it is a lot of work to keep them maintained. I dream of a tool that acts as a UI for Metacello: this tool is flexible as Metacello, while making the simple things real easy (hitting a button and done). Does versioner aim to do this? 3. I always get very nervous when someone says: They do it like this, and that works very well for them. So we should do that too. I do not believe that is always a good idea. The conclusion should be a question: Can we use that too? And now I cannot find the mail about the java SCM practice, but I do not think we can apply it to all our processes ... 4. Modularity is very important. Also for performing good SCM. And yes, we lack sufficient modularity in Moose. It should be better. I.e. because of the lack of modularity, it is sometimes hard to distinguish between where the change needs to be put in. So there is no clear group to point out who should accept the changes. So this is also an SCM problem. Cleaning up the configuration will help here very much. Thank you Steff for the good work here. And maybe you also have a point that the people working on Moose should have more focus on keeping things modular, because it makes the system better maintainable in a lot of ways. 5. Forking things will only make SCM worse, as it adds a complexity. So I very much hope we can come to an agreement how the process works, without resorting to drastic measures. Regards, Diego

10 years, 10 months

why gt is here to stay

by Tudor Girba

Hi, At this moment, GT primarily means: - Playground - Inspector - Debugger (Metaceller was never a subject to debate, so I will not address it here) The Coder will likely follow but first in a different format than one expects. Namely, it will appear first as a code editor inside the inspector. GT is neither a whim, nor is it experimental. GT is a long term project. For example, the inspector was incubated for more than 4 years, and it is time to work with it and evolve it based on real-life experience. It is true that sometimes it is still moving but that is because it is alive :). Yet, the functionality is there, and if there are issues they should be treated as such: report them and they will be fixed. Now, the main reason why GT is not optional for the main Moose distribution is that, as I explained one year ago at the MooseDay, Moose will provide the IDE. First, we need a new IDE in Pharo and I think we have cool set of concepts and the Moose engines are perfect for it. Second, when analyzing data from XML structures, plain files, DB, or even Pharo objects, the Inspector is cornerstone. And so is the Playground. As for the Debugger, I will remind you that it comes with working dedicated debuggers for PetitParser, Glamour, and Announcements. These alone make it worth the effort when developing Moose-based solutions. Not to mention that we are building something that is ridiculously small for the power it harnesses. We should not stop this because we find a couple of bugs along the way. For all these reasons, GT is here to stay. Cheers, Doru p.s. Btw, the development of GT is not reserved to a closed circle. We would like to invite anyone interested in participating in the development of GT. p.p.s. Of course, because this system is properly engineered, it can be safely replaced by the default tools: EyeInspector registerToolsOn: Smalltalk tools. SpecDebugger registerToolsOn: Smalltalk tools. Workspace registerToolsOn: Smalltalk tools. -- www.tudorgirba.com "Every thing has its own flow"

10 years, 10 months

Re: Release process for Moose components and subcomponents

by Stephan Eggermont

Versioner cannot currently be used to make the switch from Pharo 3 to Pharo 4. It also cannot be used to maintain Moose versions for both. If you want to be able to maintain versions delivered to customers, you'll need the platform support and need to be able to DRY configurations. The delivered configuration is unlikely to load in a current Pharo image, so it needs a dependency on a ConfigurationOfPharo version Stephan

10 years, 10 months

Re: Release process for Moose components and subcomponents

by Stephan Eggermont

Steph wrote >I was discussing with christophe and > - for external projects that we do not control we could also fork >and maintain our own configuration. That is madness for maintained projects. You might need a snapshot, but don't want to do the work to maintain a configuration. Stephan

10 years, 10 months

RoassalPdfExporter2

by stepharo

hi alex the baseline is wrong because it does not depend on roassal. Then there is again this FuelMetalevel version that is around. development should be better a baseline than this development: spec "By convention the development branch should point to a fixed version that is regularly updated and might contain unstable code. The name used by Metacello is only defined by the following pragma:" <symbolicVersion: #development > "For the development tag refer to a fixed version which you update if you commit new code. Note that you can refer here to any other version name from this configuration" spec for: #'common' version: 'dev'. I can fix it if you give me access.... Stef

10 years, 10 months

Is GLMRoassalEasel correctly packaged?

by stepharo

Hi doru Is GLMRoassalEasel correctly packaged because Glamour-Tools just requires Glamour-Core and I have the impression that GLM-RoassalEasel should be in Glamour-Roassal something. Stef

10 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev