vUDS Scheduling

[Scott Kitterman]

I agree it's better to do it in public.  I'm surprised it's enough effort to be 
worth a vUDS, but if it is, it is.

Scott K

On Monday, August 19, 2013 18:45:33 Daviey Walker wrote:
> Hi Scott,
> 
> I can only speak on behalf of the Cloud and Server track, but I'd like
> to clarify how we intend to use this.  Unlike a start-of-cycle vUDS,
> this is a midcycle checkpoint opportunity.
> 
> The purpose of this, is to drive existing blueprints to completion.
> 
> This is an chance for those involved in Cloud and Server to do a
> 'show-and-tell' of blueprints defined 3 months ago.  We can evaluate
> decisions made then, check if assumptions were correct, anything we
> feel needs to be re-addressed and some re-scoping.  Very little (if
> any), new work should come from this.
> 
> The Canonical Server team previously did this same exercise but at an
> internal-only mid-cycle sprint.  This is largely the same thing, but
> out in the open.  THIS i am a big fan of and I am sure you are also
> supportive of this.
> 
> Personally, I think the timing to clash with feature freeze lends
> itself nicely.  This is the time that blueprints should be de-scoped
> if they are clearly not on track with features, and anything we
> /really/ need to see this cycle - can be considered very carefully
> with risk mitigation.
> 
> If you have any questions about this, please feel free to give me a shout.
> 
> > I agree that this is useful for Canonical upstreams trying to map out
> > their
> > next three - six months' work.  From a distro development perspective, not
> > so much.  I would hope there's a look beyond the next three months.  By
> > starting to plan for 14.04 now, they'll be in a much better position to
> > understand what needs doing and when to land things in the archive on a
> > timely basis.
> > 
> > Scott K
> > 
> > On Monday, August 19, 2013 12:15:45 Rick Spencer wrote:
> >> For Ubuntu touch, at least, there is a lot to figure out and do before
> >> shipping 13.10. Personally, I think it would be most beneficial to do
> >> that planning and have those discussions transparently and in an
> >> organized manner.
> >> 
> >> Cheers, Rick
> >> 
> >> On Mon, Aug 19, 2013 at 11:58 AM, Scott Kitterman <ubuntu at kitterman.com>
> > 
> > wrote:
> >> > On Monday, August 19, 2013 10:52:18 Ted Gould wrote:
> >> >> On Mon, 2013-08-19 at 10:05 -0400, Michael Hall wrote:
> >> >> > UDS August 2013
> >> >> > Starts: Tue, 27 Aug 2013 14:00:00 UTC
> >> >> > Ends: Thu, 29 Aug 2013 20:00:00 UTC
> >> >> 
> >> >> Are we putting vUDS the three days before feature freeze?
> >> >> 
> >> >> https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
> >> >> 
> >> >> Seems like bad time for people working on Ubuntu.
> >> > 
> >> > I think that is generically true for the mid-cycle vUDS.  This is no
> >> > doubt
> >> > worse than it might be, but it's a bit early to start planning the next
> >> > Ubuntu release cycle.  Whoever it's for, I don't think it's for people
> >> > working on Ubuntu.
> >> > 
> >> > Scott K
> >> > 
> >> > --
> >> > ubuntu-devel mailing list
> >> > ubuntu-devel at lists.ubuntu.com
> >> > Modify settings or unsubscribe at:
> >> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
> > 
> > --
> > ubuntu-devel mailing list
> > ubuntu-devel at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel