version
Is 2021.01 the latest version of OpenSCAD?
The "latest, official" version, I believe. I haven't seen an officially
blessed release since that one (though, hope springs eternal that one will
come out).
On Thu, Aug 22, 2024 at 1:38 PM Joe Weinpert via Discuss <
discuss@lists.openscad.org> wrote:
Is 2021.01 the latest version of OpenSCAD?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
- Jon Gilbert
jong@jong.org / jgilbertsjc@gmail.com
A lot of us use one of the interim builds, with great success. Go to the
Downloads page and scroll until you see Development Snapshots.
On 8/22/2024 5:10 PM, Jonathan Gilbert via Discuss wrote:
The "latest, official" version, I believe. I haven't seen an
officially blessed release since that one (though, hope springs
eternal that one will come out).
On Thu, Aug 22, 2024 at 1:38 PM Joe Weinpert via Discuss
discuss@lists.openscad.org wrote:
Is *2021.01* the latest version of OpenSCAD?
_______________________________________________
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
- Jon Gilbert
jong@jong.org / jgilbertsjc@gmail.com
OpenSCAD mailing list
To unsubscribe send an email todiscuss-leave@lists.openscad.org
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
On Thu, 2024-08-22 at 14:10 -0700, Jonathan Gilbert via Discuss wrote:
The "latest, official" version, I believe. I haven't seen an
officially blessed release since that one (though, hope springs
eternal that one will come out).
Don't be afraid to run dev snapshots. I am running 2024.03.02.ai18721
(git e3e5f8e0c), and have no complaints about it, and it's not even the
latest dev version.
On Thu, Aug 22, 2024 at 1:38 PM Joe Weinpert via Discuss
discuss@lists.openscad.org wrote:
Is 2021.01 the latest version of OpenSCAD?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
- Jon Gilbert
jong@jong.org / jgilbertsjc@gmail.com
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
"Release early, release often."
I wish the developers were not afraid to actually release something
once in a while instead of always telling people to use development
versions for years at a time.
If it's good enough to use, it should be good enough release. If it's
NOT good enough to release, that suggests it's not good enough to use.
+1 for releasing often.
This is especially true for bugs that have unreleased fixes; I think
there's about two I'm still waiting on that have been corrected for some
time measured in years, but I can't leverage yet because they're not part
of an official release. I get that there's bleeding-edge changes that have
the potential for really neat things, and I like that those things are
available as a preview, but if I'm writing vendable libraries I need them
to be backed by something stable. I'm not about to tell co-collaborators to
depend on something that's still potentially in flux.
That said, I'm mostly happy with 2021.01 since it gets me to like 85% of
where I want to be, I'm definitely not wholly blocked on my project, and
I'm excited about what's coming with the next release.
On Thu, Aug 22, 2024 at 3:01 PM Kevin Cole via Discuss <
discuss@lists.openscad.org> wrote:
"Release early, release often."
I wish the developers were not afraid to actually release something
once in a while instead of always telling people to use development
versions for years at a time.
If it's good enough to use, it should be good enough release. If it's
NOT good enough to release, that suggests it's not good enough to use.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
- Jon Gilbert
jong@jong.org / jgilbertsjc@gmail.com
I get frustrated by this too. I'm putting out books using OpenSCAD models, so I can't really tell the readers to download a dev snapshot. However, I'm developing the models using one of these snapshots, then checking that they work as expected in the officially released version. There have been one or two bugs, but the biggest problem is that I have some models that render in a few seconds using recent dev versions, but take 30+ minutes to do the same in the latest release, due to missing features like lazy union and rendering using Manifold instead of CGAL.
I wish someone would make it a priority to clean things up for an official release at least, say, once a year?
On Aug 22, 2024, at 15:09, Jonathan Gilbert via Discuss discuss@lists.openscad.org wrote:
+1 for releasing often.
This is especially true for bugs that have unreleased fixes; I think there's about two I'm still waiting on that have been corrected for some time measured in years, but I can't leverage yet because they're not part of an official release. I get that there's bleeding-edge changes that have the potential for really neat things, and I like that those things are available as a preview, but if I'm writing vendable libraries I need them to be backed by something stable. I'm not about to tell co-collaborators to depend on something that's still potentially in flux.
That said, I'm mostly happy with 2021.01 since it gets me to like 85% of where I want to be, I'm definitely not wholly blocked on my project, and I'm excited about what's coming with the next release.
On Thu, Aug 22, 2024 at 3:01 PM Kevin Cole via Discuss discuss@lists.openscad.org wrote:
"Release early, release often."
I wish the developers were not afraid to actually release something
once in a while instead of always telling people to use development
versions for years at a time.
If it's good enough to use, it should be good enough release. If it's
NOT good enough to release, that suggests it's not good enough to use.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
- Jon Gilbert
jong@jong.org / jgilbertsjc@gmail.com
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
An official release requires documentation. Altering that once, rather
than weekly or monthly, may take less time. I am not an OpenSCAD
developer, but there may be reasons to not do an official release very
often.
On 8/22/2024 6:00 PM, Kevin Cole via Discuss wrote:
"Release early, release often."
I wish the developers were not afraid to actually release something
once in a while instead of always telling people to use development
versions for years at a time.
If it's good enough to use, it should be good enough release. If it's
NOT good enough to release, that suggests it's not good enough to use.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
On Thu, Aug 22, 2024 at 6:37 PM Jon Bondy jon@jonbondy.com wrote:
An official release requires documentation. Altering that once, rather
than weekly or monthly, may take less time. I am not an OpenSCAD
developer, but there may be reasons to not do an official release very
often.
For me, documentation has always been an integral part of the code. Even if
it's in a separate file. This is what I keep stressing with students: If
you make a change to the behavior of code, make a change to the
corresponding documentation. If you're changing the code so often that you
cannot keep up, don't recommend your code in flux to anyone. Small
incremental changes that get stabilized and documented and released are
better than trying to create a masterpiece / opus that will still be
unfinished at the time of your death.
(A development version should only be for developers and testers, not for
people who actually want to use your code in production. Sure, the testers
may do interesting things with new features, but don't make all users
dependent on undocumented features.)
Like many here, I use 2021.01 and am pretty happy with it. But when I keep
reading questions about features mentioned on the mailing list that don't
exist in 2021.01, I wonder if it's time for a list for developers and a
list for users. If the only way I can learn something from the mailing list
is to set up a cron job to install nightly, then the list isn't a general
discussion list.
The OpenSCAD documentation has at least historically been essentially a
crowdsourced document that is not even always correct.
I know there are questions like whether lazy union will ever even appear in
a stable release due to ways it changes the models and broken backward
compatibility, and I think manifold still has bugs, maybe?
But I agree that the slow development cycle can be annoying when crucial
features take years to appear in the stable release.
On Thu, Aug 22, 2024 at 6:38 PM Jon Bondy via Discuss <
discuss@lists.openscad.org> wrote:
An official release requires documentation. Altering that once, rather
than weekly or monthly, may take less time. I am not an OpenSCAD
developer, but there may be reasons to not do an official release very
often.
On 8/22/2024 6:00 PM, Kevin Cole via Discuss wrote:
"Release early, release often."
I wish the developers were not afraid to actually release something
once in a while instead of always telling people to use development
versions for years at a time.
If it's good enough to use, it should be good enough release. If it's
NOT good enough to release, that suggests it's not good enough to use.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org