Ben, i noticed your changes and wondering why there is a beta version if at the end a final 15 Release should have all fixed issues listed, independently from a beta or RC's. Is it a goal to publish 15-beta like any other release (e.g. Blog Post) and to re-label 15-beta issues with 15.0 once we made it? If Not, is it possible to get release notes/fixed bug list containing both, 15-beta and 15.0 issues?
IMO its a bit confusing because I want to indicate that the issues were fixed in the upcoming final release 15/14.1 any dependent project would integrate Clarification is much appreciated -- Frank Am 13.11.2015 05:08 schrieb "Ben Caradoc-Davies" <[email protected]>: > Developers, > > please use "15-beta" for master in Jira Affects and Fix Versions. The > rationale is that "15-beta" is the next release from master. > > I noticed that several issues were using "15" not "15-beta". I have > changed these to "15-beta" so they are not omitted from release > changelogs. I then removed the version "15". > > Jira makes it waaay to easy for any developer to inadvertently add a new > version with a single misplaced click. > > Kind regards, > > -- > Ben Caradoc-Davies <[email protected]> > Director > Transient Software Limited <http://transient.nz/> > New Zealand > > > ------------------------------------------------------------------------------ > _______________________________________________ > GeoTools-Devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel >
------------------------------------------------------------------------------
_______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
