Empathy List Archives

MK

Marius Kintel

Tue, Dec 1, 2015 3:34 PM

To clarify:

o OpenSCAD releases: YYYY.MM. Every new release is expected to add new behavior, and perhaps change or deprecate behavior as well
o Bugfix releases: YYYY-MM-n. These are pure (critical) bugfixes with no new functionality added.
o Development snapshots: YYYY.MM.DD. These are unstable builds, then may contain new experimental functions, they may be severely bug ridden, but tend to be relatively stable.

Yes, we can change this. In the future. The proposed OpenSCAD2 major update could be a good time to do this.

-Marius

On Dec 1, 2015, at 08:29 AM, Ari Diacou ari.diacou@gmail.com wrote:

Thanks!

but why wasn't it called 2015.12?

To clarify: o OpenSCAD releases: YYYY.MM. Every new release is expected to add new behavior, and perhaps change or deprecate behavior as well o Bugfix releases: YYYY-MM-n. These are pure (critical) bugfixes with no new functionality added. o Development snapshots: YYYY.MM.DD. These are unstable builds, then may contain new experimental functions, they may be severely bug ridden, but tend to be relatively stable. Yes, we can change this. In the future. The proposed OpenSCAD2 major update could be a good time to do this. -Marius > On Dec 1, 2015, at 08:29 AM, Ari Diacou <ari.diacou@gmail.com> wrote: > > Thanks! > > but why wasn't it called 2015.12? >

MK

Marius Kintel

Tue, Dec 1, 2015 3:38 PM

..I forgot (as it felt needless to say): Yes, all bugfixes are in master. As all development happens in master, we simply cherry pick or backport critical issues to 2015.03-x when needed.

-Marius

On Dec 1, 2015, at 09:25 AM, Jerry Davis jdawgaz@gmail.com wrote:

have those 2015.03 fixes been merged with the newest dev branch?
just askin.

..I forgot (as it felt needless to say): Yes, all bugfixes are in master. As all development happens in master, we simply cherry pick or backport critical issues to 2015.03-x when needed. -Marius > On Dec 1, 2015, at 09:25 AM, Jerry Davis <jdawgaz@gmail.com> wrote: > > have those 2015.03 fixes been merged with the newest dev branch? > just askin.

MK

Marius Kintel

Tue, Dec 1, 2015 3:46 PM

I don’t have a good way of ensuring a clean history.
My workflow is usually to git cherry pick commits related to github issues from master into 2015.03.x.
Even though this would give us an equivalent patch, the git commit hash would be different.
I think that, in order to have a properly linked graph, we’d have to do development in the 2015.03 branch and merge those changes into master. That’s a perfectly valid workflow, we just tend not to do it.

-Marius

On Dec 1, 2015, at 10:27 AM, doug moen doug@moens.org wrote:

Thanks, nop head, I didn't know about Graphs/Network.

It's not showing me what I want, though. In the Network diagram, I can see two separate commits just before Nov 16, on the master and 2015.03 branches, both labelled "sync with 2015.03-2", but there is no arc connecting these nodes. The two branches don't have any connecting arcs, as far back as I looked.

I don’t have a good way of ensuring a clean history. My workflow is _usually_ to git cherry pick commits related to github issues from master into 2015.03.x. Even though this would give us an equivalent patch, the git commit hash would be different. I think that, in order to have a properly linked graph, we’d have to do development in the 2015.03 branch and merge _those_ changes into master. That’s a perfectly valid workflow, we just tend not to do it. -Marius > On Dec 1, 2015, at 10:27 AM, doug moen <doug@moens.org> wrote: > > Thanks, nop head, I didn't know about Graphs/Network. > > It's not showing me what I want, though. In the Network diagram, I can see two separate commits just before Nov 16, on the master and 2015.03 branches, both labelled "sync with 2015.03-2", but there is no arc connecting these nodes. The two branches don't have any connecting arcs, as far back as I looked.

C

ctchin

Wed, Dec 2, 2015 5:06 AM

kintel wrote

The new binaries are available for download, or on their way shortly.

I was waiting and waiting for the -2 installer being a little jealous of
MacOS users who got their dmg already.

Only today I was impatient enough to check http://files.openscad.org/ and
found that the Windows installers had been sitting there for over almost 2
weeks Why does the download page fail to link to the latest release?

http://www.openscad.org/downloads.html#windows

Thanks! But a little frustrated...

--
View this message in context: http://forum.openscad.org/OpenSCAD-2015-03-2-released-tp14860p14887.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

kintel wrote > The new binaries are available for download, or on their way shortly. I was waiting and waiting for the -2 installer being a little jealous of MacOS users who got their dmg already. Only today I was impatient enough to check http://files.openscad.org/ and found that the Windows installers had been sitting there for over almost 2 weeks Why does the download page fail to link to the latest release? http://www.openscad.org/downloads.html#windows Thanks! But a little frustrated... -- View this message in context: http://forum.openscad.org/OpenSCAD-2015-03-2-released-tp14860p14887.html Sent from the OpenSCAD mailing list archive at Nabble.com.

MK

Marius Kintel

Wed, Dec 2, 2015 5:51 AM

On Dec 2, 2015, at 00:06 AM, ctchin c.t.chin@szu.edu.cn wrote:

Only today I was impatient enough to check http://files.openscad.org/ and
found that the Windows installers had been sitting there for over almost 2
weeks Why does the download page fail to link to the latest release?

We upload to the server before announcing the release, so we have the chance to test last-minute issues.
I guess we forgot to push the new link to the website, sorry.

-Marius

> On Dec 2, 2015, at 00:06 AM, ctchin <c.t.chin@szu.edu.cn> wrote: > > Only today I was impatient enough to check http://files.openscad.org/ and > found that the Windows installers had been sitting there for over almost 2 > weeks Why does the download page fail to link to the latest release? > We upload to the server before announcing the release, so we have the chance to test last-minute issues. I guess we forgot to push the new link to the website, sorry. -Marius

SK

Steve Kelly

Thu, Dec 3, 2015 2:09 PM

'git cherry-pick -x' adds a cross reference and can help when using other
tools like github to analyze branches.
On Dec 2, 2015 12:52 AM, "Marius Kintel" marius@kintel.net wrote:

On Dec 2, 2015, at 00:06 AM, ctchin c.t.chin@szu.edu.cn wrote:

Only today I was impatient enough to check http://files.openscad.org/

and

found that the Windows installers had been sitting there for over almost

2

weeks Why does the download page fail to link to the latest release?

We upload to the server before announcing the release, so we have the
chance to test last-minute issues.
I guess we forgot to push the new link to the website, sorry.

-Marius

OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

'git cherry-pick -x' adds a cross reference and can help when using other tools like github to analyze branches. On Dec 2, 2015 12:52 AM, "Marius Kintel" <marius@kintel.net> wrote: > > On Dec 2, 2015, at 00:06 AM, ctchin <c.t.chin@szu.edu.cn> wrote: > > > > Only today I was impatient enough to check http://files.openscad.org/ > and > > found that the Windows installers had been sitting there for over almost > 2 > > weeks Why does the download page fail to link to the latest release? > > > We upload to the server before announcing the release, so we have the > chance to test last-minute issues. > I guess we forgot to push the new link to the website, sorry. > > -Marius > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >

discuss@lists.openscad.org

OpenSCAD 2015.03-2 released