You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by gi...@git.apache.org on 2017/05/02 23:59:43 UTC

[GitHub] wohali commented on issue #499: Sort out GitHub issues for gitbox repos

wohali commented on issue #499: Sort out GitHub issues for gitbox repos
URL: https://github.com/apache/couchdb/issues/499#issuecomment-298794021
 
 
   Yes, I think you've got exactly the right thing for "next minor release," except that we'd simply edit the label to become "2.2.0" once we knew what the numbering might be. (major.minor.patch right?) Alternately we can simply start with defining 2.1.0, 2.2.0, 3.0.0 etc and just assign things as necessary, and move them out to another milestone (or to no milestone if we can't make a commitment).
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services