The extensions work will still be 2.0. We will either end up going from 1.6
to 2.0, or we'll package a bunch of GSoC/UCOSP work as 1.7 while working on
2.0.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


On Thu, Mar 24, 2011 at 11:20 PM, Jan Koprowski <jan.koprow...@gmail.com>wrote:

> Christian!
>
>  It is great news! 1.7 sounds better then 2.0 :) Thanks!
>
> Regards,
>
> On Fri, Mar 25, 2011 at 7:17 AM, Christian Hammond <chip...@chipx86.com>
> wrote:
> > Extensions are going to be the big focus once we get 1.6 out the door. A
> lot
> > of work has gone into it by many, many students through both UCOSP and
> GSoC,
> > so that'll continue :)
> >
> > Webhooks will end up being an exension. We had some work toward
> refactoring
> > it into an extension recently.
> >
> > Christian
> >
> > --
> > Christian Hammond - chip...@chipx86.com
> > Review Board - http://www.reviewboard.org
> > VMware, Inc. - http://www.vmware.com
> >
> >
> > On Thu, Mar 24, 2011 at 11:13 PM, Jan Koprowski <jan.koprow...@gmail.com
> >
> > wrote:
> >>
> >> Hi Christian,
> >>
> >>  I'm surprised You share my point of view. I agree with You that
> >> making something new is much more interesting then ending someone's
> >> work. Things I can't wait are:
> >>  * Kicked as Extensions with many, many, many hooks provided and well
> >> documented :D
> >>  * Cool webhooks sending also some data (objects) to given URL :P
> >>  * Planty of ReviewBoard-Django signals perfectly documented on
> >> docs.reviewboard.org :)
> >>
> >> That is probably all because this allow me to spice ReviewBoard by my
> >> own :) for my company :] and waiting for 2.0 since I get it drive me
> >> crazy :D
> >>
> >> Greetings from Poland.
> >>
> >> On Thu, Mar 24, 2011 at 9:27 PM, Christian Hammond <chip...@chipx86.com
> >
> >> wrote:
> >> > I quite agree. A lot of that needs to be finished up. For some of it,
> >> > we've
> >> > had students go and finish up the project (or at least get further on
> >> > it)
> >> > and we'll probably continue to do that.
> >> >
> >> > There's always, of course, the need to deliver an interesting project
> >> > that a
> >> > student can work on. Finishing up someone else's work is not nearly as
> >> > attractive as doing something new and exciting, so we need to do a bit
> >> > of
> >> > both, I think.
> >> >
> >> > Any specific branches you're wanting work done on?
> >> >
> >> > Christian
> >> >
> >> > --
> >> > Christian Hammond - chip...@chipx86.com
> >> > Review Board - http://www.reviewboard.org
> >> > VMware, Inc. - http://www.vmware.com
> >> >
> >> >
> >> > On Wed, Mar 23, 2011 at 10:42 PM, Jan Koprowski
> >> > <jan.koprow...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >>  Personally I will be glad if GSoC won't provide new features because
> >> >> there is too much cool stuff waiting on non-public branches I can't
> >> >> wait. IMHO this stuff wait too long and providing it to stable
> version
> >> >> should be the first goal.
> >> >>
> >> >> Regards,
> >> >>
> >> >> Jan
> >> >>
> >> >> On Thu, Mar 24, 2011 at 1:39 AM, Paul Schulz <p...@mawsonlakes.org>
> >> >> wrote:
> >> >> > Hi Christian,
> >> >> >
> >> >> > On Tue, Mar 22, 2011 at 6:49 AM, Christian Hammond
> >> >> > <chip...@chipx86.com>
> >> >> > wrote:
> >> >> >> Hey everyone,
> >> >> >>
> >> >> >> We've been accepted again this year in Google's Summer of Code, a
> >> >> >> yearly
> >> >> >> event where students from around the world participate in open
> >> >> >> source
> >> >> >> projects, developing work experience and getting paid for it.
> >> >> >
> >> >> > (snip)
> >> >> >
> >> >> >> We're also looking for ideas for projects, so if you have an idea
> >> >> >> for
> >> >> >> something awesome you'd like to see, just reply :)
> >> >> >>
> >> >> >> Thanks!
> >> >> >>
> >> >> >> Christian
> >> >> >
> >> >> > I work as a System Administrator for a large(ish) software
> >> >> > engineering
> >> >> > organisation and we are making use of and relying on ReviewBoard
> >> >> > extensively in our software development process.
> >> >> >
> >> >> > Thank you for your efforts so far. Working with the Engineers, I
> more
> >> >> > often hear about where the tool falls short, rather then about all
> >> >> > the
> >> >> > other really good things about ReviewBoard that actually works
> really
> >> >> > well.
> >> >> >
> >> >> > The this end, I did an internal survey and came up with the
> following
> >> >> > suggestions for feature improvements (see below).
> >> >> >
> >> >> > Thanks again for everyones efforts,
> >> >> > Paul
> >> >> >
> >> >> > ------------------------------------------
> >> >> > [Workflow]
> >> >> >
> >> >> > * Ship-it lockout or reset
> >> >> >
> >> >> > If the ship-it option has been selected, then no other
> changes/diffs
> >> >> > can be uploaded. Comments can still be made, or if a change to the
> >> >> > code is made, then the ship-it tags are removed.
> >> >> >
> >> >> > * Master Ship-it
> >> >> >
> >> >> > A reviewer (or group) with master ship-it power is all that is
> >> >> > required to designate that a patch be shipped.
> >> >> >
> >> >> > * Automated Ship-it patch submission
> >> >> >
> >> >> > If a patch is marked as ship-it, than commit it to the repository.
> >> >> > (All of the required information is available, including commit
> >> >> > comment.)
> >> >> >
> >> >> > * Explicitly separate Reviewers from Shippers
> >> >> >
> >> >> > A shipper is someone with shipping powers, a reviewer is someone
> who
> >> >> > is included in the review for comment.
> >> >> >
> >> >> > [Integration]
> >> >> >
> >> >> > * Bugzilla
> >> >> >
> >> >> > Add a bug report comment to a bug once a review has been completed.
> >> >> >
> >> >> > * Subversion
> >> >> >
> >> >> > Block a check in of a patch/changeset until a review has been
> >> >> > approved
> >> >> > (for some definition of approved).
> >> >> >
> >> >> > [Improvements]
> >> >> >
> >> >> > * Allow use of Full Name where usernames are displayed
> >> >> >
> >> >> > Reviewboard has access to full names, it should make more use of
> >> >> > them.
> >> >> >
> >> >> > --
> >> >> > Want to help the Review Board project? Donate today at
> >> >> > http://www.reviewboard.org/donate/
> >> >> > Happy user? Let us know at http://www.reviewboard.org/users/
> >> >> > -~----------~----~----~----~------~----~------~--~---
> >> >> > To unsubscribe from this group, send email to
> >> >> > reviewboard+unsubscr...@googlegroups.com
> >> >> > For more options, visit this group at
> >> >> > http://groups.google.com/group/reviewboard?hl=en
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> ><> Jan Koprowski
> >> >>
> >> >> --
> >> >> Want to help the Review Board project? Donate today at
> >> >> http://www.reviewboard.org/donate/
> >> >> Happy user? Let us know at http://www.reviewboard.org/users/
> >> >> -~----------~----~----~----~------~----~------~--~---
> >> >> To unsubscribe from this group, send email to
> >> >> reviewboard+unsubscr...@googlegroups.com
> >> >> For more options, visit this group at
> >> >> http://groups.google.com/group/reviewboard?hl=en
> >> >
> >>
> >>
> >>
> >> --
> >> ><> Jan Koprowski
> >
> >
>
>
>
> --
> ><> Jan Koprowski
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to