[jbosstools-dev] Re: We have branched - Codefreeze and status

[Sean Flanigan]

Max Rydahl Andersen wrote:
> This means that if an issue is set to be fixed for CR2 you need to
> commit to both trunk and CR2.
> The release of CR2 is for as soon as possible, best would be if it is
> available Wednesday to not have
> to wait till monday to do the release announcement.
> 
> For trunk work on GA can now resume BUT remember, GA is *not* for adding
> new features -
> we need to keep GA *stable*, don't experiment on GA with
> partial/inprogress commits etc.
> 
> If you are in doubt if an issue is ok to work on ask on jbosstools-dev.

So, if I understand correctly, trunk is still frozen for new work?  Will
the GA release will eventually happen from trunk, rather than the CR
branch?  Does that mean that the CR branch is not really a Candidate for
[GA] Release?

Why not call the branch the 3.0 branch, to be used for
stabilisation/bugfixes now, and eventually to become the 3.0 maintenance
branch?

I guess I'm having trouble understanding the conventions of
trunk/branches in this project.  Perhaps there is a wiki page to cover
this sort of thing?

Do I need to hold off on string externalisation (JBIDE-3557) until after
GA?  I don't plan to break the trunk build (who does?), but even small
changes need QA before release.   (If you're just saying not to make
architecture-breaking changes in trunk, then that's different.)

Thanks

Sean.

-- 
Sean Flanigan

Senior Software Engineer
Engineering - Internationalisation
Red Hat

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20090127/61cddf9f/attachment.bin