[Distutils] Annoucing distribute project

Matthias Klose doko at cs.tu-berlin.de
Wed Sep 24 13:49:01 CEST 2008


announcing a fork without any objective? what is this fork about? if
it stays 100% compatible, isn't it just more frequent releases?

  Matthias

Tarek Ziadé writes:
> Hi,
> 
> I am launching a fork of setuptools. The name is "Distribute". (not
> definitive) and will be community-driven
> 
> This fork will remain 100% compatible with setuptools, and follow closely
> setuptools evolutions.
> 
> Roadmap
> =======
> 
> - Distribute 0.1 (09/27/2008)
> 
> The first release of Distribute will be done at the end of this week,
> targeting setuptools 0.6x,
> and will provide all latest bugfixes done in the 0.6 branches of setuptools,
> like Subversion 1.5 compatibility.
> 
> - Distribute 0.2 (10/27/2008)
> 
> The 0.2 release will be done in 1 month, targeting setuptools current trunk,
> and will focus on
> providing a maximum of bugfixes. You can provide patches, or aks for a
> particular bug to be fixed.
> Use the launchpad bug tracker for that https://bugs.launchpad.net/distribute
> 
> - Distribute 0.3
> 
> The 0.3 release will contain new features and improvments, and its release
> date decide when 0.2 comes out.
> 
> Project managment
> ===============
> 
> Distribute is using launchpad (https://launchpad.net/distribute) and bzr and
> anyone that wants to
> contribute is welcome to provide a branch.
> 
> The branch are merged if they provide tests and if there is a consensus of
> the community
> on it.
> 
> The process is as follow for a contribution:
> 
> - create a bzr branch
> - talk about it on distutils-SIG, using [distribute] in the header, asking
> for review/merge
> - it is discussed in the mailing list
> - if no one objects, and if it has tests, it will be merged by a maintainer
> 
> I am the maintainer at this point but this role will be extended to other
> people that want to become
> a maintainer, so I will not become a botlleneck for this project.
> 
> A maintainer has to be nominated by 100% of the maintainers, and there will
> be at most
> 4 maintainers in this project. Maintainers are added or removed after each
> release.
> They work together to release the next milestone.
> 
> Let me know if you want to become a maintainer. Maintainers need to discuss
> their changes
> as well on the mailing list, and their only privilege is being able to merge
> branches on the main branch,
> because they are trust to do so.
> 
> Cheers
> Tarek
> 
> -- 
> Tarek Ziadé | Association AfPy | www.afpy.org
> Blog FR | http://programmation-python.org
> Blog EN | http://tarekziade.wordpress.com/
> <div dir="ltr">Hi,<br><br>I am launching a fork of setuptools. The name is &quot;Distribute&quot;. (not definitive) and will be community-driven<br><br>This fork will remain 100% compatible with setuptools, and follow closely setuptools evolutions.<br>
> <br>Roadmap<br>=======<br><br>- Distribute 0.1 (09/27/2008)<br><br>The first release of Distribute will be done at the end of this week, targeting setuptools 0.6x,<br>and will provide all latest bugfixes done in the 0.6 branches of setuptools, like Subversion 1.5 compatibility.<br>
> <br> - Distribute 0.2 (10/27/2008)<br>
> <br>The 0.2 release will be done in 1 month, targeting setuptools current trunk, and will focus on <br>providing a maximum of bugfixes. You can provide patches, or aks for a particular bug to be fixed.<br>Use the launchpad bug tracker for that <a href="https://bugs.launchpad.net/distribute">https://bugs.launchpad.net/distribute</a><br>
> <br>- Distribute 0.3 <br><br>The 0.3 release will contain new features and improvments, and its release date decide when 0.2 comes out.<br><br>Project managment<br>===============<br><br>Distribute is using launchpad (<a href="https://launchpad.net/distribute">https://launchpad.net/distribute</a>) and bzr and anyone that wants to <br>
> contribute is welcome to provide a branch. <br><br>The branch are merged if they provide tests and if there is a consensus of the community <br>on it.<br><br>The process is as follow for a contribution:<br><br>- create a bzr branch <br>
> - talk about it on distutils-SIG, using [distribute] in the header, asking for review/merge<br>- it is discussed in the mailing list<br>- if no one objects, and if it has tests, it will be merged by a maintainer<br><br>I am the maintainer at this point but this role will be extended to other people that want to become <br>
> a maintainer, so I will not become a botlleneck for this project.<br><br>A maintainer has to be nominated by 100% of the maintainers, and there will be at most<br>4 maintainers in this project. Maintainers are added or removed after each release.<br>
> They work together to release the next milestone.<br><br>Let me know if you want to become a maintainer. Maintainers need to discuss their changes<br>as well on the mailing list, and their only privilege is being able to merge branches on the main branch,<br>
> because they are trust to do so.<br><br>Cheers<br>Tarek<br clear="all"><br>-- <br>Tarek Ziadé | Association AfPy | <a href="http://www.afpy.org">www.afpy.org</a><br>Blog FR | <a href="http://programmation-python.org">http://programmation-python.org</a><br>
> Blog EN | <a href="http://tarekziade.wordpress.com/">http://tarekziade.wordpress.com/</a><br>
> </div>
> _______________________________________________
> Distutils-SIG maillist  -  Distutils-SIG at python.org
> http://mail.python.org/mailman/listinfo/distutils-sig


More information about the Distutils-SIG mailing list