Subversion 1.5 Status Update

Well I think we can definitely see the light at the end of
the tunnel.
 We are down to 16 issues with the 1.5 milestone.  Of those,
7 are
STARTED so I think there are quite a few that will be
RESOLVED in the
days ahead.

Karl is pretty close to done on sparse directories.  Just a
few
lingering issues remain.

Merge tracking has had several big issues RESOLVED, such as
the new
merge algorithm that Kamesh committed.  I think Dan has some
concerns
about lingering edge cases that might show up.  Paul is
close to
committing a new API that will allow us to merge an
arbitrary set of
revisions.  Besides those there are a few other known issues
we need
to get wrapped up.

There is definitely some issues in the tracker that anyone
could step
in and knock off if you want to help.  There are also at
least a few
items being worked on that do not currently have the 1.5
milestone
attached, but will likely be done in time for release --
such as
relative externals.

It is hard to say at this point how we are doing in terms of
our goal
date of October 12th.  There has been so much activity the
last month
or so I imagine we are all a little concerned about overall
stability.
 That being said, I think that trunk builds are being used
by a lot
wider group of people than ever before, so I remain
optimistic that we
can stabilize for release in a good timeframe.

One thing that occurred to me recently was whether we have a
release
manager for this release.  Obviously it would be great if
danderson
intends to remain in this role, but I do not want to
volunteer him or
just assume he still wants the role.  So this is an area
where we
could possibly use a volunteer if we want to make progress
towards
release.

Finally, do we have a standard process for getting from
/trunk to the
/1.5.x branch and RC1?  It seems like we do this a little
differently
each release.  Given that I would still like to see us get a
GA out
before the end of the year, I'd vote for whatever we think
will give
us a quality RC1 release the fastest.  I tend to think
staying on
/trunk until we are ready to make the RC1 would do this as
long as we
are watchful of what is being committed until we make the
branch.
Anyway, I do not have any strong feelings on this.  I just
want to see
us continue to make progress towards the GA.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

PS - For those that are interested, here are some rough
issue tracking
numbers I have been keeping:

2007-09-06: 138 Total 37 Open (11 New, 10 Closed in previous
2 weeks)
2007-09-20: 146 Total 34 Open (7 New, 12 Closed in previous
2 weeks)
2007-10-04: 151 Total 16 Open (7 New, 23 Closed in previous
2 weeks)

These do not really capture issues that are moved in and out
of the
1.5 milestone, other than how they impact on the totals.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

"Mark Phippard" <markphipgmail.com> writes:
> There is definitely some issues in the tracker that
anyone could step
> in and knock off if you want to help.  There are also
at least a few
> items being worked on that do not currently have the
1.5 milestone
> attached, but will likely be done in time for release
-- such as
> relative externals.
>
> It is hard to say at this point how we are doing in
terms of our goal
> date of October 12th.  [...]

I think we're going to make Oct. 12th, but it would be great
if
someone could do a sweep of the "---"
(unmilestoned) issues in the
tracker.  It's usually best if one person does that, so they
can spot
dups quickly, etc.

I'd like to do it, but I feel I'd better work on
sparse-directories
right now... and of course, the closer to Oct. 12th the
"---" sweep
happens, the less able we would be to handle any surprise
discoveries.
So if someone wants to do it now, that'd be great. 
Otherwise, I'll
get to it when I can.

-Karl

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

On 10/4/07, Karl Fogel <kfogelred-bean.com> wrote:
> "Mark Phippard" <markphipgmail.com> writes:
> > There is definitely some issues in the tracker
that anyone could step
> > in and knock off if you want to help.  There are
also at least a few
> > items being worked on that do not currently have
the 1.5 milestone
> > attached, but will likely be done in time for
release -- such as
> > relative externals.
> >
> > It is hard to say at this point how we are doing
in terms of our goal
> > date of October 12th.  [...]
>
> I think we're going to make Oct. 12th, but it would be
great if
> someone could do a sweep of the "---"
(unmilestoned) issues in the
> tracker.  It's usually best if one person does that, so
they can spot
> dups quickly, etc.
>
> I'd like to do it, but I feel I'd better work on
sparse-directories
> right now... and of course, the closer to Oct. 12th the
"---" sweep
> happens, the less able we would be to handle any
surprise discoveries.
> So if someone wants to do it now, that'd be great. 
Otherwise, I'll
> get to it when I can.

