Hi,
for better or worse, our milestone and release planning is not great. We normally decide on what we want to work on for the next release and release new versions based on Fedora or RHEL releases (mostly because there is normally no other driver..if there are other projects or distributions who would like us to release on a different schedule, please just speak up!).
The result is that our milestones don't really reflect the reality -- we have a huge milestone called "1.16" that is not really going to become 1.16, it's rather a set of tickets we'd like to work on "sometimes in the future". In addition, we have milestones that track bug fixing in released versions, currently 1.13.5 and 1.14.2 and the version currently under development, which is 1.15 at the moment.
What I propose to make it clearer to outsiders what the expectations are is simply the following: - rename the current 1.16 bucket to "Future releases", maybe with a more explanatory note, like "Future releases - not planned for a particular date" - triage the milestones like 1.17 or 2.0, move tickets from there either to deferred or just close them - rename the "Deferred" milestone to "Patches welcome".
I think this would make it clearer a bit in terms of what the sssd upstream is working on now and what we are working on next..
Comments? Thoughts?
On 10/07/2016 12:20 PM, Jakub Hrozek wrote:
Hi,
for better or worse, our milestone and release planning is not great. We normally decide on what we want to work on for the next release and release new versions based on Fedora or RHEL releases (mostly because there is normally no other driver..if there are other projects or distributions who would like us to release on a different schedule, please just speak up!).
The result is that our milestones don't really reflect the reality -- we have a huge milestone called "1.16" that is not really going to become 1.16, it's rather a set of tickets we'd like to work on "sometimes in the future". In addition, we have milestones that track bug fixing in released versions, currently 1.13.5 and 1.14.2 and the version currently under development, which is 1.15 at the moment.
What I propose to make it clearer to outsiders what the expectations are is simply the following: - rename the current 1.16 bucket to "Future releases", maybe with a more explanatory note, like "Future releases - not planned for a particular date" - triage the milestones like 1.17 or 2.0, move tickets from there either to deferred or just close them - rename the "Deferred" milestone to "Patches welcome".
I think this would make it clearer a bit in terms of what the sssd upstream is working on now and what we are working on next..
Comments? Thoughts?
Ack.
We can do the 1.17 and 2.0 (and maybe other milestones) triage on the next devel meeting. Or we can make a special BJ call for this.
Michal
On Fri, Oct 07, 2016 at 02:23:16PM +0200, Michal Židek wrote:
On 10/07/2016 12:20 PM, Jakub Hrozek wrote:
Hi,
for better or worse, our milestone and release planning is not great. We normally decide on what we want to work on for the next release and release new versions based on Fedora or RHEL releases (mostly because there is normally no other driver..if there are other projects or distributions who would like us to release on a different schedule, please just speak up!).
The result is that our milestones don't really reflect the reality -- we have a huge milestone called "1.16" that is not really going to become 1.16, it's rather a set of tickets we'd like to work on "sometimes in the future". In addition, we have milestones that track bug fixing in released versions, currently 1.13.5 and 1.14.2 and the version currently under development, which is 1.15 at the moment.
What I propose to make it clearer to outsiders what the expectations are is simply the following: - rename the current 1.16 bucket to "Future releases", maybe with a more explanatory note, like "Future releases - not planned for a particular date" - triage the milestones like 1.17 or 2.0, move tickets from there either to deferred or just close them - rename the "Deferred" milestone to "Patches welcome".
I think this would make it clearer a bit in terms of what the sssd upstream is working on now and what we are working on next..
Comments? Thoughts?
Ack.
We can do the 1.17 and 2.0 (and maybe other milestones) triage on the next devel meeting. Or we can make a special BJ call for this.
Renamed.
I also moved all tickets from 2.0 to triage.
On Fri, Oct 7, 2016 at 12:20 PM, Jakub Hrozek jhrozek@redhat.com wrote:
Hi,
for better or worse, our milestone and release planning is not great. We normally decide on what we want to work on for the next release and release new versions based on Fedora or RHEL releases (mostly because there is normally no other driver..if there are other projects or distributions who would like us to release on a different schedule, please just speak up!).
The result is that our milestones don't really reflect the reality -- we have a huge milestone called "1.16" that is not really going to become 1.16, it's rather a set of tickets we'd like to work on "sometimes in the future". In addition, we have milestones that track bug fixing in released versions, currently 1.13.5 and 1.14.2 and the version currently under development, which is 1.15 at the moment.
What I propose to make it clearer to outsiders what the expectations are is simply the following: - rename the current 1.16 bucket to "Future releases", maybe with a more explanatory note, like "Future releases - not planned for a particular date" - triage the milestones like 1.17 or 2.0, move tickets from there either to deferred or just close them - rename the "Deferred" milestone to "Patches welcome".
I think this would make it clearer a bit in terms of what the sssd upstream is working on now and what we are working on next..
Comments? Thoughts?
ACK. I really like the idea, it does look more organized both for us and for whoever is consuming SSSD.
Best Regards, -- Fabiano Fidêncio
sssd-devel@lists.fedorahosted.org
-
Fabiano Fidêncio -
Jakub Hrozek -
Michal Židek