Good post, i think it sums up the stuff I've run into.. there s some of the project s which references a snapshot release, which is particularly unfortunate since it states the project version is in maven repo.
The some of the problems I've run into are of this character..others are just typos and maybe it would be nice with more examples(that would be a nice exercise for me).. On 28 Aug 2014 07:43, "Stephan Classen" <st.clas...@gmx.ch> wrote: > I am the newest member of the onami team. So the following is my personal > view and not the onami best practice. > > Well, if you know how to fix them, go ahead and fix them. > If you are not sure if the website contains something on purpose I would > ask the dev list. > > There is just a few things to consider: > 1) > According to https://issues.apache.org/jira/browse/INFRA-8057 we are in > the middle of a transition from SVN to GIT. > SVN is currently read only and any changes to GIT won't be reflected in > SVN. So there is no place to check in your changes. > > 2) > What version of the page do you fix? > I fixed myself a few deprecated links about a month ago (guice moved from > google-code to github). > I did the changes to trunk. But when I was about to deploy the sites I > realized that trunk contains all snapshot versions. > If I would deploy the sites from trunk then all version information would > be wrong. So I guess one must make the changes twice. > Once in trunk and once in a branch of the latest release. Lots of > duplicated work but this is feasible. > > 3) > How to deploy the sites? > Deployment would have to be done from the branches I guessed. > But this still doesn't quite cut it. Since the tags of the releases only > contain the subdirectories of a single module. > To build the site one also needs the modules "parent" and "site". But I'm > not sure if one should take these from trunk or from the time the > release of the module in question was released. I tend to go for trunk but > this means that the dependencies of the branch may change > since we release a new version of "parent" in March and most modules have > not been released since then. > > > So after I made the above thoughts I decided to leave the website as it is > and went on holiday. > Good thing you brought the topic back up. I'd love to call in a gathering > of all onami committers and work the issues out together. > We could discuss the new release procedure with GIT at the same time. > > > > > > > > On 08/27/2014 07:56 AM, nino martinez wael wrote: > >> Hi I've seen a couple of errors on our website and was wondering what the >> best approach to getting them fixed are.. >> >> Should I just create issues in jira or should I try to fix em? Or both? >> >> Whats the onami way? >> >> >
