I guess the plan should be:
* release discussions: done by this thread
* prepare the release: mvn release:prepare which tags the code
* make the release: mvn release:perform which pushes (signed)
artifacts to repository.apache.org
* stage the generated Maven documentation
* propose a vote on this list: mail should include the urls and the
closed/left issues.
* ask Incubator PMC for the release
* publish and announce the release

Anything else?

If everybody is agree with this plan, I could try to start the process
this week.

Cheers,

Vincent

2009/4/13 Ian Boston <[email protected]>:
> Being a release newbie with a desire to step into the unknown, what needs to
> be done ?
> presumably, build some artifacts, sign them, put them somewhere, agree that
> they should be the release, and then tell the incubator list we want to
> release them ?
>
> Ian
>
> On 13 Apr 2009, at 21:52, Kevin Brown wrote:
>
>> None of those 3 issues are actually release blockers. No feature request
>> is
>> ever a release blocker unless that feature was explicitly identified as
>> critical for the release at the beginning.
>>
>> On Mon, Apr 13, 2009 at 1:39 PM, Adam Winer <[email protected]> wrote:
>>
>>> I don't think we should wait for any of those issues.  Release, and
>>> release again.
>>>
>>> -- Adam
>>>
>>>
>>> On Mon, Apr 13, 2009 at 1:20 PM, Vincent Siveton <[email protected]>
>>> wrote:
>>>>
>>>> Hi Ian,
>>>>
>>>> 2009/4/13 Ian Boston <[email protected]>:
>>>>>
>>>>> I hate to bring it up again, but is it time to do a release on the
>>>>> 1.0.x
>>>>> branch ?
>>>>
>>>> I am agree with you.
>>>> According Jira [1], we have 3 issues left and according the board
>>>> report, we plan to do a release of 1.0.x in this quarter.
>>>> So, could we fix them and make a release soon? Ping me if devs need
>>>> help.
>>>>
>>>> Cheers,
>>>>
>>>> Vincent
>>>>
>>>> [1]
>>>
>>>
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310741&fixfor=12313553
>>>>
>>>
>
>

Reply via email to