On 16 juil, 20:11, Daniel Jue <[email protected]> wrote:
> Sorry, what I was trying to say is that I don't think they go back and
> add fixes to the previous versions. Any improvements or patches are
> included in the latest version number.
>
> There are a whole bunch of tickets listed as "fixednotreleased" which
> go into a planned future release.
> If you look at the current "branches" section of the repository, there
> is only 1_6 and some intermediate build snapshots (which I assume
> needs to be renamed to 1_7 now) As soon as 1.6 came out, I think they
> stopped adding fixes to 1.5.x. I guess the same for 1.6 now that 1.7
> is out, etc.
AFAICT, the repo is organized as follows:
- /changes contains development branches that only one developer
works on at a time; anything there can be discarded at any time,
there's no guarantee it'll end up in GWT in the end (some branches
there are "playgrounds" for new features)
- /branches contains development branches that are shared between
developers and *will* (or already have) end up in GWT (e.g. the oophm
branch, which is being merged into trunk; htmlunit for automated UI
tests, and crawlability to, if I understood correctly, make your apps
SEO-friendly). It also contains "snapshot" of the trunk that I guess
are used internally at Google for their projects such as Wave, Code
Search, Moderator, etc. (trunk is deemed stable enough that a snapshot
is taken, the snapshot eventually gets "patched" by cherrypicking
fixes from the trunk when a "really annoying" bug is found)
- /trunk is the main development "branch", as of now, it is what will
become GWT 2.0
- /releases contains development branches for releases; they're
mainly "feature freezed"; they allow for development of other features
on /trunk without "disturbing" the release process (e.g. runAsync,
oophm, several compiler optimizations, etc.). When they'll want to
start working (on a day-by-day basis, otherwise they'll use /branches)
on a feature for post-2.0, they'll create a /releases/2.0 branch and
work on the new feature on /trunk. Thus, if /trunk isn't ready and the
latest release needs an update, they can work on /releases
independently of /trunk (that's what happened with 1.7, which is
derived from 1.6, not from trunk –remember, it's only called 1.7
instead of 1.6.5 because it introduces a new ie8 permutation which
might break many third-party libs–)
> Is there a gwt dev on here that can attest to this?
I'm not a gwt dev, but I confirm that there's only one supported
version of GWT: the latest released version.
That means that if you have an issue with 1.5.3, you'll have to either
patch it yourself or upgrade (same thing if you have an issue with
1.6, though migrating from 1.6 to 1.7 is almost seamless).
It also means there won't be any other 1.5.x or 1.6.x version (maybe
we'll see a 1.7.1 or 1.8 before the 2.0 gets out though).
I believe you can find a message from a gwt dev stating this, either
on this group or on the contributors one (might date from the time 1.5
was released, and someone asked for a 1.4 update).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
