I'm thinking of moving The Burning Edge to the aviary branch.
Trunk advantages:
- Will become Firefox 2.0 in the future.
- Has a fix for config.trim_on_minimize (248423).
- Has a fix for Slashdot rendering (217527).
Branch advantages:
- Will become Firefox 1.0 and all Firefox 1.x releases, so it's more important to test in the short term.
- Find Toolbar.
- Live Bookmarks (in tomorrow's builds).
- Has fixes for some toolbar customization bugs (232707, 221482).
- Has a working extension manager.
This entry was posted
on Wednesday, July 7th, 2004 at 7:05 pm and is filed under Other.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
July 7th, 2004 at 7:12 pm
> Will become Firefox 2.0 in the future.
Will Firefox 1.x never return to the trunk? I thought, that the aviary branch was only created for Firefox release 0.9-1.0.
July 7th, 2004 at 7:22 pm
I am more interested in the 1.0 release track.
July 7th, 2004 at 7:30 pm
How about you track the branch until 1.0, and then see where the major action is at that point? If there are outstanding bugs and a quick maintenance release (1.0.1 or something) is indicated, then keep following it. Otherwise, consider switching back to the trunk.
July 7th, 2004 at 7:43 pm
All the action is in the branch. New features, new regressions, new crashes, yay!
July 7th, 2004 at 8:05 pm
Agreed; I think the Burning Edge summaries are more useful to end users than to developers, and end users will be more interested in the branch that will become the next release.
July 7th, 2004 at 8:09 pm
Blake Ross (a Firefox developer) reads The Burning Edge and says it would be more useful to him if it followed the branch.
July 7th, 2004 at 9:23 pm
http://www.exchangecode.com/spellbound/
since “spellbound” only states .9+ (actually the title say 9.0+… but we’ll let that pass) I’m sticking with aviary… heaven forbid it looks for .8 somewhere… shrugs
July 7th, 2004 at 9:48 pm
Go with the branch because 1) people read your buglists and d/l the ones with the least amount of pink :) — we need aviary testers — and 2) the trunk is just going to be behind and then one day you’re going to have a giant patch that says something like “ported extension manager from branch to trunk” and we’ve missed all that development.
Not to mention, since the road to 1.0 is on the branch, this blog stopped being on the bleeding — er burning — edge when it stopped covering the branch.
July 7th, 2004 at 10:35 pm
Leading up to 0.8 you covered both, I thought that was nice. I understand if that takes up too much of your time though. At the moment, the branch is more important to track, but it would be nice if there were weekly updates about the trunk as well.
July 8th, 2004 at 12:57 am
Go for the branch, Jesse! I’ll be with you :)
July 8th, 2004 at 1:08 am
Go with the branch – primarily because the new extension manager works on the branch.
July 8th, 2004 at 1:38 am
You should stay with the trunk, because it concerns also Mozilla 1.8 branch where all modifications related to gecko engine appear first
July 8th, 2004 at 3:58 am
I would start testing aviary builds if you switch to cover the branch. Currently I just use the release versions.
July 8th, 2004 at 6:26 am
Another me too for the Branch.
July 8th, 2004 at 7:07 am
I also vote for the branch.
July 8th, 2004 at 7:44 am
I say go with the aviary branch. :)
July 8th, 2004 at 7:56 am
+1 for the Branch.
July 8th, 2004 at 8:01 am
I’ve never used a branch build — I follow the burning edge as according to you. It makes sense to switch over to branch if it’s practical and then switch back to trunk as we get closer to 2.0 — say maybe at 1.7 or something of the sort ;)
My vote is for the branch.
July 8th, 2004 at 9:26 am
I personally would like to continue the trunk, however simply because in mozillazine forum mainly everyone concentrate on branch and I like to be informed at BE about the trunk a lot. However, choose wisely ;)
July 8th, 2004 at 9:55 am
+1 for the branch
July 8th, 2004 at 1:57 pm
I’m more interested in the leaves… :|
July 8th, 2004 at 2:37 pm
+1 for BOTH :-)
but I also thought the AVIARY branch was for up to 1.0 only…
July 8th, 2004 at 3:57 pm
I vote also for the trunk, because aviary branch is already covered in mozillazine board
July 8th, 2004 at 4:07 pm
branch++;
July 8th, 2004 at 5:49 pm
I vote for branch. And its obvious that most people agree with me =)
July 8th, 2004 at 6:59 pm
I counted 18 votes for branch and 4 for trunk. Branch it is :)
July 8th, 2004 at 7:00 pm
I’ll try to do weekly trunk updates.
July 9th, 2004 at 5:11 am
Sounds like a good decision. And thank you again for the work you do on BE!
July 9th, 2004 at 11:03 am
I vote for the trunk. It’s faster and I don’t use any extensions so I don’t need the extension manager from aviary.
July 15th, 2004 at 6:45 am
How about taking advantage of the categories in MovableType and do both?
July 15th, 2004 at 8:52 am
I do use categories in Movable Type (trunk, branch). Posts with a gray border are branch. There are archive pages for each. I don’t remember if I set up an RSS feed for each.
July 19th, 2004 at 11:09 am
Is it too late to vote for Trunk?