All,

I have completed the following

[x] remove voting requirements from ReleaseChecklist wiki page
[x] update Maven plugin dependency versions
[x] release the contents of branches/release-1.3 as version 1.3.2-rc1
[x] release the contents of trunk as version 2.0-rc1
[x] release the contents of branches/3.0-spike as version 3.0-beta1-rc2

In one week if there are no issues with the release candidate
versions, I will release the actual versions (1.3.2, 2.0, and
3.0-beta1) and then continue with

 - branch trunk to branches/release-2.0
 - merge branches/3.0-spike to trunk
 - release the contents of trunk as version 3.0-beta1

If anyone thinks that I should just cut 3.0 at that time instead of
3.0-beta1 I would be fine with that too.

   michael



On Thu, Nov 21, 2013 at 4:51 PM, Michael Heuer <[email protected]> wrote:
> All,
>
> I would like to propose removing the voting requirements from the
> Piccolo2D release process
>
> "Votes from Piccolo2D project committers are binding, however votes
> from other contributors and users are welcomed.  The vote must receive
> at least three +1 binding votes and no -1 binding votes."
>
> http://code.google.com/p/piccolo2d/wiki/ReleaseChecklist
>
> I was not able to recruit the necessary number of votes in April and
> the number of active committers has not improved since then.
>
> I will proceed-until-veto starting next week with the following:
>
>  - remove voting requirements from ReleaseChecklist wiki page
>  - update Maven plugin dependency versions
>  - release the contents of branches/release-1.3 as version 1.3.2
>  - release the contents of trunk as version 2.0
>  - branch trunk to branches/release-2.0
>  - merge branches/3.0-spike to trunk
>  - release the contents of trunk as version 3.0
>
> Then at that point I may import trunk into a github repository and
> continue development on version 3.x there.
>
> Now would be a good time to raise objections.
>
>    michael
>
>
> On Fri, Apr 19, 2013 at 4:41 PM, Michael Heuer <[email protected]> wrote:
>> All,
>>
>> I was afraid this might happen . . .  we don't have much going on with
>> Piccolo2D these days and I probably won't be able to find three active
>> committers to vote on a release.
>>
>> Since this is not the most significant release, just a release
>> candidate for a beta, I propose to proceed-until-veto next week.
>>
>>    michael
>>
>>
>> On Wed, Apr 10, 2013 at 3:59 PM, Michael Heuer <[email protected]> wrote:
>>> On Wed, Apr 10, 2013 at 3:58 PM, Michael Heuer <[email protected]> wrote:
>>>> This is a vote for releasing Piccolo2D.Java 3.0-beta1 based on release
>>>> candidate rc1 (version 3.0-beta1-rc1).
>>>>
>>>> 3.0-beta1-rc1 is available from the Maven central repository (or will
>>>> be shortly) at e.g.
>>>>
>>>> <dependency>
>>>>   <groupId>org.piccolo2d</groupId>
>>>>   <artifactId>piccolo2d-core</artifactId>
>>>>   <version>3.0-beta1-rc1</version>
>>>> </dependency>
>>>>
>>>>
>>>> ---------------
>>>> [X] +1  I support this release
>>>> [ ] +0
>>>> [ ] -0
>>>> [ ] -1  I oppose this release because...
>>>> ----------------
>>>
>>>    michael

-- 
-- 
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Piccolo2D Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to