[
https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373768#comment-15373768
]
Sean Busbey commented on HBASE-16215:
-------------------------------------
well, I disagree that there's no overhead. the list of branches could be where
folks can look to see the work that is going on. ATM they have to rely on
recently changed sorting to gauge where work is actually happening.
keeping history is good, and I like the archive/foo naming. How about tags?
that would mirror our use of 'rel/foo' tags for releases. Then if someone
decides to drive an additional release out of one of those release lines it'd
be easy enough to start a branch off of e.g. an 'archive/branch-1.0' tag. (or
maybe 'archive/eom-1.0' so the word branch isn't there?)
I'll start a DISCUSS thread. I think we're close enough to agreement to make
progress, so we might as well get everyone talking about it now.
> clean up 1.0.z references
> -------------------------
>
> Key: HBASE-16215
> URL: https://issues.apache.org/jira/browse/HBASE-16215
> Project: HBase
> Issue Type: Task
> Components: community, website
> Reporter: Sean Busbey
>
> I've seen us state a few places that 1.0.z is EOM. We should clean up
> remaining references
> * remove 1.0.z artifact from dist.apache
> * remove it from the ref guide (java prereqs, hadoop prereqs, RM list)
> * remove branch-1.0 from git
> * remove unreleased 1.0.z versions from JIRA
> * archive released 1.0.z versions in JIRA
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
