Yep, this parallels the problem with docs, which we decided belong in the module.<br><br>It's possible we could still have broader examples that go into a shared examples directory and only update on a full Seam release, then have local examples for modules that can be updated more often. Actually, this option is good because we can verify backward compatibility in the general examples while still having the flexibility to demonstrate more specific features in the module-local examples.<br>
<br>-Dan<br><br><div class="gmail_quote">On Tue, Nov 24, 2009 at 12:00 PM, Shane Bryzak <span dir="ltr"><<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I can foresee a potential issue with the release cycle for examples,<br>
especially if we go down the path that we discussed during the meeting<br>
where we consolidate examples into more complex apps that demonstrate<br>
multiple Seam features. For example, let's say that we release a<br>
production version of Seam 3.0.0 that contains (among other things):<br>
<br>
Seam Security 3.0.0<br>
Seam examples 3.0.0<br>
<br>
Now let's say I add some new feature into security and decide to do a<br>
release of Seam Security 3.0.1. If I have accordingly updated the<br>
security examples with the new feature, does that mean that I need to do<br>
a simultaneous release of Seam examples 3.0.1? Also, what if other<br>
sub-project leads have in the meantime added new features to their<br>
modules and their examples are in an incomplete state? As you can see<br>
this becomes a problem.<br>
<br>
One possible solution is to remove the examples branch altogether and<br>
include the examples within the related module instead. This prevents<br>
us though from creating multi-feature examples, as they will be bound to<br>
the sub-project lifecycle. One other option is to only release<br>
examples during a major Seam release, however this is less desirable in<br>
the case where we release a module with complex new features that really<br>
need to be demonstrated.<br>
<br>
IMHO out of these two options the first one seems the lesser of two<br>
evils, however I'm wondering what you guys think.<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>