Hi All,<br><br>I wanted to convey you all that Gluster's Bugzilla (<a href="http://bugs.gluster.com">http://bugs.gluster.com</a>) is in the process of migration to Red Hat's Bugzilla (<a href="https://bugzilla.redhat.com">https://bugzilla.redhat.com</a>). For all of you, the difference will be just different URL to hit while submitting the bug.<br>
<br>We will be keeping all the existing bugs as is, and GlusterFS product will be listed in Community version of Red Hat products (<a href="https://bugzilla.redhat.com/enter_bug.cgi?classification=Community">https://bugzilla.redhat.com/enter_bug.cgi?classification=Community</a>)<br>
<br>Currently, we (@Gluster) are supporting both commercial deployments and community releases under same bugzilla database, and if we only move commercial bugzilla to <a href="http://redhat.com">redhat.com</a>, it would lead to lot more confusion, and it would be lot of work to track bugs from two different databases on developers as product will remain same in both case. Hence we decided keep just one bugzilla instance. This would make sure every one has better visibility on what is happening w.r.t the project.<br>
<br>Also our current development practice to use Gerrit (<a href="http://review.gluster.com">http://review.gluster.com</a>) and Jenkins (<a href="http://build.gluster.com">http://build.gluster.com</a>) for code submission will remain as is, which means, each commit will go against a bug id, which would be visible for everyone.<br>
<br>After the migration, all your user credentials in <a href="http://bugs.gluster.com">bugs.gluster.com</a> will be properly copied over to <a href="http://bugzilla.redhat.com">bugzilla.redhat.com</a>. If any of you have account in both bugzillas already, and if the email-id used is same, then the account will be merged together.<br>
<br>Current planned date of migration is around Dec 10th, 2011.<br><br>Please feel free to ask questions if you have any.<br><br>Regards,<br>Amar<br>GlusterFS Developer<br><br>