incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <>
Subject Re: when to do a next Allura release?
Date Mon, 13 Jan 2014 15:32:03 GMT
Blocking github-importer tickets
and are now closed, so we could
do a release with all the importers enabled now.

However I said [1] that we'd also remove a SourceForge reference on a repo page
before our next release, so I think we should do some work on


On 12/10/13 3:28 PM, Cory Johns wrote:
> Agreed.  Having all of our current importers enabled seems like a good spot
> to release, as does activity streams.
> I think we should try not to ever go more than 2 months without doing a
> release, and I might even say 1 release per month might be a good target
> though we can start with 2 and see how that goes.
> On Tue, Dec 10, 2013 at 2:36 PM, Dave Brondsema <> wrote:
>> How frequently do we want to make Allura releases?  Particularly when do
>> we want
>> to make our next one - but we can talk in general terms too.
>> I am thinking we should do one fairly soon.  It took a while to get our
>> first
>> release out, but we now have a release script which should help automate a
>> lot
>> and ensure we cover all the technical aspects.  And I think we'll be able
>> to get
>> the votes more easily now that we've gotten past the hurdle of the first
>> one.
>> Also, the Incubator PMC (IPMC) has voted & invited me to join the IPMC a
>> little
>> while ago, so I can cast a binding vote too.
>> In general, I'd suggest we make releases after certain significant
>> features are
>> done, or after a few months if we're doing many small/medium changes but
>> nothing
>> too big.  Lately we've done a lot of work around Google, Trac, and Github
>> importers.  IMO is a
>> blocker for
>> github, but after that is fixed might be a good time to release.  Another
>> big
>> ongoing initiative is activity streams, which might make a good 3rd
>> release).
>> --
>> Dave Brondsema :
>> : personal
>> : programming
>>               <><

Dave Brondsema : : personal : programming

View raw message