Hi all,
I've created a new project on github, Moose-Collection. This project is
intended to be a superproject which tracks Moose and related projects as
they evolve and are released.
git clone git://github.com/samv/Moose-Collection
I'd like to get this automatically updating soon, such that the "stable"
branch always tracks the latest stable releases of modules, and "dev"
any pre-releases. To help with the automatic updating, it would be
appreciated if projects make signed tags eg "0.64" to indicate release
once they have done so. Moose and Class::MOP are already like this.
I've speculated on some policies for how the branches get updated; from
the README:
>---
In general there will not be a new superproject commit for every
submodule commit; if you want the very latest from each of the
submodules you will have to pull them individually. However, the
following branches will be defined;
- stable - representing only CPAN released versions of modules
- dev - representing CPAN development releases
- next - collecting 'master'-quality branches from sub-projects
where available, or latest CPAN release where not.
- pu - collecting 'trunk'-quality branches
'next' and 'pu' will be subject to automatic update, probably on an
hourly or thereabouts basis. 'stable' and 'dev' will be updated as
new already added CPAN releases are noticed, or as signed tags in
subprojects are noticed.
>---
Ideally I'd like to make it really easy for people to check out the
latest stable, dev, and unstable tracks of Moose. 'git submodule'
provides only basic plumbing at the moment so this is going to require a
few scripts; I'll post one as a patch to this list to give an example of
the sort of thing that might be useful...
Sam.
