Hello. Can we copy trunk -> dist for the release, so we don't block any new development because of the release? There was the point of dist, even if we forgot it completely. Cheers, fijal
2010/3/1 Maciej Fijalkowski <fijall@gmail.com>:
Hello.
Can we copy trunk -> dist for the release, so we don't block any new development because of the release? There was the point of dist, even if we forgot it completely.
Maybe we should copy it to branch/release-1.2maint or some such name? We could back port critical bug fixes. -- Regards, Benjamin
This is already done. However, I wonder what's the purpose of dist. On Tue, Mar 2, 2010 at 2:46 PM, Benjamin Peterson <benjamin@python.org> wrote:
2010/3/1 Maciej Fijalkowski <fijall@gmail.com>:
Hello.
Can we copy trunk -> dist for the release, so we don't block any new development because of the release? There was the point of dist, even if we forgot it completely.
Maybe we should copy it to branch/release-1.2maint or some such name? We could back port critical bug fixes.
-- Regards, Benjamin
Hi Maciej, On Tue, Mar 02, 2010 at 02:51:33PM -0700, Maciej Fijalkowski wrote:
This is already done. However, I wonder what's the purpose of dist.
I'll copy from release/1.2.x into both release/1.2.0 and dist when we really do the release. That's supposedly the purpose of dist, I guess. A bientot, Armin.
participants (3)
-
Armin Rigo -
Benjamin Peterson -
Maciej Fijalkowski