I can tentatively volunteer (I'd rather you have more time
to help
code).  The tentative part is that I am not sure what the
job is.  I
guess I'd be looking for things that are now DONE with an
eye for any
1.5 blockers that we missed?  What do I do with everything
else
though?  Leave at --- or assign to 1.6-consider or what?

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

"Mark Phippard" <markphipgmail.com> writes:
> I can tentatively volunteer (I'd rather you have more
time to help
> code).  The tentative part is that I am not sure what
the job is.  I
> guess I'd be looking for things that are now DONE with
an eye for any
> 1.5 blockers that we missed?  What do I do with
everything else
> though?  Leave at --- or assign to 1.6-consider or
what?

The job is basically this:

   for i in issues_marked_as("---"):
      if issue_is_a_dup_of_some_other_issue(i):
        close_as_dup(i)
      elif issue_is_invalid(i):
        close_as_invalid(i)
      elif issue_already_fixed(i):
        close_as_fixed(i)
      elif issue_unreproducible(i):
        close_as_worksforme(i)
      elif issue_is_real_but_we_won't_fix_it(i):
        close_as_wontfix(i)
      elif issue_is_closeable_for_some_other_reason(i):
        close_as_it_for_that_reason(i)

      # Else issue should remain open, so DTRT with it...

      # Set priority, platform, subcomponent, whatever, as
needed.
      adjust_all_fields_that_need_adjustment(i)

      # Figure out where to put it.
      if
issue_is_not_important_enough_to_block_any_particular_releas
e(i):
        move_to_milestone(i, "nonblocking")
      elif
issue_resolution_would_require_incompatible_changes(i):
        move_to_milestone(i, "2.0")
      elif issue_hurts_people_somewhat(i):
        move_to_milestone(i, "1.6")  # or
whatever
      elif issue_hurts_people_a_lot(i):
        move_to_milestone(i, "1.5-consider")
      elif issue_hurts_and_hurts_and_won't_stop_hurting(i):
        move_to_milestone(i, "1.5")

-K

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

On Thu, 4 Oct 2007, Karl Fogel wrote:

> "Mark Phippard" <markphipgmail.com> writes:
>> There is definitely some issues in the tracker that
anyone could step
>> in and knock off if you want to help.  There are
also at least a few
>> items being worked on that do not currently have
the 1.5 milestone
>> attached, but will likely be done in time for
release -- such as
>> relative externals.
>>
>> It is hard to say at this point how we are doing in
terms of our goal
>> date of October 12th.  [...]
>
> I think we're going to make Oct. 12th, but it would be
great if
> someone could do a sweep of the "---"
(unmilestoned) issues in the
> tracker.  It's usually best if one person does that, so
they can spot
> dups quickly, etc.

Please have a look at #2791 which adds pipe support to
svn_io_start_cmd2 
and uses it run_hook_cmd.

Thanks
Martin


PS:
Issue URL: http://subversion.tigris.org/issues/show_bug.cgi?id=2791


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

On 10/4/07, Karl Fogel <kfogelred-bean.com> wrote:

>    for i in issues_marked_as("---"):
>       if issue_is_a_dup_of_some_other_issue(i):
>         close_as_dup(i)
>       elif issue_is_invalid(i):
>         close_as_invalid(i)
>       elif issue_already_fixed(i):
>         close_as_fixed(i)
>       elif issue_unreproducible(i):
>         close_as_worksforme(i)
>       elif issue_is_real_but_we_won't_fix_it(i):
>         close_as_wontfix(i)
>       elif
issue_is_closeable_for_some_other_reason(i):
>         close_as_it_for_that_reason(i)
>
>       # Else issue should remain open, so DTRT with
it...
>
>       # Set priority, platform, subcomponent, whatever,
as needed.
>       adjust_all_fields_that_need_adjustment(i)
>
>       # Figure out where to put it.
>       if
issue_is_not_important_enough_to_block_any_particular_releas
e(i):
>         move_to_milestone(i, "nonblocking")
>       elif
issue_resolution_would_require_incompatible_changes(i):
>         move_to_milestone(i, "2.0")
>       elif issue_hurts_people_somewhat(i):
>         move_to_milestone(i, "1.6")  # or
whatever
>       elif issue_hurts_people_a_lot(i):
>         move_to_milestone(i, "1.5-consider")
>       elif
issue_hurts_and_hurts_and_won't_stop_hurting(i):
>         move_to_milestone(i, "1.5")

