Conclusions from user survey

[Daniel Fetchinson]

This is a message to the developers since Ken asked us not to hijack
the user survey thread.

So, now that the survey results are in and has been summarized by Ken
(thanks a lot!), what are the long term consequences? More
specifically, what is the road map for the 1.x branch, if any at the
moment? Any official news on 1.5?

Cheers,
Daniel

--
Psss, psss, put it down! - http://www.cafepress.com/putitdown

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Ken Kuhlman]

On Mon, Nov 2, 2009 at 4:08 PM, Daniel Fetchinson <fetchinson@...> wrote:

This is a message to the developers since Ken asked us not to hijack
the user survey thread.

So, now that the survey results are in and has been summarized by Ken
(thanks a lot!), what are the long term consequences? More
specifically, what is the road map for the 1.x branch, if any at the
moment? Any official news on 1.5?

Cheers,
Daniel

Well, the first order of business was to catch 1.5 back up with 1.1.   That's done, with the exception of the failing test that I asked for help on yesterday.

Once that's fixed, someone (probably me) needs to propose goals for the release. When we have consensus on that, we can start putting out alpha releases.

You can view the open 1.5 tickets on our trac [1].  The 4 defects with a "high" priority are blockers to putting out a final release.  Also note that only the tickets with version of "1.5 HEAD" are for issues introduced in the 1.5 branch;  the others are carried-forward from previous releases.

What I personally took away from the survey was a desire to keep the 1.5 release small, so I intend to focus on documentation almost exclusively once the blockers are closed.

Thanks,
-Ken


[1]
http://trac.turbogears.org/query?status=!closed&group=type&milestone=1.5&order=priority

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Christopher Arndt]

On 3 Nov., 05:25, Ken Kuhlman <kskuhl...@...> wrote:
> On Mon, Nov 2, 2009 at 4:08 PM, Daniel Fetchinson <fetchin...@...
> Once that's fixed, someone (probably me) needs to propose goals for the
> release. When we have consensus on that, we can start putting out alpha
> releases.

I met with Christoph Zwerschke the day before yesterday and we talked
a bit about what we think should go into a TG 1.5 release. I agree,
that there shouldn't be too many new features, but there are some
issues, which we already planend for the TG 1.1 release, but nobody
found the time to do and I'd like to adress at least some of them for
TG 1.5.

I don't have my notes with me now, but I'll try write up our plans
tonight and publish them here. We initially intended to dicuss this
with Ken and the TG2 developers internally first, but I think it's no
harm doing this openly.

> What I personally took away from the survey was a desire to keep the 1.5
> release small, so I intend to focus on documentation almost exclusively once
> the blockers are closed.

On the other hand, I don't see much sense in keeping a TG 1 branch if
it doesn't evolve. That would be no fun to work on and without some
fun, nothing gets done.

Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Daniel Fetchinson]

>> Once that's fixed, someone (probably me) needs to propose goals for the
>> release. When we have consensus on that, we can start putting out alpha
>> releases.
>
> I met with Christoph Zwerschke the day before yesterday and we talked
> a bit about what we think should go into a TG 1.5 release. I agree,
> that there shouldn't be too many new features, but there are some
> issues, which we already planend for the TG 1.1 release, but nobody
> found the time to do and I'd like to adress at least some of them for
> TG 1.5.
>
> I don't have my notes with me now, but I'll try write up our plans
> tonight and publish them here. We initially intended to dicuss this
> with Ken and the TG2 developers internally first, but I think it's no
> harm doing this openly.
>
>> What I personally took away from the survey was a desire to keep the 1.5
>> release small, so I intend to focus on documentation almost exclusively
>> once
>> the blockers are closed.
>
> On the other hand, I don't see much sense in keeping a TG 1 branch if
> it doesn't evolve. That would be no fun to work on and without some
> fun, nothing gets done.

Thanks guys for the responses, it's good to know that 1.5 will be out
in the not too distant future. I also think that incremental small
changes are good, there is no need to wait for a huge new killer
feature before releasing 1.5. Even if a small 1.5 is out it will send
a powerful message that the 1.x branch is not dead and really cool new
complicated stuff can go in any time after that, 1.6, etc.

Cheers,
Daniel


--
Psss, psss, put it down! - http://www.cafepress.com/putitdown

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Ken Kuhlman]

On Tue, Nov 3, 2009 at 3:19 AM, Chris Arndt <chris.arndt@...> wrote:

On 3 Nov., 05:25, Ken Kuhlman <kskuhl...@...> wrote:
> On Mon, Nov 2, 2009 at 4:08 PM, Daniel Fetchinson <fetchin...@...

> Once that's fixed, someone (probably me) needs to propose goals for the
> release. When we have consensus on that, we can start putting out alpha
> releases.

I met with Christoph Zwerschke the day before yesterday and we talked
a bit about what we think should go into a TG 1.5 release. I agree,
that there shouldn't be too many new features, but there are some
issues, which we already planend for the TG 1.1 release, but nobody
found the time to do and I'd like to adress at least some of them for
TG 1.5.

I don't have my notes with me now, but I'll try write up our plans
tonight and publish them here. We initially intended to dicuss this
with Ken and the TG2 developers internally first, but I think it's no
harm doing this openly.

That's fantastic news!  If you guys agree on an agenda, then as far as I'm concerned we have our devplans.

 

> What I personally took away from the survey was a desire to keep the 1.5
> release small, so I intend to focus on documentation almost exclusively once
> the blockers are closed.

On the other hand, I don't see much sense in keeping a TG 1 branch if
it doesn't evolve. That would be no fun to work on and without some
fun, nothing gets done.

Chris

Right. I didn't mean to restrict anyone's fun too much.  I'm just saying that I've had my share & it's time for me to focus on a quality upgrade experience for the stuff I've done.

-Ken

 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---