If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2022-03-08
What do you think..? Have you installed our current iteration..?
I have watched several reviews of our efforts, during the rebirth of PeppermintOS, when we launched on the 2nd February 2022. They have ranged from disrespectful, unfounded to warmly received and highly thought of by the reviewer.
It depends on what you expect from a distro or is brand loyalty that sacrosanct.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the record PeppermintOS has never used the words "Rolling Release" regarding our Debian based distro. That is purely from and propagated by some of the community.
👍
2
Last edit: MintSpider - Peter Paterson 2022-03-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem they are sticking on: Peppermint has migrated into its own continuous delivery OS based on the Debian Bullseye repositories. Giving you the option to pull from testing if you like and we believe this will appeal to new and experienced Linux users.
So... let's break it down... *Peppermint has migrated into its own continuous delivery OS based on the Debian Bullseye repositories. *
We do use the DevOps culture and the CI/CD pipelines for our development process it is a very common practice used today. In many cases for many teams that has turned into DevSecOps
DevOps automation and CI/CD are major components of many different application development cultures and they greatly enhance this process, giving advantages to both the software development team members and the community. Many organizations implement these processes today... Let’s take a closer look at the advantages of DevOps automation and CI/CD.
Helps catch problems
CI/CD pipelines enable the integration of smaller clusters of code, which makes it easier to deal with the possible problems that always occur in code. These smaller parts can be tested right after they are merged into the code repository. We in essence can write and reuse unit tests, This allows the team to catch and work on an issue right away. Finally, using CI/CD pipelines helps with identification of (bugs). That’s a great solution for huge teams that's why large companies use CI/CD, but it is also a great tool-set for those of us who volunteer and work remotely which is all of the Peppermint team around the world, when the communication between the team members can be delayed at times.
Faster release rates
If issues are caught earlier, they are fixed faster. It ensures faster release times on condition that the developers continuously create the code which we do for specific tools. In other words, CI/CD pipelines provide for the consistent code integration and deployment, getting the code ready for release. With the potential to speed up the development process, via the automated delivery pipelines, We do this using our own CD pipeline and working with Woodpecker CI so that we can run our pipelines in Docker Containers.
Automated delivery pipelines as I mentioned above we built this already, gives fewer errors and when they do occur, we can find them quickly. This means that the developer and community contributors don't have to make so many changes in the code so that they can focus on developing and innovation.
Continuous integration
This is the method that lets us automate integration of any changes in code from different developers of the team and community. In essence, continuous integration ensures the code quality and includes code analysis, compilation, code packaging, and unit testing. WoodPecker helps us containerize our pipelines so that we can run the code and ensure it of good quality before it reaches the git repos.
Continuous delivery
This approach provides us with frequent and fast production release. Nobody is manually uploading production code to the production CodeBerg repos it happens after the code has been tested.......... after it is committed we use continuous delivery so that we can release at any time. That is why there are no versions or point releases for peppermint that information is stored in the git repo history.... Continuous delivery, lets us set the release frequency, for example, we can do daily or weekly on any of the code base.
Continuous delivery enables quick releases. See...... the automation is the core principle of continuous delivery and it helps to effectively automate releases. We have built our own tool set to do this. Even down to the ISO deployment. We release when we want as we need to...
So,... Yes we have migrated from a single waterfall development practice to a DevOps CI/CD process and culture
We are based on Debian
Yes we are and no we do not change any of that code at all. apt update / upgrade will do what they always do, no more no less
Yes----- Peppermint has migrated into its own continuous delivery OS based on the Debian Bullseye repositories
The other dig is this: Giving you the option to pull from testing if you like and we believe this will appeal to new and experienced Linux users
Yes - we do pin the unstable repo, yes we do....users have the choice to use the pinned repo or not.
Yes - we do think it will appeal to all users both new and experienced
Its all choice at the end of the day... providing choice is the value.
**@H. J. Villalobos, **
I hope this answers your question as well as the info that @mintspider linked to
If you do have more questions please do send them our way....transparency is always the best approach.
👍
3
Last edit: Peppermint OS 2022-03-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the excellent explanation. Superb. I think this needs to be on your main web-page. Maybe not all of this but a summary that is detailed enough so it is more understandable to an end-user. Finally, from my end anyway, there should be a release number to sync up with the Debian release number so everyone is on the same page (Peppermint 11?). Just a thought. Thanks for leaning forward to provide the details that make Peppermint what it is. This goes a long way. Peppermint needs to prosper. Best regards...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmm.... lets see.....thinking how to explain this..... we never intend to "officially release" a new PeppermintOS.
What I mean by this is.....with the live-build tools its really a moot point from the base level.
Even when Debian 12 does come out ..... we don't care..... we just adjust the live-build tools then spin the ISO. We don't add any value to the core OS code...
This is why we can have a 32 bit(still in testing) / 64 bit ISO.
It is also why we can spin an ISO of devuan...for non-systemd
What we do care about is that the tools we build work in all those base OS's.....
we need things like
* pyqt
* tkinter
* sqlite
* tkinterbootstrap
* pygit
* calamares
and on....
Tools that we use to build things are ongoing as long as they work on Debian and Devuan we will continuously keep developing and innovating upon those things regardless of the versions of the base OS..
So....from a logical perspective it make more sense to maintain a builddate (some call it a changelog) file, that keeps a running history of what changes in the ISO
This is why having a version Peppermint 11, 12 etc... does not make sense in our pipeline
I hope that helps do let us know if you have more questions
👍
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the explanation of the terms CI/CD and "continuous delivery." Now that I understand that CI/CD is a development model and does not really affect users, I can see the benefit of using the terminology. If the Peppermint components are being developed and pushed out via CI/CD pipelines, then that can be easily explained on the website. Using the term continuous delivery is very confusing to users who are unfamiliar with the development model and its implications, as I was uniformed. Thanks again for the explanation.
👍
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How many 'f' and 's' words does one need to make a point?
It made my toes curl.
Enough said.
Off topic:
Me thinks that Peppermintos is a step up from Devuan itself,
the -default- desktop is much more pleasant to the eyes.
To name but one thing.
Kind regards,
Edward
❤️
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
LPE - Thanks! yeah they were piling on back then ..... I could not really fully understand why...we were and still are trying to keep the project alive....that is a good thing...LOL
None the less thanks for the kind words
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Peppermint needs to address a few issues here. Just acknowledge it and correct it and then move on. We all want Peppermint to succeed.
TRG - TheRealGeek
Peppermint OS RANT - Are thy lying to you
https://youtu.be/7JN57toaSG8
eznix
Peppermint OS Linux - Continuous Delivery ≠ Rolling Release
https://youtu.be/DRJ82kq3cMA
Last edit: MintSpider - Peter Paterson 2022-03-08
What do you think..? Have you installed our current iteration..?
I have watched several reviews of our efforts, during the rebirth of PeppermintOS, when we launched on the 2nd February 2022. They have ranged from disrespectful, unfounded to warmly received and highly thought of by the reviewer.
It depends on what you expect from a distro or is brand loyalty that sacrosanct.
H. J. Villalobos, I added in some details of each YouTube video, so that members will know what they are about to click on and open.
Every YouTube content maker has the total right to make their own opinions known.
PeppermintOS's development plans have been announced quite clearly in this forum:
**
PeppermintOS Development Process **
https://sourceforge.net/p/peppermintos/pepos/announcements/thread/aebf8f4131/
For the record PeppermintOS has never used the words "Rolling Release" regarding our Debian based distro. That is purely from and propagated by some of the community.
Last edit: MintSpider - Peter Paterson 2022-03-08
That's good feedback and it helps provide context. Thank you!
The problem they are sticking on:
Peppermint has migrated into its own continuous delivery OS based on the Debian Bullseye repositories. Giving you the option to pull from testing if you like and we believe this will appeal to new and experienced Linux users.
So... let's break it down...
*Peppermint has migrated into its own continuous delivery OS based on the Debian Bullseye repositories. *
We do use the DevOps culture and the CI/CD pipelines for our development process it is a very common practice used today. In many cases for many teams that has turned into DevSecOps
DevOps automation and CI/CD are major components of many different application development cultures and they greatly enhance this process, giving advantages to both the software development team members and the community. Many organizations implement these processes today... Let’s take a closer look at the advantages of DevOps automation and CI/CD.
Helps catch problems
CI/CD pipelines enable the integration of smaller clusters of code, which makes it easier to deal with the possible problems that always occur in code. These smaller parts can be tested right after they are merged into the code repository. We in essence can write and reuse unit tests, This allows the team to catch and work on an issue right away. Finally, using CI/CD pipelines helps with identification of (bugs). That’s a great solution for huge teams that's why large companies use CI/CD, but it is also a great tool-set for those of us who volunteer and work remotely which is all of the Peppermint team around the world, when the communication between the team members can be delayed at times.
Faster release rates
If issues are caught earlier, they are fixed faster. It ensures faster release times on condition that the developers continuously create the code which we do for specific tools. In other words, CI/CD pipelines provide for the consistent code integration and deployment, getting the code ready for release. With the potential to speed up the development process, via the automated delivery pipelines, We do this using our own CD pipeline and working with Woodpecker CI so that we can run our pipelines in Docker Containers.
Automated delivery pipelines as I mentioned above we built this already, gives fewer errors and when they do occur, we can find them quickly. This means that the developer and community contributors don't have to make so many changes in the code so that they can focus on developing and innovation.
Continuous integration
This is the method that lets us automate integration of any changes in code from different developers of the team and community. In essence, continuous integration ensures the code quality and includes code analysis, compilation, code packaging, and unit testing. WoodPecker helps us containerize our pipelines so that we can run the code and ensure it of good quality before it reaches the git repos.
Continuous delivery
This approach provides us with frequent and fast production release. Nobody is manually uploading production code to the production CodeBerg repos it happens after the code has been tested.......... after it is committed we use continuous delivery so that we can release at any time. That is why there are no versions or point releases for peppermint that information is stored in the git repo history.... Continuous delivery, lets us set the release frequency, for example, we can do daily or weekly on any of the code base.
Continuous delivery enables quick releases. See...... the automation is the core principle of continuous delivery and it helps to effectively automate releases. We have built our own tool set to do this. Even down to the ISO deployment. We release when we want as we need to...
So,... Yes we have migrated from a single waterfall development practice to a DevOps CI/CD process and culture
We are based on Debian
Yes we are and no we do not change any of that code at all. apt update / upgrade will do what they always do, no more no less
Yes----- Peppermint has migrated into its own continuous delivery OS based on the Debian Bullseye repositories
The other dig is this:
Giving you the option to pull from testing if you like and we believe this will appeal to new and experienced Linux users
Yes - we do pin the unstable repo, yes we do....users have the choice to use the pinned repo or not.
Yes - we do think it will appeal to all users both new and experienced
Its all choice at the end of the day... providing choice is the value.
**@H. J. Villalobos, **
I hope this answers your question as well as the info that @mintspider linked to
If you do have more questions please do send them our way....transparency is always the best approach.
Last edit: Peppermint OS 2022-03-09
Thank you for the excellent explanation. Superb. I think this needs to be on your main web-page. Maybe not all of this but a summary that is detailed enough so it is more understandable to an end-user. Finally, from my end anyway, there should be a release number to sync up with the Debian release number so everyone is on the same page (Peppermint 11?). Just a thought. Thanks for leaning forward to provide the details that make Peppermint what it is. This goes a long way. Peppermint needs to prosper. Best regards...
Hmmm.... lets see.....thinking how to explain this..... we never intend to "officially release" a new PeppermintOS.
What I mean by this is.....with the live-build tools its really a moot point from the base level.
Even when Debian 12 does come out ..... we don't care..... we just adjust the live-build tools then spin the ISO. We don't add any value to the core OS code...
This is why we can have a 32 bit(still in testing) / 64 bit ISO.
It is also why we can spin an ISO of devuan...for non-systemd
What we do care about is that the tools we build work in all those base OS's.....
we need things like
* pyqt
* tkinter
* sqlite
* tkinterbootstrap
* pygit
* calamares
and on....
Tools that we use to build things are ongoing as long as they work on Debian and Devuan we will continuously keep developing and innovating upon those things regardless of the versions of the base OS..
So....from a logical perspective it make more sense to maintain a builddate (some call it a changelog) file, that keeps a running history of what changes in the ISO
This is why having a version Peppermint 11, 12 etc... does not make sense in our pipeline
I hope that helps do let us know if you have more questions
Thanks for explaining. I disabled the unstable repo and the source repo's too.
Thank you for the explanation of the terms CI/CD and "continuous delivery." Now that I understand that CI/CD is a development model and does not really affect users, I can see the benefit of using the terminology. If the Peppermint components are being developed and pushed out via CI/CD pipelines, then that can be easily explained on the website. Using the term continuous delivery is very confusing to users who are unfamiliar with the development model and its implications, as I was uniformed. Thanks again for the explanation.
No problem any time,,,,if you have any questions do let us know.
Thanks Peppermint OS for all the info and time invested.
Just watched this video from above, at least I tried to.
https://youtu.be/7JN57toaSG8
How many 'f' and 's' words does one need to make a point?
It made my toes curl.
Enough said.
Off topic:
Me thinks that Peppermintos is a step up from Devuan itself,
the -default- desktop is much more pleasant to the eyes.
To name but one thing.
Kind regards,
Edward
LPE - Thanks! yeah they were piling on back then ..... I could not really fully understand why...we were and still are trying to keep the project alive....that is a good thing...LOL
None the less thanks for the kind words