So I will run thru all JIRAs fixed on 3.1.1, see if there is some blocker, compare with git log...
Then I will follow the procedure in order to prepare a release to be voted Is it thw right approach? Thank you Enrico Il sab 22 dic 2018, 16:12 Karl Heinz Marbaise <[email protected]> ha scritto: > Hi Enrico, > > take a look here: > > > https://maven.apache.org/developers/release/maven-project-release-procedure.html > > Kind regards > Karl Heinz Marbaise > On 22/12/18 14:09, Enrico Olivelli wrote: > > Hi, > > I am interested in having a release for the Maven Assembly plugin. > > I will have some time during this end-of-year period. > > > > There are a few JIRAs open, some of them are already assigned > > > > In particular I am interested in releasing the fix for: > > https://issues.apache.org/jira/browse/MASSEMBLY-861 > > > > which I found to be a duplicate of this one, already committer to master > branch > > https://issues.apache.org/jira/browse/MASSEMBLY-675 > > > > I would be a good change to learn the release procedure for Maven plugins > > > > I found this doc, but it does not talk about "plugins", only "Core" > > and "Parent POM" > > https://maven.apache.org/developers/release/index.html > > > > > > Cheers > > Enrico > -- -- Enrico Olivelli
