Hi all, I've just pushed v2.0.0 tag to the master branch, Fedora build and ISO is in the works and will be announced separately. But this occasion made me thinking about our 'next' branch and I'm not sure I like it any more: this used to be the place to do development of new features and master was supposed to be for stable release only. This made confusion for most of the people expecting to see new development in the default branch they get after checkout, master. I'd like to propose we drop 'next' branch and have only 'master' in the upstream repo and do development there, like in other projects e.g. libvirt.git What do you think? Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20110704/854d67fd/attachment.htm>
On 07/03/2011 06:44 PM, Alan Pevec wrote:> Hi all, > > I've just pushed v2.0.0 tag to the master branch, Fedora build and ISO > is in the works and will be announced separately. > But this occasion made me thinking about our 'next' branch and I'm not > sure I like it any more: this used to be the place to do development of > new features and master was supposed to be for stable release only. This > made confusion for most of the people expecting to see new development > in the default branch they get after checkout, master. > I'd like to propose we drop 'next' branch and have only 'master' in the > upstream repo and do development there, like in other projects e.g. > libvirt.git > What do you think?ack, go for it :)
Seemingly Similar Threads
- [Fwd: Re: [PATCH node-image] keep NIC and HBA firmwares]
- [PATCH node] save all not-parsed boot parameters
- [PATCH node-image] workaround for gpxe issue with the virt-preview
- [PATCH node] handle list of variables to ignore
- [PATCH node] display descriptions for all disks