Re: Update of parent Pom - change versioning scheme?
On 11 February 2011 16:05, sebb wrote: > On 11 February 2011 10:23, Asankha C. Perera wrote: >> Hi Sebastian >>> >>> We release the parent POM to Maven Central. >>> There's no Java code involved but there is source which is used by >>> Maven, so I think we probably ought to have a vote (as we did for the >>> plugin). >>> >>> There's almost nothing to check, so voting should be pretty simple. >>> And once it has a separate versioning scheme, it can be released >>> independently. >> >> We have time to finish the branding changes until end of Q1 2011. However >> the next report is due by 14th Feb 10am PST >> >> Do you think we could squeeze in the footer (the last remaining item) by >> this time? > > The code is all ready, as far as I can tell. I can release the Maven > skin tonight, when the 72 hours is up. > > I was planning on doing a comparison of the old and new pages next, in > case there are any problems, e.g. with broken links. > > I think it might be best to start with the parent site first. I've done the parent files. They seem to be OK. I had to change the css to drop the extra ApacheCon image at the top of the menu, so this will disappear from the child sites until they are updated. I'll move on to the next level shortly. > Not quite sure about how we redod the child sites - the docs may have > moved on since the last release, so it may be necessary to regenerate > from the tags. > In particular, we want the version info to relate to the release. I > can take a look at that. > > We don't normally vote on documentation, so I don't think that needs > to be held up by any vote on the parent POM. > >> thanks >> asankha >> >> -- >> Asankha C. Perera >> AdroitLogic, http://adroitlogic.org >> >> http://esbmagic.blogspot.com >> >> >> >> >> >> - >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: Update of parent Pom - change versioning scheme?
On 11 February 2011 10:23, Asankha C. Perera wrote: > Hi Sebastian >> >> We release the parent POM to Maven Central. >> There's no Java code involved but there is source which is used by >> Maven, so I think we probably ought to have a vote (as we did for the >> plugin). >> >> There's almost nothing to check, so voting should be pretty simple. >> And once it has a separate versioning scheme, it can be released >> independently. > > We have time to finish the branding changes until end of Q1 2011. However > the next report is due by 14th Feb 10am PST > > Do you think we could squeeze in the footer (the last remaining item) by > this time? The code is all ready, as far as I can tell. I can release the Maven skin tonight, when the 72 hours is up. I was planning on doing a comparison of the old and new pages next, in case there are any problems, e.g. with broken links. I think it might be best to start with the parent site first. Not quite sure about how we redod the child sites - the docs may have moved on since the last release, so it may be necessary to regenerate from the tags. In particular, we want the version info to relate to the release. I can take a look at that. We don't normally vote on documentation, so I don't think that needs to be held up by any vote on the parent POM. > thanks > asankha > > -- > Asankha C. Perera > AdroitLogic, http://adroitlogic.org > > http://esbmagic.blogspot.com > > > > > > - > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: Update of parent Pom - change versioning scheme?
Hi Sebastian We release the parent POM to Maven Central. There's no Java code involved but there is source which is used by Maven, so I think we probably ought to have a vote (as we did for the plugin). There's almost nothing to check, so voting should be pretty simple. And once it has a separate versioning scheme, it can be released independently. We have time to finish the branding changes until end of Q1 2011. However the next report is due by 14th Feb 10am PST Do you think we could squeeze in the footer (the last remaining item) by this time? thanks asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: Update of parent Pom - change versioning scheme?
On 9 February 2011 12:54, Oleg Kalnichevski wrote: > On Tue, 2011-02-08 at 22:51 +, sebb wrote: >> Assuming that the Maven Skin vote succeeds and it is released, I think >> we'll need to release a new version of the HC parent POM. >> >> At present its version appears to be tied to the client and core versions. >> >> I think it might be easier if the parent had a separate release cycle, >> with a separate version scheme. >> For example, Commons has just a single digit versioning scheme, like >> the Apache parent Pom. >> >> There probably also ought to be trunk and tags SVN directories for it. >> >> Thoughts? >> > > A very formal release process for a common parent project definitely > makes sense for Commons where a dozen of fairly different projects with > different groups of developers depend on it. I would prefer to keep > things simple for HC, if possible. We release the parent POM to Maven Central. There's no Java code involved but there is source which is used by Maven, so I think we probably ought to have a vote (as we did for the plugin). There's almost nothing to check, so voting should be pretty simple. And once it has a separate versioning scheme, it can be released independently. > I have no problem with a different (single digit) versioning scheme, > though. OK, we could start with 5 (which I think is bigger than 4.1.1 in Maven terms). - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: Update of parent Pom - change versioning scheme?
On Tue, 2011-02-08 at 22:51 +, sebb wrote: > Assuming that the Maven Skin vote succeeds and it is released, I think > we'll need to release a new version of the HC parent POM. > > At present its version appears to be tied to the client and core versions. > > I think it might be easier if the parent had a separate release cycle, > with a separate version scheme. > For example, Commons has just a single digit versioning scheme, like > the Apache parent Pom. > > There probably also ought to be trunk and tags SVN directories for it. > > Thoughts? > A very formal release process for a common parent project definitely makes sense for Commons where a dozen of fairly different projects with different groups of developers depend on it. I would prefer to keep things simple for HC, if possible. I have no problem with a different (single digit) versioning scheme, though. Oleg - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