Oh man, we should document this procedure somewhere.  

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

On 10/4/07, Karl Fogel <kfogelred-bean.com> wrote:
> "Mark Phippard" <markphipgmail.com> writes:
> > I can tentatively volunteer (I'd rather you have
more time to help
> > code).  The tentative part is that I am not sure
what the job is.  I
> > guess I'd be looking for things that are now DONE
with an eye for any
> > 1.5 blockers that we missed?  What do I do with
everything else
> > though?  Leave at --- or assign to 1.6-consider or
what?
>
> The job is basically this:
>
>    for i in issues_marked_as("---"):
>       if issue_is_a_dup_of_some_other_issue(i):
>         close_as_dup(i)
>       elif issue_is_invalid(i):
>         close_as_invalid(i)
>       elif issue_already_fixed(i):
>         close_as_fixed(i)
>       elif issue_unreproducible(i):
>         close_as_worksforme(i)
>       elif issue_is_real_but_we_won't_fix_it(i):
>         close_as_wontfix(i)
>       elif
issue_is_closeable_for_some_other_reason(i):
>         close_as_it_for_that_reason(i)
>
>       # Else issue should remain open, so DTRT with
it...
>
>       # Set priority, platform, subcomponent, whatever,
as needed.
>       adjust_all_fields_that_need_adjustment(i)
>
>       # Figure out where to put it.
>       if
issue_is_not_important_enough_to_block_any_particular_releas
e(i):
>         move_to_milestone(i, "nonblocking")
>       elif
issue_resolution_would_require_incompatible_changes(i):
>         move_to_milestone(i, "2.0")
>       elif issue_hurts_people_somewhat(i):
>         move_to_milestone(i, "1.6")  # or
whatever
>       elif issue_hurts_people_a_lot(i):
>         move_to_milestone(i, "1.5-consider")
>       elif
issue_hurts_and_hurts_and_won't_stop_hurting(i):
>         move_to_milestone(i, "1.5")

My hand is not raised quite as high up as it was before 

I'll start making a dent when I can.  With 124 issues I do
not think
anyone could just blow through it.  In the few I sampled it
looked
like Erik has done some work in engaging the user, he just
did not
change the settings.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

On 10/4/07, Dirkjan Ochtman <dirkjanochtman.nl> wrote:
> Mark Phippard wrote:
> > It is hard to say at this point how we are doing
in terms of our goal
> > date of October 12th.  There has been so much
activity the last month
> > or so I imagine we are all a little concerned
about overall stability.
> >  That being said, I think that trunk builds are
being used by a lot
> > wider group of people than ever before, so I
remain optimistic that we
> > can stabilize for release in a good timeframe.
>
> Question: there was a thread a while back about whether
the new
> python-ctypes bindings would go into 1.5. I didn't see
a resolution in
> that thread (and a quick search didn't bring one up in
another thread
> either), I asked around in #svn but nobody there knew
about this.
>
> So: will the aim be for the python-ctypes bindings to
be in 1.5?

I thought they were merged to trunk already.  If they are in
trunk
then they will be included.

-- 
Thanks

Mark Phippard
http://markphip.blogspo
t.com/

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org

On 10/5/07, Mark Phippard <markphipgmail.com> wrote:
> On 10/4/07, Dirkjan Ochtman <dirkjanochtman.nl> wrote:
> > Mark Phippard wrote:
> > > It is hard to say at this point how we are
doing in terms of our goal
> > > date of October 12th.  There has been so much
activity the last month
> > > or so I imagine we are all a little concerned
about overall stability.
> > >  That being said, I think that trunk builds
are being used by a lot
> > > wider group of people than ever before, so I
remain optimistic that we
> > > can stabilize for release in a good
timeframe.
> >
> > Question: there was a thread a while back about
whether the new
> > python-ctypes bindings would go into 1.5. I didn't
see a resolution in
> > that thread (and a quick search didn't bring one
up in another thread
> > either), I asked around in #svn but nobody there
knew about this.
> >
> > So: will the aim be for the python-ctypes bindings
to be in 1.5?
>
> I thought they were merged to trunk already.  If they
are in trunk
> then they will be included.

No, they are on their own "branch" (which isn't
actually a branch, but
separate directory under branches/ctypes-python-bindings).

--dave

-- 
David Glasser | glasserdavidglasser.net | http://www.davidglasser.
net/

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org