From: Brian M. <br...@gr...> - 2008-01-25 23:19:05
|
Stephane, > > Brian, should we already add some more versions? > Perhaps a 2.2.11 which > > might never be released? Perhaps a 3.2 to start > documenting things that > > should not be in 3.0.x like the menu > restructuring? Perhaps a 3.0.1 for the > > things that are being done, but need not stop a > 3.0.0 to be released? > > Only an admin can make those releases, so I guess > that will mean you. I > > don't have a specific preference, but do like the > fact to have an overview > > of what other people want to achieve before a > release. > > I would like to see us keep future releases vague. > Create a single > "3.x" release, or call it "future GRAMPS" release. > This way > bugs/features don't get split into multiple future > release tags, > especially since we haven't yet defined what the > future releases will > be. Either it goes into an existing release -- like > 3.0.0 -- or into > a "future" bucket. > > This way when it comes time to bug scrub, you don't > have to decide yet > if it goes into 3.0.1, 3.1.0, 3.2.0, etc... Only > once a release is > defined do you bring into it the reports that will > be addresses. I agree. Given that we are made up of a bunch of volunteers, it is hard to predict what will be in which future release. "Target Version" should not be set for new features unless a person has committed to completing it and has assigned it to themselves. ~Brian |