How about some basics:

MD5 and SHA1 of each artifact involved.

Codehaus kingpins, how about making this a requirement if something doesn't
go through on the first cut?

It's just unprofessional to not do this, and not change the version, at the
same time.

Fred.

On Mon, Mar 18, 2013 at 11:13 PM, Baptiste Mathus <[email protected]> wrote:

> Hi,
>
> I'd like to release version *1.0-alpha-4* of the 
> *extra-enforcer-rules*project.
> Note that this is the third try. So, please don't forget to delete your
> local version if you already tried the previous release attempt.
>
> Extra Enforcer Rules is a project containing extra rules for Apache
> Maven's Enforcer Plugin.
>
> We solved 7 issues:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=18450
>
> There are still a couple of issues left in JIRA:
>
> https://jira.codehaus.org/issues/?jql=project%20%3D%20MOJO%20AND%20component%20%3D%20extra-enforcer-rules%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
> Staging Repositories:
> General:  https://nexus.codehaus.org/content/groups/staging/
> Exclusive:
> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-036/
>
> (Staging) Site:
> http://mojo.codehaus.org/extra-enforcer-rules/
>
> SCM Tag:
> https://svn.codehaus.org/mojo/tags/extra-enforcer-rules-1.0-alpha-4/
>
> Note that this version includes two new rules:
>
>    - enforcerBytecodeVersion : rule to check that bytecode of
>    dependencies is not higher than expected
>    - banCircularDependencies : rule to prevent having circular
>    dependencies
>
>
>  [ ] +1
>  [ ] +0
>  [ ] -1
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
> Cheers
>
> --
> Baptiste
>

Reply via email to