Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Renaming Iceweasel to Firefox

bugs.debian.org

Post reply on HN
Print view View original

71–80 of 155 posts

Re: Renaming Iceweasel to Firefox

#71

Post by legulere »

ryandrake wrote: post #27

> Mozilla releases new Firefox releases every 6 to 8 weeks. In parallel of these rapid releases [...] One of the fun differences between the various organizations I've worked for is the differing ideas of how frequently releases should happen and what is considered "fast" and "slow" in different places. I've seen release cycles measured in weeks and those measured in years. I'm sure there are places that release ever…

I find it very interesting that they are adopting a different release schedule for Firefox than the rest of Debian stable. People that care about fast release cycles probably really just care about few minor things being up to date, while administrators don't care about which programs/libraries make problems when updating as long as the total amount of breakages in a certain time isn't too high.

Re: Renaming Iceweasel to Firefox

#72

Post by marssaxman »

twunde wrote: post #15
Touche wrote: post #2

> On the contrary, Debian having a longer release cycle (about every two years), release cycles don't align. Then change your release cycle. Seriously, it's not that hard. Say that browsers are different and get released frequently. Create a firefox-lts package that is updated at the beginning of your Debian release cycle -- and never again. Let the firefox package be the firefox package, updated as frequently as ups…

If you don't like the 2 year release cycle, use Ubuntu, which is Debian-based. Debian maintains such long release cycles because the tolerance for bugs and incompatibilities are smaller than other linux distros. For long-lived applications or applications that have long planning periods Debian is ideal. NASA uses Debian, because their projects are measured in years, have low tolerances for bugs, and are developed to…

It's really very nice to just throw Ubuntu 14.04 on everything and not worry about it. I can use my machines for doing work and not have to waste a lot of time dealing with whatever the latest churn is.

Re: Renaming Iceweasel to Firefox

#73

Post by baldfat »

mfontani wrote: post #11
baldfat wrote: post #10

Earlier quoted context omitted.

I have been just doing dup on OpenSUSE for over 6 years without a single issue. :) I am getting rusty on rebuilding server skills. Debian's update system does drive me nuts, but I have never run a Debian server for longer then 6 months.

Considering the last distro upgrade had Apache going from 2.2 to 2.4, which introduced considerable changes to the config file format, "upgrading the servers" is not something that can be done in _all_ cases.

But that is an issue with Apache and not really a Distro issue. I'm thinking I didn't have to change anything on my Apache config since mine is very vanilla.

So if you have a vanilla config on Apache it still works.

Re: Renaming Iceweasel to Firefox

#74

Post by miah_ »

jhasse wrote: post #56
astrodust wrote: post #14

Earlier quoted context omitted.

Although GitHub Issues has a lot of issues, for the singular reason that you can opt-in and opt-out of notifications on particular subjects I find it vastly more useful than most bug trackers. Is there a good open-source GitHub alternative that implements this feature?

> you can opt-in and opt-out of notifications on particular subjects What do you mean by that? Doesn't every bug tracker implement that feature?

You can (un)subscribe to specific issues, but you cannot filter issues in general. Which means you'll still get notified about new issues until you manually (or programmatically) unsubscribe from them.

Re: Renaming Iceweasel to Firefox

#75

Post by steveklabnik »

vermontdevil wrote: post #69
steveklabnik wrote: post #23

Earlier quoted context omitted.

Debian user and Mozilla employee who uses Iceweasel here. I work on Rust, not Firefox though. > Why does the operating system have any say on what applications get released > and how often? This has to do with the interaction between the original authors and the distribution itself. Let's go through an example: 1. I, Steve, write some bit of software, libfoo, and host it on my GitHub page. 2. Debian users would like…

Yep. Thanks for this. Painted a great pic in my mind about the issue/process here.

Great, glad to help.

Re: Renaming Iceweasel to Firefox

#76

Post by ebbv »

nitrogen wrote: post #34
oliwarner wrote: post #28

Congratulations HN, OP, we DDoSed the debian bug tracker. Please be considerate when linking to webapps. If there's a static or cached version available, please post that. In this case Debian's tracker mirrors everything to publicly mirrored mail servers (which are static), ie: https://www.mail-archive.com/debian-bugs-dist@lists.debian.o...

Or write faster apps? Caching pages for logged-out users is part of web site performance 101.

Right so even if your application is only meant for 10 concurrent users it's your duty to optimize it to the point where it can handle HN traffic...

Come on man.

Re: Renaming Iceweasel to Firefox

#77

Post by secure »

windsurfer wrote: post #36
nitrogen wrote: post #34

Earlier quoted context omitted.

Or write faster apps? Caching pages for logged-out users is part of web site performance 101.

Debbugs works great for being last updated 12 years ago. It's main interface is email, after all, so the web interface is read-only. I think the real issue here is the hardware it's running on.

With regards to hardware being the issue:

The last I’ve heard was that debbugs is run on the fastest hardware the Debian project has available, i.e. one of the few machines with fast SSDs.

Re: Renaming Iceweasel to Firefox

#78

Post by moron4hire »

subway wrote: post #68
moron4hire wrote: post #45

Earlier quoted context omitted.

Untrusted by whom? It's the same vendor whether it comes from their site or the package repository. And maybe people include way too many dependencies in their projects if it's too much to manage manually. Also, installers are perfectly capable of managing dependencies.

It's the same vendor whether it comes from their site or the package repository. Prove it. The package manager allows you to cryptographically verify the binary was inspected by somebody you trust (the package maintainers). While windows has added code-signing/verification capabilities, many installers are unsigned, and those which are signed don't have a useful trust anchor.

Prove the repository maintainer doesn't blanket approve things because they are overwhelmed.

Re: Renaming Iceweasel to Firefox

#79

Post by mort96 »

moron4hire wrote: post #46
temp wrote: post #24

Earlier quoted context omitted.

>Installers aren't that bad Nothing stops you from getting Firefox on Debian the "Windows" way.

Tried it, couldn't get it to work. This was Raspbian, though.

Did you try to download the x86 build? If so, it's your fault. If they don't provide an arm build, or if you got the arm build, it's Mozilla's fault, not Debian's.

Re: Renaming Iceweasel to Firefox

#80

Post by autoreleasepool »

oliwarner wrote: post #39
chrisan wrote: post #35

Earlier quoted context omitted.

I'm not familiar with whatever bug tracker they use, but shouldn't this be the default such that a user doesn't have to make this mental note?

Perhaps I'm being unfair —because I know how the sausage is made— but if it looks like it's generated by Perl (clunky late-90s design, obvious interactive parts, filter, logins, etc) it probably scales like a squirrel carrying watermelons. (One at a time is okay.) Debian should definitely do more to stop this from happening but this isn't the first time a HN link to a clunky old webapp has taken it down.

I fail to understand how the burden of a clunky outdated web app should be the end users problem.

You may be able to spot a 90's style perl-based web app but some of us are much younger and in a different field than web development.

I don't think it's worth shaming OP and HN for using the Internet as intended. The real problem seems to be that Debian is using outdated technology for their bug tracker.

Post reply on HN