+1

On Jan 11, 2006, at 1:31 PM, Daryl Olander wrote:

+1

On 1/10/06, Carlin Rogers <[EMAIL PROTECTED]> wrote:

+1

On 1/10/06, Steve Hanson <[EMAIL PROTECTED]> wrote:

+1

On 1/10/06, Rich Feit <[EMAIL PROTECTED]> wrote:

+1

Chad Schoettger wrote:

+1

On 1/10/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote:


 And, my +1.


On 1/10/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote:


All--

 Seems that there is general consensus in doing a 1.0.1 patch
release
to 1.0 in the very near future.  This mail is the vote to start
that
process and includes the following actions:

- Call the release 1.0.1
- Add a 1.0.1 Release to JIRA
- Re-categorize a set of bugs to fix in the 1.0.1 release into this
category.  (Am guessing this will be 3-5 of these that we decide
land
in 1.0.1).
- Plan to release in the next 2-3 weeks

Please vote (PMC members, especially) on this in the next 72 hours;
the vote will run until 4PM GMT 1/13/2006.

Vote early, vote once.  Thanks!

Eddie

Vote:
[+1] Yes, take the action items above to start a 1.0 patch release


called 1.0.1.


[0]  Abstain / not sure.
[-1] No, there is an issue with a 1.0.1 release or the stated
action
items.  If you vote this way, please explain why and what can be
done
to address your concerns.





-----Original Message-----
From: Eddie O'Neil [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 07, 2006 6:17 PM
To: Beehive Developers
Subject: [proposal] do a 1.0 patch release

All--

 Since we released 1.0 in October, we've been mostly doing


cleanup


and bug fixing. This has squashed about 70 (rough count) or so


bugs,


added some new documentation, and committed the controls test
container. In an effort to deliver these changes in a release,


I'd


like to propose that we move to release a patch release of


Controls +


NetUI in the next few weeks.

Specifics:
release number: 1.0.1
release date: targeted around January 27th (or so)
contains: already completed bug fixes and anything we identify
in


the


next week or so that is high enough priority to fix before
release

Additionally, this release would require the following actions: - renaming the "1.1" release to "1.0.1" to denote a patch to the


1.0


release. All of the work we've done in 1.1 is just bug fixing,
so
this seems like the right thing to do.
- review all of the remaining bugs for those we will try to fix
in


the


next couple of weeks

Comments / flames? Depending on the discussion over the next


couple


of days, I'll start a vote next week to capture agreement on


moving


toward a release.

Eddie
















Reply via email to