For sure should setup the git flow, it can open up new decoupled things for development. As for the release, I haven't done any Apache release before so would anyone like to own this up ? I can kick-off the things but would require some help from the more experienced Apache citizens !
regards, Rahul On Sat, Sep 28, 2013 at 2:41 AM, Mirko Kämpf <[email protected]> wrote: > I also think this is a good time for a release. > Especially the feature branches might help to open > and decouple future work. > > +1 > > Best wishes > Mirko > > > 2013/9/27 Adam Berry <[email protected]> > > > I think this is a good idea. > > > > I would like to propose though that moving forward we use the git flow > > model for managing moving through releases etc. Under this we would > create > > a develop that represents the current state of hadoop-eclipse-merge with > > HDT-40 applied (when we get there). Tagging when we get to an approved > > release as is the traditional Apache way. > > > > We can make a branch to archive master as it stands right now with the > > converted old tools. > > > > Then we could make a release branch to drive home on getting these > features > > out asap. Shortly after, or at the same time we can start the work on > > feature branch(es) for developing the MR launch features using the same > > ideas as we have for HDFS now. > > > > Cheers, > > Adam > > > > > > > > On Fri, Sep 27, 2013 at 4:02 AM, Rahul Sharma <[email protected]> > wrote: > > > > > I would like to know how do people feel about release of HDT from > > > hadoop-eclipse-merge branch. With the fix of icons issue[1] I think the > > > functionality of browsing Zookeeper and HDFS servers provides us a > good > > > release point. > > > > > > regards, > > > Rahul > > > > > > 1: https://issues.apache.org/jira/browse/HDT-40 > > > > > >
