On Thursday, January 6, 2011 6:29:32 AM UTC-8, James Bennett wrote:
>
> It'd also be a major
> maintenance/bookkeeping headache and, I think, *more* likely to result
> in us accidentally crossing the streams while trying to keep track of
> what goes on in which branch.
>
I have the same concern here. With an A.B.C.D system my concern is that a
lot of people would simply be confused. It'd be confusing enough for the
core team to manage, let alone trying to explain it to users.
> Personally, I'd be in favor of keeping the overall release process
> as-is -- one release branch, which gets all bugfixes while applicable,
> plus highlighting the individual security patches as released -- and
> providing better documentation of what the release branch really is
> (i.e., not a security-only branch) and how to pull just a security
> update if that's what you want.
>
+1 on that. As long as it's easy for people who *only* want the security
patches to get them without any other updates I think that's fine.
>From a slightly more philosophical point of view, I'll add two other points
of consideration:
1) Even security patches can introduce regressions, so creating a
security-fix only branch doesn't inherently provide a regression-free
branch; it only make it less likely by decreasing the number of changes
which could potentially contain a bug.
2) Any bug is a potential liability for a user. While the bugs that are
serious enough to trigger security releases are more urgent, there is a
statistical net gain to having all the fixes included in the branch. While
it's psychologically frustrating to a user to upgrade and be faced with a
new regression that was previously unknown, from a purely mathematical
standpoint you're actually better off in the aggregate.
All that is to say that a 1.2.5 release is completely appropriate and I'm +1
for it, and I think it's better to continue as we have and be as responsive
and responsible as possible when new regressions are found.
That's my two cents,
- Gabriel
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
