Updated it a little bit :-) Now it's to my liking as well.
2013/9/25 Ankit Kumar <[email protected]> > Modified the Changes.txt to just mention the main JIRA items. Please review > and modify if still needed. > > @Mentors, please comment if we still miss anything or are we ready for > release. > > ~Ankit > > > On Tue, Sep 24, 2013 at 9:07 PM, Henry Saputra <[email protected] > >wrote: > > > Yes, CHANGES.txt can just contain list of bug fixes with JIRA cases to > > just help people know what being added/modify for each releases. > > > > - Henry > > > > > > On Tue, Sep 24, 2013 at 1:06 AM, Kasper Sørensen > > <[email protected]> wrote: > > > Hi Ankit, > > > > > > One remark about the changes.txt file... And first of all, sorry that > > it's > > > coming now and not earlier! I don't like the approach of dividing it up > > in > > > Sub-tasks, Tasks, New features etc... The file is meant for people to > > > understand what changes where made in a release, not necesarily what > > > categories etc. they had. And maybe some of it can be kept out to make > it > > > more clear to the reader. > > > > > > Take for example the Cassandra changes.txt file: > > > > > > https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=HEAD > > > > > > This IMO makes it much clearer what the individual releases mean for > the > > > user. I can make a suggestion for MetaModel, if you like? > > > > > > > > > > > > > > > 2013/9/23 Ankit Kumar <[email protected]> > > > > > >> Hi Henry, > > >> > > >> All my changes are pushed to the git repository. I don't exactly > > understand > > >> what you mean by "we need to change the SCM for getting the right > > source". > > >> Is it that we are pointing to a wrong location. > > >> > > >> Regarding the mvn and git staging repo could you please raise a JIRA > to > > the > > >> Infra as i don't know the exact process. It would be good if you also > > share > > >> how it should be done so we can do it ourselves next time. > > >> > > >> @Mentors, please review the codebase and provide comments if we still > > miss > > >> anything. In case you feel all is good do reply +1 for Go Hit the mvn > > >> release:prepare and perform. > > >> > > >> @Arvind, thanks for reminding will make a wiki page explaining the > > special > > >> steps needed to get the release of MetaModel. > > >> > > >> Regards > > >> Ankit > > >> > > >> > > >> On Sat, Sep 21, 2013 at 12:54 AM, Arvind Prabhakar <[email protected] > > >> >wrote: > > >> > > >> > Ankit, thanks for driving this effort. As you have probably figured > > out, > > >> > the first release is the most critical and often the most difficult > > one. > > >> I > > >> > have a few suggestions that may help you and the rest of the > MetaModel > > >> > community in this process: > > >> > > > >> > * It is a good idea to have a running Wiki page that documents the > > How-To > > >> > release process for MetaModel. You can definitely start off by > copying > > >> > another project's release guide but it is important to update it > with > > >> what > > >> > you find during this exercise so that subsequent release managers do > > not > > >> > need to spend time on the same issues. > > >> > > > >> > * There is a good check-list [1] that can be followed for high-level > > >> > aspects of the release. Add to it the input above from Marvin, and > you > > >> > would have covered most if not all aspects of the release. > > >> > > > >> > * In the projects I have worked on, even those that use maven for > > builds, > > >> > we seldom use the maven release plugin. This is because the release > > >> process > > >> > can go through multiple release candidates. Hence we usually fix the > > >> > release version in the pom files on creation of the branch and keep > > >> fixing > > >> > it until it is released. But that is just one way to do it, and if > you > > >> can > > >> > find a more suitable mechanism for MetaModel then that is great too! > > >> > > > >> > Have you cut a release branch yet? > > >> > > > >> > [1] > > http://incubator.apache.org/guides/releasemanagement.html#check-list > > >> > > > >> > Regards, > > >> > Arvind Prabhakar > > >> > > > >> > > > >> > On Fri, Sep 20, 2013 at 10:54 AM, Henry Saputra < > > [email protected] > > >> > >wrote: > > >> > > > >> > > Did you commit the changes to git? We need to change SCM for > getting > > >> > > the right source. > > >> > > > > >> > > We also need mvn and git staging repo, need to file JIRA to INFRA > > for > > >> > > it. If no one gets to it by EOD I will file ticket. > > >> > > > > >> > > - Henry > > >> > > > > >> > > On Fri, Sep 20, 2013 at 8:24 AM, Ankit Kumar < > > [email protected]> > > >> > > wrote: > > >> > > > Hi All, > > >> > > > > > >> > > > We have made the necessary changes and we think we are ready for > > >> > release. > > >> > > > Atleast the mvn release:prepare DryRun does work. > > >> > > > > > >> > > > @Mentors, can you also assert if we are all good for the first > > >> release. > > >> > > If > > >> > > > possible we can also have a quick skype/gtalk session to > confirm. > > >> > > > > > >> > > > @Gagan, thanks for pointing to the apache-blur project, since > you > > >> have > > >> > > some > > >> > > > experience with (mvn and git on apache project) can you now > check > > the > > >> > > > latest Metamodel pom and verify all is good. > > >> > > > > > >> > > > Regards > > >> > > > Ankit > > >> > > > > >> > > > >> > > >
