<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
<blockquote cite="mid:497EBC76.1030205@redhat.com" type="cite">
<pre wrap="">Couldn't you just use the "CR" branch for that? (By another name,
preferably.) I don't really understand what changes would go into trunk
but not into the branch. If the answer is "no changes", then the branch
is redundant at present, is it not? Or are you saying there are issues
which we intend to fix (in trunk) for GA, but not for the the CR?
</pre>
</blockquote>
Yes - <a href="https://jira.jboss.org/jira/browse/JBIDE">https://jira.jboss.org/jira/browse/JBIDE</a>,
GA currently have 46+ issues for it. Those need to <br>
get reduced though ;)<br>
<br>
The branch is not redundant - it is there to give build and QA
engineers a chance to do builds safely<br>
and to allow progress on GA to continue.<br>
<blockquote cite="mid:497EBC76.1030205@redhat.com" type="cite">
<blockquote type="cite">
<pre wrap="">Safe string externalisation I'm ok with, I assume you did you *big*
change a few weeks back, correct ?
</pre>
</blockquote>
<pre wrap=""><!---->
So far, excluding the "i18n" folder, everything I've done has been
simple string externalisation, nothing *big*. Just lots of small
changes. Looking at the changesets, I haven't checked in any .java changes.
Even so, it may not be 100% safe, since I had to do most of it by hand
(no wizards for some things). As much as possible, I have tried to
smoke-test them in the GUI, but it's difficult to test every string when
you don't know the GUI inside out.
Most of the remaining externalisation will be the easier, wizard-driven
type, except where I have to introduce MessageFormat. However, once I
start externalising entire plugins, rather than targeting individual
strings from the GUI, comprehensive testing will become much more
labour-intensive.
</pre>
</blockquote>
hmm - I might want to hold back on that till after GA then.<br>
Could you give a status per module/plugin on what you have
covered/not-covered ?<br>
<br>
<br>
<blockquote cite="mid:497EBC76.1030205@redhat.com" type="cite">
<blockquote type="cite">
<pre wrap="">And yes, I'm saying don't make big functional changes or additions in
trunk - make bugfixes.
</pre>
</blockquote>
<pre wrap=""><!---->
Is 18n a feature, or are unexternalised strings bugs? :-)
</pre>
</blockquote>
unexternalised strings are bugs, doing l8n in another language than
english is a feature ;)<br>
<br>
/max<br>
<br>
</body>
</html>