On 7 Apr 2010, at 11:58, Pete Muir wrote:
On 18 Mar 2010, at 15:23, Dan Allen wrote:
> On Thu, Mar 18, 2010 at 5:31 AM, Andersen Max <max.andersen(a)redhat.com> wrote:
>>> Q: Will it be "simultaneous release" once a year like eclipse
does?
>>>
>>> No, firstly a simultaneous release implies that each module does it's
major feature updates at the same time, I don't see we need to stick to that. Instead
we will bundle a set of compatible modules. Secondly, we aim to release more than once a
year :-)
>>
>> What is the difference between "simultaneous release" and "bundle
a set of compatible modules" ?
>>
>> I think what Pete is implying is that the modules don't have to be releasing
at that time (or should not hold out the released until that date). Instead, we take what
is stable at the time (pushing a release if absolutely necessary to integrate well) and
then cut the bundle. But, to be honest, we're still in the process of establishing a
strategy ;)
>>
>
> Sure, and this is actually also what eclipse "simultaneous release" means -
some projects release several times, some only at that time; but all are keeping an eye on
that 1 a year big release and additional 2 bugfix releases to make sure their stuff gets
done for it. in other words - without a planned "big" release nothing would
actually work together ;)
>
>
> We'd find your team's experience and advice from working with the Eclipse
simultaneous release process a valuable resource, when the time comes for us. No doubt, we
are the newbies in this realm ;)
Ok, I misunderstood the eclipse module, I thought that they only did major releases of
the "modules" at the time of a simultaneous release. In this case, we are doing
the same idea :-)
How does eclipse manage it's issue tracker?
As Max has explained what simultaneous release means to Eclipse guys what we are looking
for, I would propose we use this term in Seam as well.