maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simone Tripodi <simonetrip...@apache.org>
Subject Re: [VOTE] Release Maven Skins version 6
Date Sun, 08 Jan 2012 12:42:50 GMT
Hi Dennis!

thanks for your help, very appreciated!

Do we have to cancel the actual vote, then cutting a new RC?
Thanks again,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Sun, Jan 8, 2012 at 12:18 PM, Dennis Lundberg <dennisl@apache.org> wrote:
> Hi Simone!
>
> I have split up the parent POM into two separate POMs now. Jenkins is
> happy about it :)
>
> The process for releasing more than one skin in the same release vote
> would look something like this:
>
> 1. Release maven-skins (the parent)
>   Important: do not close the staging are in Nexus!
> 2. Release skin A
>   Important: do not close the staging are in Nexus!
> 3. Release skin B
>   Important: do not close the staging are in Nexus!
> .
> repeat for as many skins as you want to release
> .
> N. Close the staging area in Nexus
>
>
> On 2012-01-07 21:03, Simone Tripodi wrote:
>> Hi Dennis!
>>
>> I thought it would have been releasing all skins in one shot since
>> Robert (especially) and I fixed issues that affected all skins, I
>> completely agree anyway about your considerations on SVN tags - any
>> idea how to fix current situation? I would be glad to work on it!
>>
>> Thanks for reviewing!
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> On Sat, Jan 7, 2012 at 8:15 PM, Dennis Lundberg <dennisl@apache.org> wrote:
>>> Hi Simone
>>>
>>> Thanks for your efforts on the new Fluido Skin.
>>>
>>> We have not released all the skins together like this before. A skin
>>> release is like a plugin release, it's done once for each skin. Then
>>> there is the skin-parent which also has it's own release cycle.
>>>
>>> When I look in SVN for skins:
>>> http://svn.apache.org/viewvc/maven/skins/tags/
>>>
>>> I only see one tag for all of the releases you propose, skins-6. In your
>>> case it does seem that all skins have had changes since their last
>>> respective release, but that is usually not the case. This will mean
>>> that it is very difficult to find the tag for a particular release of
>>> say the Fluido skin. How do I know that Fluido Skin 1.1 is in Skins 6,
>>> just by looking in SVN?
>>>
>>> It would still be possible to release all skins in one vote, by using
>>> the same staging area in Nexus for all of them, including the release of
>>> the skins parent.
>>>
>>> However I feel strongly that each released skin should have its own tag
>>> in SVN. So I'm -1 on the vote for now.
>>>
>>>
>>> We should probably change the skins-parent to something like we have for
>>> plugins, for this reason. One parent, which is used to inherit common
>>> configuration from and then another aggregator-pom that can be used to
>>> build all skins together in a CI-environment. At present these two
>>> functions are the same POM.
>>>
>>>
>>>
>>> On 2012-01-06 21:50, Simone Tripodi wrote:
>>>> Hi all guys,
>>>> I am here to propose the Maven Skins version 6, that includes
>>>>  * Maven Application Skin 1.0 * Maven Default Skin 1.1 * Maven Classic
>>>> Skin 1.1 * Maven Stylus Skin 1.4 * Maven Fluido Skin 1.1
>>>> We solved 16 issues:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%20=%20MSKINS%20AND%20fixVersion%20in%20(%22fluido-1.1%22,%20%22application-1.0%22,%20%22default-1.1%22,%20%22stylus-1.4%22,%20%22classic-1.1%22)%20ORDER%20BY%20component,%20key
>>>> There is still one issues left in
>>>> JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%20=%20MSKINS%20AND%20status%20=%20Open
>>>> Staging repo:https://repository.apache.org/content/repositories/maven-024/
>>>> Staging sites:http://maven.apache.org/skins/maven-application-skin-1.0/http://maven.apache.org/skins/maven-default-skin-1.1/http://maven.apache.org/skins/maven-classic-skin-1.1/http://maven.apache.org/skins/maven-stylus-skin-1.4/http://maven.apache.org/skins/maven-fluido-skin-1.1/
>>>> A special acknowledgment goes to Robert Scholte who provided a
>>>> priceless support. Dank je wel!
>>>> Vote open for 72 hours and closes on January 9th, at ~8:45pm CET.
>>>> [ ] +1 release it[ ] +0 go ahead I don't care[ ] -1 no, do not release
>>>> it because
>>>> Thanks in advance for reviewing!
>>>> -Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Dennis Lundberg
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message