*In the past, the general practice for this community has been to not closeissues until they are released.*
Sure. Sounds good. We'll update our workflow to avoid closing issues until they're released. Thanks for everyone's patience while Carl and I get used to the Apache workflow! On Thu, Aug 7, 2014 at 3:59 PM, Matt Franklin <[email protected]> wrote: > On Thu, Aug 7, 2014 at 12:34 PM, Jmeas Apache <[email protected]> > wrote: > > > Makes sense, Chris. Once we switch over to the new process we'll wait > until > > the PRs are merged before closing tickets. > > > > In the past, the general practice for this community has been to not close > issues until they are released. They should sit in a resolved state once > the fix has been committed to the Apache Repository. > > > > > > > > On Thu, Aug 7, 2014 at 12:25 PM, Chris Geer <[email protected]> > wrote: > > > > > James, > > > > > > Thanks, my only concerns is if we are marking JIRA items complete but > > > people can't get that code from Apache source control I think we have > an > > > issue. > > > > > > Chris > > > > > > > > > On Thu, Aug 7, 2014 at 9:01 AM, Jmeas Apache <[email protected]> > > > wrote: > > > > > > > Hey there Chris, > > > > > > > > You're correct that we're not updating the angular branch directly. > The > > > > current work-flow (which is soon to change...more on that in a > moment), > > > is > > > > that we're developing on the bocoup/rave fork, on the ng-rave branch. > > All > > > > of our work can be seen in the open PR against the angular branch > here > > on > > > > Github <https://github.com/apache/rave/pull/7>. > > > > > > > > The reason we chose to do this is that it allows Carl and I to > iterate > > > > faster on PRs that have dependencies on one another while *also* > being > > > > transparent to the community. With that said, Matt Franklin proposed > > that > > > > we open PRs against both branches due to some legal considerations. > > > > > > > > So, sometime soon that branch should be merged in by Matt. At that > > point > > > > we'll be opening new PRs against the angular branch directly, and > > things > > > > will look more like what you're used to seeing. > > > > > > > > James > > > > > > > > > > > > On Thu, Aug 7, 2014 at 11:55 AM, Chris Geer <[email protected]> > > > wrote: > > > > > > > > > Jmeas, > > > > > > > > > > I'm not seeing any of your changes against the angular branch, but > > I'm > > > > > seeing the tickets being closed. Are you guys actually working on a > > > > > different repository? > > > > > > > > > > Chris > > > > > > > > > > > > > > > On Thu, Aug 7, 2014 at 8:35 AM, Jmeas Apache < > [email protected] > > > > > > > > wrote: > > > > > > > > > > > There are lots of big things coming to Rave soon (I'm sure you've > > > been > > > > > > getting the emails :) ). Carl Danley and I have been working on > > > > updating > > > > > > the Angular branch of the project recently, and we're excited to > > see > > > > how > > > > > > it's transforming the project. > > > > > > > > > > > > The Angular branch is going to be much faster, and also easier to > > > > develop > > > > > > on. If you're interested in chatting with us, you should join us > on > > > IRC > > > > > at > > > > > > ##apache-rave. We're still using this mailing list for anything > and > > > > > > everything official (like changes to the code), so you won't be > > > missing > > > > > out > > > > > > on anything if you don't join the channel. It's always opt-in and > > is > > > > only > > > > > > an *additional* way to talk about Rave. > > > > > > > > > > > > Hope to see you there! > > > > > > > > > > > > > > > > > > > > >
