New release of Mutt STABLE in -current

Gerard Lally · 04-04-2016, 06:15 PM

Didn't think they'd ever get there!

MadMaverick9 · 04-05-2016, 01:19 AM

Get where?

They are not there yet.

https://dev.mutt.org/trac/milestone/1.6

Code:

Milestone 1.6

Total number of tickets: 229 - closed: 228 - active: 1

One more open bug to go https://dev.mutt.org/trac/ticket/3649

This really should've been 1.5.25.

But then ... http://www.mutt.org/download.html

Quote:

As of 1.6, Mutt has switched away from the dev/stable versioning scheme. Going forward, version numbers will be incremented based on the significance of the release.

I am gonna refrain from further comments on this. First vim, now this. I really don't like where this is going.

Paulo2 · 04-06-2016, 09:31 AM

One more flea

About the numbering version, I think the (more)chaos started with Google Chrome
with Firefox following it. Firefox is still in major version 3 I guess.
Even Linux kernel is jumping version numbers.

MadMaverick9 · 04-06-2016, 11:29 PM

Quote:

Originally Posted by Paulo2

About the numbering version, I think the (more)chaos started with Google Chrome
with Firefox following it.

This is not so much about version numbers but more about the fact that developers "release" stuff that is not ready yet. Take your time. Release it when it's ready.

Like I pointed out before with vim: every git commit is a "release" now. Completely useless.

And I agree - it started with google chrome and I personally believe git is part of the problem.

https://www.jwz.org/doc/cadt.html

Quote:

Originally Posted by jwz

I'm so totally impressed at this Way New Development Paradigm. Let's call it the "Cascade of Attention-Deficit Teenagers" model, or "CADT" for short.

Paulo2 · 04-07-2016, 08:13 AM

Quote:

Originally Posted by MadMaverick9

This is not so much about version numbers but more about the fact that developers "release" stuff that is not ready yet. Take your time. Release it when it's ready.

Like I pointed out before with vim: every git commit is a "release" now. Completely useless.
...

Thanks for the explanation, I have misunderstood.

Tonus · 04-08-2016, 02:14 PM

Btw, about mutt, couldn't have it to compile... First tried to patch for the sidebar, then, because it failed, tried from official slackbuild, with no luck too... Strange magic ?

MadMaverick9 · 04-08-2016, 10:38 PM

@Tonus: what version of Slackware are you trying it on? You don't say. Where did you download the mutt 1.6.0 Slackbuild from? What error do you get? You don't give any information that would allow people to help you. Just saying "it doesn't work" ain't gonna do it. Sorry dude. And - what version of mutt are you trying to build? You don't say that either.

Download mutt 1.6.0 Slackbuild from http://slackware.osuosl.org/slackwar...source/n/mutt/.

Code:

bash $ cat /etc/slackware-version 
Slackware 14.0
bash $ ./mutt.SlackBuild
mutt-1.6.0/
mutt-1.6.0/filter.c
mutt-1.6.0/url.c
...
Slackware package ../mutt-1.6.0-i586-1.txz created.

As you can see it builds fine on Slackware 14.0.

Works for me.

frankbell · 04-08-2016, 11:14 PM

Quote:

This is not so much about version numbers but more about the fact that developers "release" stuff that is not ready yet. Take your time. Release it when it's ready.

The target is not "ready." The target is "good enough."

Otherwise we would all still be on DOS 3.2.

"Ready" is a moving target.

Just my two cents.

Tonus · 04-09-2016, 02:54 AM

Quote:

Originally Posted by MadMaverick9

@Tonus: what version of Slackware are you trying it on? You don't say. Where did you download the mutt 1.6.0 Slackbuild from? What error do you get? You don't give any information that would allow people to help you. Just saying "it doesn't work" ain't gonna do it. Sorry dude. And - what version of mutt are you trying to build? You don't say that either.

Yes, my bad, might have been a bit tired :-/

Mutt 1.6.0, slackbuild from source dir in official slackware repo. I did apply the sidebar patch but might forgot to look close at the slackbuild or the patch. Can't even remember if I added the slang parameter correctly...

Sorry for the noise. Will go back to homework before posting further more :-P