One of the key questions of that threat was, were the incubator
release should be hosted
<snip>
Incubator code should not be on www.apache.org/dist. Only official ASF
releases are permitted to be there. Our stuff should be under
people.apache.org/dist/incubator/${podling}.
Remember: we're not trying to make Incubator code *too* widely available.
Only very committed users should be touching it at all.
</snip>
Which makes sense to me; Something like
"people.apache.org/dist/incubator/${podling}" has the character of a
SNAPSHOT, since this here is all under incubation and not a fully
adopted Apache project yet.
With Maven no big deal to add a repository;
"people.apache.org/dist/incubator/" will not be mirrored via ibiblio
-Matthias
On 8/1/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
That came up on the "maven repo for incubator" thread.
<snip>
It is not the goal of the Apache software foundation to have Incubator
code *too* widely available. The Incubator is a firewall between ASF
and Incubator code ... And if people don't start respecting that, we
may find that the voices asking to push the Incubator to an entirely
separate domain win out, which I would consider a bad thing.
</snip>
Since having a *deep* involvment in this podling, I am reading
carefully most of the general@incubator.apache.org list.
That <snip/> is also my key behind the statement for doing not to
often a release.
-Matthias
On 8/1/06, Adam Winer <[EMAIL PROTECTED]> wrote:
> On 8/1/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> >
> > Hi Joey,
> >
> >
> > > 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?
> >
> > That is a good question; though we should not do releases to often.
>
>
> I'd like to see milestone releases about once a month or so.
>
> The general goal behind the milestone releases should be
> that people can depend on a specific version instead of
> always having to download snapshots. For example,
> a team developing against Trinidad can make sure
> everyone on the team is using the same version, which makes
> testing much easier.
>
> It also means we can close bugs as fixed in a version,
> so people will know when fixes are available.
>
> The release will also *not* be available from the main Apache maven
> > repository, only from the snapshot repository.
>
>
> Is this an Apache rule? These really should not be in the
> snapshot repository, at least by Maven rules, because this
> will not be a snapshot Maven release - there'll be a real
> version number and a real tag in Subversion.
>
> -- Adam
>
>
> I have not really
> > thought about the *timeframe* between the releaes; I'd be very happy
> > to one first out :)
> >
> > Regards!
> > Matthias
> >
> > > 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
> >
>
>
--
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
