[seam-dev] Seam patches and SVN logistics

[Arbi Sookazian]

In this specific case (Seam 3.0), there is no current production support so
for now it seems like it may be ok to work directly from svn trunk (minus
the broken build problem when bugs are committed).  However, I have been
involved in private JIRAs via the Redhat/JBoss CSP in the past (with SLAs of
course) and that means the core devs will need access to a clean, working
trunk for prod maintenance, bug fixes, etc.  So I'd imagine in the future
there will be a trunk and another future project branch at minimum.  It must
have been like this in the past?

I would imagine Redhat/JBoss would have some kind of SCM standards but I
work for a division of Intuit and we don't have current SDLC/SCM standards
or best practices that I know of (or that are strictly enforced anyways).
Unfortunately, we are "slated" to migrate to Perforce (commercial product
with support but Collabnet offers support for SVN as well) in the near
future and I'm sure that won't be widely positively accepted.

Check this out:  http://java.dzone.com/news/vcs-survey

Anyways, looking forward to some good stuff from Seam 3.

btw, from this link: http://anonsvn.jboss.org/repos/seam/modules/ I don't
see a core module.  The Seam 2.2.x core will be heavily refactored (or
completely re-written/replaced) by Weld 1.0.x I'd imagine.  But will it
really be completely replaced?  I can't imagine so if Seam3 will be
backwards compatible with Seam 2.x apps...  I'd like to try out Seam 3
eventually with our non-trivial Seam/RF/JPA/JSF app here (which consists of
two Maven projects and a couple of common/infrustructural projects that are
shared b/n projects here).

I'm also wondering how backwards-compatible JSF 2 is.  I tried it briefly
with my app and experienced some problems (possibly due to
misconfiguration?) so reverted back to JSF 1.2 Mojarra for now.  It's tough
to sell Java EE 6 at enterprise shops that tend to be conservative in terms
of adopting technology (e.g. we like to stay 1 to 2 major revisions
behind).  thx.

On Thu, Mar 18, 2010 at 9:00 AM, Dan Allen <dan.j.allen at gmail.com> wrote:

> On Thu, Mar 18, 2010 at 11:41 AM, Dan Allen <dan.j.allen at gmail.com> wrote:
>
>> On Thu, Mar 18, 2010 at 10:31 AM, Lincoln Baxter, III <
>> lincolnbaxter at gmail.com> wrote:
>>
>>> Hey Arbi,
>>>
>>> Long story short, we're still working on setting up the infrastructure
>>> and providing that information to everyone so they can be on the same page.
>>>
>>> Hopefully we'll have this under wraps soon,
>>
>>
>> I'll second Lincoln by saying that you have raised great
>> questions...questions that need to be addressed. And it just so happens we
>> are working on initiating discussions with the community as I write this.
>> Now is definitely the time to jump into Seam 3 and share your input and
>> ideas. I'm talking to Lincoln right now about putting together some wiki
>> pages that explain and document the process. Stay tuned.
>>
>> We'll try not to let us slow us down, but keep in mind we are also a man
> short for a while as Pete is on vacation this month :)
>
> -Dan
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20100318/17e314ac/attachment.html