incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cory Johns <>
Subject Re: How do we handle an Incubator release
Date Tue, 06 Aug 2013 14:38:23 GMT
I think so.  We have a rat build passing on Jenkins, and the license issues
are all resolved, Dave has access to to set up the
directory and upload the file, Dave and I have keys ( and
that should be ok for signing (though mine needs a bit of
building up on the web of trust), and there are no other hurdles that I can
come up with to creating a tarball of the Allura source, signing it, and
putting it up.

For release docs, we will want to create an initial skeleton CHANGELOG.  We
also discussed changing README.markdown to INSTALL.markdown and creating a
separate README file.  We also have the generated docs up at

Is there anything else I'm missing?

On Tue, Aug 6, 2013 at 9:49 AM, Rich Bowen <> wrote:

> On 08/05/2013 03:01 PM, Peter Hartmann wrote:
>> 2013/8/5 Rich Bowen <>
>>  On 07/25/2013 08:27 PM, Dave Brondsema wrote:
>>>  I'm not aware of any blockers.  I think it might be nice to rename our
>>>> README to INSTALL, and create a README which is a short summary of what
>>>> Allura does, plus a URL or two for folks to find more info.  I don't
>>>> think
>>>> its critical though.
>>>>  How are we going on this? Are we going to be able to have a release by
>>> our
>>> next board report?
>>>  We may try. When is it coming?
that we reported in March - looks like we also reported in June -
but the page hasn't been updated. So we report in September. That gives
> us one month from today, roughly, to do this. Doable?
> --
> Rich Bowen
> Shosholoza

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message