Updated Roadmap Including 0.5 Plans

[sasquatch]

In other words, the .5 is now the release version.

Is there a separate trunk and branch now being worked on?

Thanks again.

[mscott]

just the trunk...those are the test builds called 0.5+

the branch was 0.5, there is no more development on the branch now that the release is out.

[sasquatch]

Oh, OK.

I know on Firebird, there was a released build (.7), then a branch which was leading up to the .8 release (Firefox), and the trunk.

I thought this program might follow the same model.

[mscott]

huh? we did follow that exact model. I don't understand what you are talking about.

0.4 was released...

we did developement work..got close to 0.5
0.5 branch was created leading upt to the 0.5 release
0.5+ development work continued on the trunkk
and now we'll be shifting focus back to the trunk now that the branch is ended?

I don't see where our model differs?

[sasquatch]

In FB, there was the .7 release.

Builders built branch and trunk builds, so there were 3 builds available to choose from.

Here with TB, we have .5 release. Is there a .6 trunk and branch to make 3 builds to choose from?

Maybe I'm missing something.

Thanks.

[wgianopoulos]

What about branch builds?

I always thought it was trunk/branch/release going from least to most stable and from most new to least new code.

Thanks.

There are no branch builds until it gets close to release time. The purpose of cutting a branch is to pick a time when the low level code that is shared by the Mozilla suite, Firefox and Thunderbird is considered to be stable and about ready for a release. This is ususally done around the time the application suite beta release comes out. That way you can do all the final getting something ready for release extra testing, making release candidates, etc. without having to worry about someone checking in some huge fix that does not work that breaks DNS name resolution or fixes it so you can't talk TCP/IP at all, etc. when you are trying to get your final tweaks done for your application.

[sasquatch]

I thought there was ALWAYS a branch and a trunk, just like in a real tree.

That way, while the trunk gets the big changes, like you said, the branch will get refined and ready for the next release. Just look at how much has changed since the branch which just became Firefox was released. I would think what was the trunk at that point would now become a branch, and then trunk would go on from there.

Ditto the release of .5 Thunderbird, less the name change part.

[jhirshon]

Can't we just give this "trunk/branch" nomenclature issue a rest? Not trying to be rude, just want to keep things focused

[sasquatch]

Any recent roadmap changes for Thunderbird?

[filmsi]

Now that 1.7 will be the next long-lived milestone branch and the release is now retargeted to mid-May instead of mid-April (http://groups.google.com/groups?as_umsg ... ozilla.org), will Thunderbird 0.6 still come out around middle of April or will we have to wait for next Thunderbird release until middle of May?

[fishbert]

Now that 1.7 will be the next long-lived milestone branch and the release is now retargeted to mid-May instead of mid-April (http://groups.google.com/groups?as_umsg ... ozilla.org), will Thunderbird 0.6 still come out around middle of April or will we have to wait for next Thunderbird release until middle of May?

Following your link I see:

*Thunderbird 0.6*

- All features in except Pinstripe theme for OS X
- Hopefully landing tomorrow
- Release scheduled for mid-April
- Again, plan to ship from 1.7 branch, pre-1.7
- Waiting for a little more stability

Does that answer your question?

[sasquatch]

This bug might be of interest:

http://bugzilla.mozilla.org/show_bug.cgi?id=240476