You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2013/10/03 22:02:08 UTC
[allura:tickets] Re: #6422 make an Apache Allura release happen
Which commits in https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/heads/cj/6422 exactly are new since last time? (Might want to mention on the non-ticket email thread too)
The release script looks pretty good to me. I'd rather use `git archive` to make the zip file, rather than using a working copy & excluding files. Working copies could have other files that aren't noticed (hidden by local git ignore settings). Also there is a "1.0.0" hard coded in the email template.
Beyond that I think the script is good to go, the real test is in its usage.
I would like us to put together a 1.0.1 section in the CHANGES file before we run the script though. It'll be a good exercise even though 1.0.0 was never release (and maybe CHANGES should state that fact too)
---
** [tickets:#6422] make an Apache Allura release happen**
**Status:** code-review
**Created:** Fri Jun 28, 2013 02:49 PM UTC by Dave Brondsema
**Last Updated:** Thu Oct 03, 2013 06:19 PM UTC
**Owner:** Cory Johns
This is just for time tracking. Main ticket is [#6223]
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.