Hi Pierre,
On 8/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
I had a simple question about the milestone you want to setup. When you
are talking about the "milestone" what do you really means by this? As far
as what I'm understanding by this and my little knowledge on projet
development; will this mostly translates into a *snapshot* or a *tag* in
the SVN repository associated with all the files at the current milestone
so it will be possible to check-out all the projet as it was when the
milestone was created?
yes, the goal is to create a brunch, provide release candidate and tag
it, after all is fine.
We call it milestone, not a real release, b/c it's a common thing for
Apache Incubator project to have *milestones* instead of releases.
Projects like Geronimo or MyFaces used this pattern successfully.
In other word, could you clarify / confirm the use of milestone?
You mean should users use the M1 in their production?
And if my understanding is correct, then I would also agree that with the
renaming / repackaging from ADF-faces to Trinidad (along with the fews
patches that were commited since may/june/july incubation) the milestone
would be approriate.
Good to hear; the patches are against the *old* namespace/package, right?
Any chance to overhaul them?
I have only 1 small concerns tought, before the milestone is done, there
was a new component added by Simon about the outputDocument, and there is
still
https://issues.apache.org/jira/browse/ADFFACES-86
opened concerning this component, maybe it would be useful to
commits/closes the issues since the component will likely be in the
milestone released?
we'll look into it. Raising up issues like this was one goal of my email too;
thanks for participating!
-Matthias
thanks!
Pierre-Luc Archambault
Fujitsu Consulting
"Joseph Rozier" <[EMAIL PROTECTED]> a écrit sur 2006-08-01 11:55:42
:
> Matthias,
>
> A milestone at this point seems reasonable to me.
>
> Do we have an expected time-between-milestones? For example, are we
> targetting a once-monthly/bimonthly/etc. milestone, or will milestones
> only come along when the consensus is they are needed?
>
> Thanks,
>
> Joey
>
> On 8/1/06, Matt Cooper <[EMAIL PROTECTED]> wrote:
> > Hi Matthias,
> >
> > It seems appropriate to me that all of the work you have done for
> > refactoring/renaming is good for a milestone. I am curious though,
what are
> > the benefits/implications (if any) of having a milestone release at
this
> > point? I do not see a need to couple the plug-ins and main source; so
> > releasing them independently would be okay.
> >
> > Thanks,
> > Matt
> >
> > On 7/31/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi folks,
> > >
> > > since the major refactoring and renaming tasks are almost done, I
> > > think it's time to think about releasing a first milestone version.
> > >
> > > Two things just out of my mind:
> > >
> > > 1. The release from plugins and trinidad should be independend.
> > > 2. w/ plugins we can start sooner than trinidad itself, b/c trinidad
> > > consumes the artifacts, provided from plugins.
> > >
> > > What are you general feelings about a release at this time?
> > >
> > > I think we are good in the game, because since the middle of May
(the
> > > initial commt), there was a lot's of development ongoing. The
> > > community is also growing; thanks to all how participating.
> > >
> > > What about the release number?
> > >
> > > From another incubator "release request" I learned that something
like
> > > "0.1.0-incubator" is fine. Currently we have something like
> > > "incubator-alpha-8" (just to give a sample). Maybe we should add a
> > > number to the "-incubator" string?
> > >
> > > Btw. I added the "Plugins" category to our Jira instance, to keep
> > > better track off all plugin related issues. Currently there is only
> > > one listed (see [1]).
> > >
> > > Thanks,
> > > Matthias
> > >
> > >
> > > [1] http://tinyurl.com/ed33c
> > > --
> > > Matthias Wessendorf
> > >
> > > further stuff:
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
> >
--
Matthias Wessendorf
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
