-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 28, 2008, at 4:56 PM, Fred Drake wrote:
> On Jan 28, 2008, at 4:47 PM, Barry Warsaw wrote:
>> The problem is that I make separate releases of the standalone email
>> package from these branches, so that means that email 3.0.3 or 2.5.10
>> will
> Releasing the email package from the Python maintenance branches is
> probably insane.
People seem to use a lot of strong language lately.
>From m-w.com:
insane (adjective)
1. mentally disordered
3. absurd == ridiculously unreasonable
> This kind of thing would be less of a problem if the st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2008, at 1:01 AM, Martin v. Löwis wrote:
>> What do you think of the above?
>
> Sounds fine to me. I won't touch this then for the moment,
> please let me know when you are done rearranging things.
All done! Thanks.
- -Barry
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2008, at 1:01 AM, Martin v. Löwis wrote:
>> What do you think of the above?
>
> Sounds fine to me. I won't touch this then for the moment,
> please let me know when you are done rearranging things.
Cool, I'll try to get to this today.
- -B
> What do you think of the above?
Sounds fine to me. I won't touch this then for the moment,
please let me know when you are done rearranging things.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 28, 2008, at 5:08 PM, Martin v. Löwis wrote:
> Would it help if I branch
> branches/release23-maint/Lib/email to branches/email-2.3 ?
> Or should I branch the entire release23-maint to email-2.3?
> (branches are cheap in subversion)
> (*)
I ju
> The problem is that I make separate releases of the standalone email
> package from these branches, so that means that email 3.0.3 or 2.5.10
> will have regressions.
>
> Unless you're offering to also re-apply these changes after you make the
> Python releases .
If they are there primarily to
On Jan 28, 2008, at 4:47 PM, Barry Warsaw wrote:
> The problem is that I make separate releases of the standalone email
> package from these branches, so that means that email 3.0.3 or 2.5.10
> will have regressions.
Releasing the email package from the Python maintenance branches is
probably i
On Jan 28, 2008 1:47 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis wrote:
> >> If the intent is really to do a source-only releases mostly for system
> >> vendors, then I don't see the harm in leaving those changes in. I mean,
> >> a vendor is going to cherry pick the ones they wan
Martin v. Löwis wrote:
>> If the intent is really to do a source-only releases mostly for system
>> vendors, then I don't see the harm in leaving those changes in. I mean,
>> a vendor is going to cherry pick the ones they want anyway, so let's
>> just make it easy for them to do this. That might
> If the intent is really to do a source-only releases mostly for system
> vendors, then I don't see the harm in leaving those changes in. I mean,
> a vendor is going to cherry pick the ones they want anyway, so let's
> just make it easy for them to do this. That might mean publishing the
> svn l
On Jan 27, 2008 5:11 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Jan 27, 2008, at 2:27 PM, Martin v. Löwis wrote:
>
> > Along with the release of 2.5.2, I would also like to release
> > new versions of 2.3 and 2.4. These will be security-only releases,
> > and include a few security-relevant b
On Sun, Jan 27, 2008 at 08:27:27PM +0100, "Martin v. Löwis" wrote:
> For 2.3, there are only few revisions that would be rolled back:
> r52798, r52803, r52824, r54342.
These changes can be reverted if you like; they were added for
Jython's sake, but it looks like they've now decided to skip direct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 27, 2008, at 2:27 PM, Martin v. Löwis wrote:
> Along with the release of 2.5.2, I would also like to release
> new versions of 2.3 and 2.4. These will be security-only releases,
> and include a few security-relevant bug fixes that are still bei
On Jan 27, 8:27 pm, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Along with the release of 2.5.2, I would also like to release
> new versions of 2.3 and 2.4. These will be security-only releases,
> and include a few security-relevant bug fixes that are still being
> finalized.
>
> As we don't hav
Along with the release of 2.5.2, I would also like to release
new versions of 2.3 and 2.4. These will be security-only releases,
and include a few security-relevant bug fixes that are still being
finalized.
As we don't have the infrastructure to produce full releases of 2.3
or 2.4 anymore, this wi
16 matches
Mail list logo
