Perhaps can I suggest the following: someone in the team file a ticket for any feature planned and then, keep responsability to close these bugs when features are added.By this way, you will both give visibility over the development activity and discourage people to file bug on missing features.
Once again, the last public and stable release is really old. In order to keep interest over gitg, you have to send some keep-alive messages. :-)Guilhem BONNEFILLE2013/4/3 Jesse van den Kieboom <jessevdk gnome org>Just my two cents, but I think it will be not super productive to file bugs for all the missing features right now. We pretty much know what things are still missing. For real bugs, crashes etc I agree though, feel free to file bugs.2013/4/3 Ignacio Casal Quinteiro <nacho resa gmail com>Regards.In relation to development we are trying to get it to have the same features as the previous gitg.Hi Adam,yes, feel free to file bugs in bugzilla, for libgit2-glib there is already one component.
On Wed, Apr 3, 2013 at 1:29 PM, Adam Dingle <adam medovina org> wrote:
_______________________________________________I've built the new Vala implementation gitg from git master and tried it out. It's coming along nicely!
Are bug reports for the new gitg welcome in Bugzilla at this time? What about feature requests, even for features which were present in the old gitg?adam
gitg-list mailing list
gitg-list gnome org
https://mail.gnome.org/mailman/listinfo/gitg-list
--
Ignacio Casal Quinteiro
_______________________________________________
gitg-list mailing list
gitg-list gnome org
https://mail.gnome.org/mailman/listinfo/gitg-list
_______________________________________________
gitg-list mailing list
gitg-list gnome org
https://mail.gnome.org/mailman/listinfo/gitg-list
--
-=- JID: guyou im apinc org MSN: guilhem_bonnefille hotmail com
-=- mailto:guilhem bonnefille gmail com
-=- http://nathguil.free.fr/